PROJET AUTOBLOG


Free Software Foundation Recent blog posts

source: Free Software Foundation Recent blog posts

⇐ retour index

Mise à jour

Mise à jour de la base de données, veuillez patienter...

One year of encryption with the Email Self-Defense guide

samedi 6 juin 2015 à 00:15

Since then, Email Self-Defense has been translated into ten languages, and our metrics show that tens of thousands of people have used it.

If you've been putting off setting up encryption, or know someone who might like your help setting it up, this anniversary is a great occasion to do it! It only takes about half an hour with the Email Self-Defense guide.

Resist bnulk surveillance

Even if you have nothing to hide, using encryption helps protect the privacy of people you communicate with and makes it harder for surveillance systems to isolate messages sent by those that do need protection, like whistleblowers and activists. By encrypting more of the traffic on the net, we give the surveillance systems more opaque information to sift through.

But the goal of Email Self-Defense is more than just helping people protect their information. It's also about highlighting the crucial role of free software in privacy and security, which has not received the attention it deserves in the media coverage of surveillance reform. No matter what laws governments are eventually able to pass to regulate surveillance programs, access to the source code of the computer systems we are using is crucial if we are to have a fighting chance of understanding and controlling what happens to our data.

Encryption is a critical first step, but to effectively resist bulk surveillance, we also need to build new, decentralized Web systems and work for political change. The FSF most recently joined a coalition to resist efforts to require mandatory backdoors in encryption software and we maintain a surveillance action area on fsf.org. Our founder, Richard Stallman, also describes guidelines for reining in surveillance in some detail on gnu.org.

We're excited to have an intern, Adam Leibson, joining us for the summer to work on encryption- and surveillance-related campaigns. Stay tuned for publications about his work. In the meantime, have fun setting up encryption with Email Self-Defense and share the infographic with your friends. If you want to try out your encryption, you can always send me a message at zak@fsf.org with the public key 6EB2 B137 347E 6F7C DEDC AFF6 82DE 8D64 B509 0AC8.

Introducing Stephen Mahood, system administrator

mercredi 3 juin 2015 à 19:05

This introduction has taken me time because we have been busy—despite the record snowfall in Boston this winter, there have been a few 'fires' to put out. Once the fires were extinguished we had more snow than I could ever imagine, followed quickly by LibrePlanet, so perhaps this should be taken as my six-month introduction.

Why would people in the Latin American free software community know me? Well, before moving back to Boston, I spent nearly three years south of the U.S., living in San Marcos, Guatemala and Distrito Federal (aka Mexico City), Mexico. In that time, I traveled to Brazil for the World Social Forum Free Palestine as a free software tech activist working to maintain the conference site (Drupal 7) and registration (CiviCRM), and to participate in a collective session on tech security for activists. However, tech has not always been my path. I became an activist before deeply delving into the free software movement.

My work began with political organizing for the Howard Dean campaign in the U.S. in 2003. During that time, I learned and organized using the labor union organizing model of César Chávez of the United Farm Workers. Why might that be of interest to the free software movement? The database system we used to track, update, and engage voters is mirrored in CiviCRM. The methods and models of our organizing focused on sharing stories and getting to know our supporters more closely. We kept detailed notes from our one-on-one meetings with supporters and input that information into our database with ease, but more importantly, we were able to track friends, family, and neighbors who expressed support. We could pinpoint the meetings they attended; all of this was easily put into the database in a form that, if another organizer picked up our work, they could catch up pretty quickly and continue without missing a beat. Impressed? I know I was, to the point that I felt the desire and need to learn more about this organizing model, with the hopes the tech would not be too far behind.

Soon after the election was over and George W. Bush was reelected, I found my way into a graduate program at the University of Massachusetts Amherst. The graduate program in Labor Relations and Research (we just called it Labor Studies) altered my life and understanding of the world, including free software. Though I had used GNU/Linux before, it was in graduate school that I began to see the connection between free software movements and labor/social movements. I saw that we cannot just sit on the sidelines waiting for people to individually choose to use and build free software, we need to organize and engage people to understand why free software creates a better future for us all. The first step came with my fellow union members (graduate students in the UMass system are organized in the United Auto Workers union) where we began to replace the Windows systems in our office with Ubuntu (which was only a step away from proprietary, as I later learned how Ubuntu is not so free as in freedom, despite being free as in beer). Though it was a good step with our local, in other labor union interactions the idea of GNU/Linux was foreign, as the tide of MacBooks swept in (I was guilty of it too, but that did not last long).

