Viewing posts for the category debian
After I finished an re-read my epic post describing my first day and a half at Debconf10 I suddenly realised that if I continue to describe the rest of 13 days here in such style and verbosity this would become a book, a boring one at that, so I decided to limit myself to 2 posts for Debcamp and then a post a day for the Debconf.
I had planned long for this Debconf and with the experience from the previous times I did all I could to reach one goal - minimise stress. I think I got it right this time.
After a few months, today I finally got the approval and
Daniel, I also recently installed a WRT on the Linksys WRT54GL. But I used DD-WRT instructions - went to http://www.dd-wrt.com/site/support/router-database, entered my model number and got direct download links to the firmware along with a README.
Want a sound card? Want a cleared sound that is not contaminated by electromagnetic interference in you computer's case? Want that all to work in Linux?
Want a definition of a paper cut bug? Here it is. And here and here are two more side effects of the same bug. The original bug report will be 6 years old in a month. Can we do something to prevent this bug surviving that long?
A bit more than a week after Debconf9 ended here is a post summarising what I remember about it - for myself to look back to later, for others that were there for a good memory, for those that were not there for insight and for organisers of future Debconfs to improve.
First I will point to resources that will receive more updates than this blog:
Daniel says that we should move away from SHA1 by switching hash algorithms for signatures and generating keys that use at least SHA256 from SHA-2 family. I have been bitten by non-default GPG options before. So I propose that we do a security release of GPG that changes the defaults of key generation and key signing in such ways that SHA-1 algorithms are not used by default for any operation, unless a backwards compatibility option is used.