Just two short weeks after the release of the previous version of CQRLOG, version 1.7.1 has been released to the public with the following bugfixes:
- “When TRX control is not active, use frequency and mode from NewQSO window” option to Preferences->Band map added
- CTRL+N hotkey to QSO list window added (do NOT send QSL)
- TRX control window was not sizeable – fixed
- when ESC was pressed twice in Remote mode, log crashed – fixed
- program crashed when freq was entered with comma as decimal separator – fixed
- broken grid square statistic fixed
If you can, please evaluate this new package and provide karma. The new package should already be in rawhide.
I recently upgrade to Fedora 20 and quickly found my offlineimap instance failing. I was getting all kinds of errors regarding the certificate not being authenticated. Concerned wasn’t really the word I’d use to describe my feelings around the subject. Turns out, the version of offlineimap in Fedora 20 (I won’t speculate as to earlier versions) requires a certificate fingerprint validation or a CA validation if
SSL=yes is in the configuration file (.offlineimaprc). I was able to remedy the situation by putting
sslcacertfile = /etc/ssl/certs/ca-bundle.crt in the config file.
I won’t speculate as to the functionality in earlier versions but checking to make sure the SSL certificate is valid is quite important (MITM). If you run across a similar problem just follow the instructions above and all should, once again, be right with the world.
The F21 Election schedule slipped and I’ve reworked the election schedule. Please note that we’ve opened up input for the questionnaire so there is still time to ask a question if you haven’t already done so. Additional information will be transmitted per the schedule.
Fedora Board Elections
There are two nominations for two open seats on the Board: Neville Cross and Haïkel Guémar. Because there were no other challengers we won’t hold an election or townhall for these candidates.
FESCo (Engineering) Elections
There are six nominations for four seats on FESCo: Stephen Gallagher, Dennis Gilmore, Miloslav Trmač, Marcela Mašláňová, Toshio Kuratomi, and Kyle McMartin. Because there are challengers for the seats we’ll hold a townhall and an election based on the updated schedule. Input for the questionnaire for the candidates has been reopened until 23:59UTC on 27 January 2014.
FAmSCo (Ambassadors) Elections
There are four nominations for three seats on FAmSCo: Neville A. Cross, Truong Anh Tuan, Marcel Ribeiro Dantas, and Jon Disnard. Because there are challengers for the seats we’ll hold a townhall and an election based on the updated schedule. Input for the questionnaire for the candidates has been reopened until 23:59UTC on 27 January 2014.
I’ve just built the latest version of CQRLOG, version 1.6.1, for Fedora 18 through 21. The packages are being pushed to the updates-testing repos now and should be available soon. If you use CQRLOG in Fedora from the repositories I’d appreciate you testing this latest build and giving karma if it works (or doesn’t work) for you.
This update provides the following enhancements and bugfixes:
- 630M band added
- added OQRS (online QSL request system) to QSL sent menu
- added “Always sort by QSO date” option to Search function
- cursor is moved to last opened log in DB connection window
- “Ask before creating a backup” option to “Auto backup” added
- band map is much faster, a few optimization added
- program freezed for a few milliseconds with every bandmap refresh – fixed
- “MySQL server has gone away” problem fixed
- membership values collation were case sensitive – fixed
- ADIF import sometimes crashed with access vioalation, now will show what happened
- qrz search with right click on a call in the recent QSOs list didn’t work
- band map font settings was not loaded when program started
This morning I was greeted with a blog post from the fine folks over at Qualys on how BEAST isn’t really still a threat (unless you are using an Apple product). BEAST, a vulnerability found in SSL and TLS 1.0, was discovered around this time a couple of years ago and put web users in a precarious position of using a poor cipher choice (RC4) or be vulnerable. Not to worry, however, as developers were able to come up with a solution to the problem (n/n-1).
So I mentioned the Qualys article in my $dayjob IRC channel where my always awake coworker provided information that Fedora is, in fact, still vulnerable to the attack. Thanks to a problem with pidgin-sipe connecting to a Microsoft server, the n/n-1 split was backed out of the NSS software leaving anything that depends on it potentially vulnerable (Chrome, Firefox, and Thunderbird to name a few).
There is a fix, although it’s not fantastic by any stretch of the imagination. By simply adding these two lines to your /usr/bin/firefox file the vulnerability should be fixed:
We added these two lines at line 36 and restarted Firefox. My way-too-awake coworker did a test and confirmed that it was working in his environment. Your mileage may vary.
Hopefully the fix for BEAST can be reapplied to NSS in Fedora soon as leaving users exposed can be dangerous.
Thanks to Hubert Kario for pointing me, and walking me, though this stuff before my morning coffee.
Update: 2013-09-12 @ 14:30 UTC
Apparently this problem will be persistent according to the NSS package maintainer. From the ticket:
I bit of information from the nss side of things. The nss disabling patch is not applied on Rawhide or f20, onlt applied on stable branches. After we branch Rawhide for the next fedora release and we enter in Alpha, I send emails to the fedora development mailing list telling them that NSS_SSL_CBC_RANDOM_IV=1 will be the default as they use updates-testing and ask for feedback on whether it causes problems. Twice they have said it still causes problems. There are still unpatches servers out there. Once we go beta I have to enable the patch again. f20 is entering Alpha soon so I’ll send that email again. I know this bug is for Firefox but I though worth informing you that we monitor this every six months for nss.
Update: 2013-10-10 @ 15:22 UTC
Update: 2013-10-17 @ 10:32 UTC
I believe this problem has been fixed (finally!) for Fedora 19 and beyond.
On Sunday, 08 September, upstream developers released version 1.6.0 of CQRLOG. This update has been pushed to the testing repositories in Fedora for versions F21, F20, and F19. Three +1 karma feedback gets the update into the normal Fedora update repos sooner. Please give it a test.
Since upgrading to Fedora 19 I’ve been working out the kinks. Today I was finally able to run one of my problems down and fix it. It involved the failure of my MTA to deliver mail due to a TLS failure.
This failure was working against both postfix and ssmtp. After much log searching I was able to determine that ssmtp wasn’t verifying the public certificate of the distance SMTP server against the CA certificates I have on my system. I was able to confirm that the problem existed on other Fedora 19 systems and that it wasn’t just my crazy setup. After working with a couple of developers it seems that the ssmtp configuration file now requires the entry “TLS_CA_File=/etc/pki/tls/certs/ca-bundle.crt” to function correctly. It is not currently known what changes were made that created this problem.
I have not troubleshot postfix as of yet but I suspect a similar solution will be needed.
I went to sign an outgoing message tonight and my Gemalto USB Shell Token wouldn’t light up when I plugged it into my USB port. After doing the typical troubleshooting I am left with the thought that the device has given up the ghost. This isn’t a big problem because I saved the card the SIM came out of and I’m able to use my token on my personal laptop with a traditional card reader. My work computer, however, does not have one of these fancy card readers (maybe I can find my USB one somewhere?).
I can buy another Gemalto device but I’m wondering if there is a better device to use? I mean, the Gemalto lasted almost 500 signatures. But I guess I can now take advantage of the failure to try something else. Does anyone have any suggestions?
When Fedora Badges hit the streets I was excited. I could see several possibilities in the project and I hoped it would be a good way to recognize people for their hard work. Here’s my take on the program.
What it does
Fedora Badges is a lot like the military’s medal and ribbon award system only a lot cleaner and somewhat less dangerous. Each badge has its own criteria for obtaining it. Take, for example, the “In Search of Bull (Tester I)” badge. To receive this badge all you need to do is test and add karma to one updates-testing updates in Bodhi. That’s it. Do that and you get a pretty badge that looks like:
Rewarding hard work
So like I mentioned before, the Badges project helps recognize people’s hard work. Sure, lots of people (199 as of this writing) qualify for the Tester I badge because over the course of their work in Fedora they’ve tested a package before it was pushed to the repositories. But not many (I count 5) have made it to the “Both Bull and Self Transcended” level which requires testing of at least 250 packages. It takes someone special to achieve that level of
Getting people involved outside their comfort zones
Another thing I like about Badges is that it allows people to see other activities that they may not know about or haven’t felt like they could do. If someone looked at my badge wall they’d quickly see what is easily obtainable with very little skill. Maybe they’ve never edited a wiki page or participated in an IRC meeting but those are two things that anyone can do to earn a badge while being a contributor to Fedora (while you’re at it reset your FAS password). Maybe we’ll get a few more people watching Bodhi for updates to software they use and will be able to give feedback that is helpful to the packager.
Gaming the system
Sure, there will be people out there that will game the system to get badges. But is that all bad? I have found myself wanting to get a Tagger badge but had never gone into that system and really knew little about the program. But I did go in to make a contribution and even if I did tag a few packages just to get a badge I did provide a service towards that project and helped them get a few more packages tagged. The best part is that I gave it a try and found something else I might like doing within the Fedora Project. I wouldn’t have done it otherwise but I might go back to help do more package tagging.
I really like this Badges system and I hope others will take a look at it and perhaps branch out into other aspects of this great Project. From answering questions on ask.fedoraproject.org to submitting builds to koji there is always something else people can explore. Maybe you’ll find something new within the Project to add to your list of activities. I know I have.