In labor circles discussing technology is a challenge. The labor movement itself never adapted well to technology, usually fighting it off instead of learning how it could improve their bargaining position and offer their own technology ideas before the 'boss' enforced them. Discussions about office computers were equally challenging, as computers are seen as just a tool. Seeing this, I began actively conversing with free software folks on identi.ca (later StatusNet and now GNU social), where I met a comrade named Walton (aka @leischa), who wrote his masters dissertation on adapting the free software development method (making code available for others to look at and contribute to) to labor movements, which historically has been rather closed and don't share experiences with other unions and groups. So, we both share the viewpoint that labor unions need to work together not just in solidarity, but in reality. There are strengths in some unions and weaknesses in others, and we both advocate for unions to accept those differences and move forward, adapting to the system we reside in -- that is when we decided to create a podcast to discuss this issue.

With our shared vision, me and Walton created the Cyberunions podcast. We began before—but in the same year as—the Occupy movement. We discussed in great detail software that we knew would be beneficial to the labor movement, as well as elements in the labor movement that free software communities could adopt. Walton and I had and continue to have visions of labor unions funding free software, but we also felt it was a struggle to convince a union to use free software, let alone support its development. The podcast has been around for a while now, though we have been bad about keeping it up to date as of late—but there are plans to bring it back.

In the four years that the Cyberunions podcast has been around, I have had the chance to meet and learn from many amazing folks, mostly from the May First People Link community, but also with folks from StatusNet/GNU social—and that continues to this day. If it were not for chance meetings and connections, I would never be where I am now, working for an organization at the foundation and forefront of free software. It was activism and organizing that got me where I am, and I see no reason to stop now. I will continue to organize and work with unions to adopt free software even our own (FSF staff are also in the UAW -- more like United Aferro Workers). If you see me around in IRC (marxistvegan on freenode or mv on oftc and indymedia) or on GNU social, I look forward to engaging with the community and plan to keep organizing while maintaining our servers through rain, sleet, hail, and snow. I only draw the line when the temperature are in the 90s (30s in C). I hate the heat.

in solidarity && happy hacking

March through May 2015 - Quezón City, Iligan, Yangon, Mandalay, Lyon

lundi 1 juin 2015 à 22:10

Here are some photographic excerpts of a few of the trips RMS has taken in the past few months.

He was in Quezón City, Philippines, on March 25th, 2015, to give his speech, "A Brave GNU World," to a packed room as part of RightsCon Southeast Asia:

(Photo under CC BY-ND and courtesy of EngageMedia.)

...in Iligan, Philippines, on March 30th, to give a speech on computing, freedom, and privacy at Mindanao State University:

(Photos under CC BY-ND and courtesy of Bobby Timonera.)

...in Myanmar — his first visit to the country — to speak in Yangon on April 2nd and in Mandalay on April 7th. The visit was a great success, with The Myanmar Times' Stuart Alan Becker saying

Richard Stallman's speeches in Yangon and at Mandalay University caused a lot of young people in Myanmar to take a second look at the trends taking place in the online world. In a country where the migration to mobile technology is happening at great speed, Stallman's message was something most of them had never heard: an activism in favor of user's control. The people who listened to Richard were exposed — some for the first time — to the notion that profit motivated companies impose restrictions and limit choices. With FSF's resources, I think some of them were opened to a new world of possibility.

(Photos under CC BY-ND and courtesy of Stuart Alan Becker.)

...and in Lyon, France, on May 14th, to speak at the European Lab's fifth forum for an audience of hundreds:

(Photos under CC BY-ND and courtesy of Marion Bornaz.)

Please fill out our contact form so that we can inform you about future events in and around Quezón City, Iligan, Yangon and Mandalay, and Lyon.

Please see www.fsf.org/events for a full list of RMS's confirmed engagements, and contact rms-assist@gnu.org if you'd like him to come speak.

Thank you to everyone who helped make these visits possible!

The Licensing and Compliance Lab interviews François Marier of Libravatar

lundi 1 juin 2015 à 19:20

In this edition, we conducted an email-based interview with François Marier, a free software developer from New Zealand. He is the lead developer of Libravatar. In addition to his passion for decentralization, he contributes to the Debian project and volunteers on the FSF licensing team.

Libravatar is a free network service providing profile photos for a number of Web sites, including bugs.debian.org and git.kernel.org. Its flexible architecture allows end users to host their own images and allows Web sites to use Gravatar as a fallback when necessary. It is licensed under the GNU Affero General Public License version 3, or end user can opt for any later version (GNU AGPLv3+).

What inspired you to create Libravatar?

As I explained in a talk I gave at linux.conf.au in 2011, my main sources of inspiration were the Franklin Street Statement, as well as a talk that Evan Prodromou gave at LibrePlanet in 2009.

I figured that we have a lot of work to do to replace all of the nonfree Web services we rely on, and so I decided that I would participate and get started with replacing the simplest Web service I could think of: the Gravatar.com avatar hosting service.

How are people using it?

The main audience for Libravatar are the developers of free Web applications. By using Libravatar over Gravatar, they are giving their users the option of either self-hosting their own avatars or using a free software service.

There are a few projects that use Libravatar, and in terms of traffic, our biggest users are the Debian, Fedora, Mozilla and the kernel Linux projects.

What features do you think really set Libravatar apart from similar software?

