Why use a password manager in the first place? Well, they make it easy to have strong, unique passwords for each of your accounts on every system you use (and that’s a good thing).
For years I’ve stored my passwords in Firefox, because it’s convenient, and I never bothered with all those other fancy password managers. The problem is, that it locked me into Firefox and I found myself still needing to remember passwords for servers and things.
So a few months ago I decided to give command line tool Pass a try. It’s essentially a shell script wrapper for GnuPG and stores your passwords (with any notes) in individually encrypted files.
I love it.
Continue reading Command line password management with pass
The Free Software Foundation has published a reply to Microsoft’s Community Promise surrounding C# and CLI. Here’s a snippet:
The ECMA 334 and 335 specifications describe the core C# language, including information about standard libraries that must be available in any compliant implementation. However, there are several libraries that are included with Mono, and commonly used by applications like Tomboy, that are not required by the standard. And just to be clear, we’re not talking about Windows-specific libraries like ASP.NET and Windows Forms. Instead, we’re talking about libraries under the System namespace that provide common functionality programmers expect in modern programming languages: binary object serialization, regular expressions, XPath and XSLT, and more.
Microsoft needs to do more to assure the free software community that they will not sue over the use of .NET. Release an irrevocable license for all patents in .NET (or at least Mono’s implementation) that remains in effect even after a sale of said patents. Or make a deal with Novell and get them to release Mono under GPLv3..
Peter Galli has written on his blog that he was informed by Scott Guthrie (the Corporate Vice President for the .Net Developer Platform) that Microsoft will include C# and CLI under their “Community Promise“.
It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions.
You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications.
Just when (or if) this will happen is not yet clear, nor is whether it will hold any water. Still, it could be the one step to help ease the current patent issues in Mono in relation to C# and CLI (the rest of the Mono implementation of .NET remains under threat however).
Gotta laugh at this from Microsoft’s promise, though:
This promise by Microsoft is not an assurance that either (i) any of Microsoft’s issued patent claims covers a Covered Implementation or are enforceable.
Anyway, interesting to see where this goes.