While Libravatar and Gravatar are quite similar in terms of features, Libravatar distinguishes itself in the areas of federation and self-hosting, as well as support for independent authentication systems. We also made it easy to delete and export your account because we believe that users should be in control of their own data.

Why did you choose the GNU AGPLv3+ as Libravatar's license?

Since my original goal was to produce a free software replacement for Gravatar, using a copyleft license was a no-brainer since it guarantees that the software will always stay free.

While developers are free to rely on the Libravatar service in their nonfree Web applications, I wanted any self-hoster using the main codebase to be part of our community. The GNU AGPL seemed like a good way to encourage a sharing culture.

How can people help contribute to Libravatar?

Our most pressing need is growing our mirror network. If you have a small amount of disk space (< 400 MB) and bandwidth (around 1GB / month) on your server, please get in touch at mirrors@libravatar.org! We are slowly becoming more and more popular and are already pretty close to capacity. Scaling a free service to keep up with increasing popularity is one of the big unsolved problems in the free software world, it seems.

Another easy place where people can help is with translations. We currently support fourteen different languages but we are always hoping to reach more people in their native language.

What's the next big thing for Libravatar?

It's hard to point to a single big thing because the service is fairly mature now, having been around since 2010.

Some of the things we are thinking about at the moment are: support for Do Not Track, SVG avatars (to help with high-DPI displays), and a graphical refresh with support for mobile. Get in touch if you are good with pixels and interested in getting involved.

Sysadmin adventures: When weather threatens our work

lundi 1 juin 2015 à 17:01

You might be wondering, why in the world would an air conditioner be important during a blizzard? It's all about the servers. Most of our servers are not on site in our office, but those that are vital to the day-to-day work of the FSF are.

For me, snow is a welcome given of living in the Boston area, one that I missed in more than three years living in Guatemala and Mexico. Despite meeting some awesome free software comrades during that time, winter was always calling me back north. Home to me has always been Boston (I skip my youth because, well, New Jersey is worth skipping). I moved here in the fall of 1996 and experienced my first major snowstorm the following April Fools' Day, the biggest joke of the year. The temperature was in the 60s (Fahrenheit, the mid-teens in Celsius) for weeks prior, when suddenly we were slammed with 25 inches (63.5 cm) of snow in a twelve hour period—the biggest storm since the infamous Blizzard of 1978. I have always welcomed the snow in my life. After all, I was born in the blizzard that happened just a few weeks before the record-breaker in 1978, which nearly led to my mother being taken to the hospital by snowmobile. I like the snow and the challenges it brings to life, but I never thought it would affect my work as a sysadmin.

View from the roof door, with the FSF air conditioning unit on the other end of the roof

A view from the roof door, with the FSF air conditioning unit on the far end.

The weather throughout February brought high temperatures below freezing and weekly snow storms, amounting to piles of snow taller than me (sixty-six inches, or 1.676 meters). We received more than ninety-five inches (2.43 meters) of snow, cumulatively, and none of it melted in February. The last week of the month brought a new challenge, one I had never considered. Another snowstorm with high winds led to giant drifts of snow.

And then came the temperature warnings in our server closet. It incrementally went from 70F (21C) to 90F (32C). The weather was bad enough to severely delay—or shut down entirely—the public transit system, so travel to the office wasn't feasible for any of us in the Boston office. Over IRC, me and Lisa, our senior sysadmin, began identifying which servers we could turn off during the weekend to help lower the temperature in the closet. At this point, we had no idea why the air conditioning, crucial to temperature regulation in the server closet, was not working. It was not until Tuesday that we were able to make it back to the office.

Arriving by bike on Tuesday morning, I was ready to investigate the air conditioning issue. Thinking through the possibilities, I decided to turn the unit back on and see if it would stay on. That lasted about ten minutes before it automatically shut down. This left me with few options: either call the repair folks and hope they could come to the office that day or we could further investigate the issue myself by going to the roof, where ventilation part of the unit resides. Off I went.

This was not my first visit to the roof for an air conditioner issue, so I knew where to find the unit. I put on a sweatshirt and a keffiyeh and headed to the roof. The roof door locks from the inside, so I grabbed a piece of metal to wedge in the door to keep me from being locked out. I pushed the door to the roof and...it did not budge even an inch. Snow was piled up blocking the door. I leaned in, hard, and the door ever so slowly opened, leaving me just enough room to squeeze through.

But as I got out on the roof, the next challenge presented itself: four feet of snow, covering a veritable farm of air conditioning units—and ours was on the far side of the roof, forty snow-covered yards away.

To get there, I had to climb over other air conditioning units, duck below beams, and push through the snow. I finally arrived at our AC unit, and after some digging, I discovered that the snow had blown into the unit's cooling fan, preventing from spinning. I spent most of the morning digging and cleaning out the fan. I trekked back to the office, and the system started up again. Just one of the many quirks of a sysadmin's role here at the FSF.