It is now a little more than a week since 13.1 was released. There are things that one only notices with sustained use. So, here, I’ll mention some of what I have been noticing since switching my main desktop over to 13.1.
This one is really good news. Konqueror has been running continuously for over three days, with nary a problem. Previously, it was likely to crash after 12 hours or less, and sometimes it would crash when minimized. It looks as if a long standing bug has finally been fixed.
Normally, I close and reopen the browser once per day, as a way of deleting session cookies (and thus reducing tracking). But I’ve kept it open to see how long it lasts. I will close it shortly after posting this.
In my previous post, I indicated that I would report on any glitches.
This will be a short post. I have installed on four different machines. The install went as smoothly as any.
I did run into one glitch, with ecryptfs. And that showed up on all of the installs. When installing from the DVD (which I did, except I “burned” to a USB), you cannot directly include “ecryptfs”. That software is in the repos, but not on the DVD. So, technically, this was a post-install glitch.
I used Yast software manager to add ecryptfs. After adding it, I noticed that the pam configuration had not been updated. The result is that login does not automatically decrypt the Private directory.
The problem is easily corrected by running (as root)
# pam-config -a --ecryptfs
With that change, everything has been just about perfect. Well, Apper is still a bit flaky, so I’ll probably turn it off.
I began downloading at shortly after 6 am (Chicago time) this morning. That’s 12:00 UTC. Download is proceeding smoothly at just below my max Internet speed.
I have already been running 13.1 on my test systems. I had installed from RC2 (release candidate 2), and then updated as updates became available. So those installs should be updated to the final release version. I still need to install for my main desktop system, and I’ll reinstall the final release on a couple of other systems.
Happy downloading and installing.
If I run into any install glitches, I will post on those.
From the factory mailing list, I see this message:
Subject: openSUSE:13.1 is locked Further updates to 13.1 will happen through the update repo - and we already have quite some updates pending for GA.
That’s an excerpt from the email.
To summarize, 13.1 has reached its final stage. All that remains is to prepare the distribution media (the “iso” files), have them picked up by mirrors, and then it will be available. In the above email, “GA” means General Availability. The release schedule has a date of Nov. 19th for that. There are still fixes needed, but they will occur by updating your system after installing.
In case you have been wondering what ECC is, here’s a pretty good overview:
h/t Bruce Schneier
A little background
Most encryption that we use is symmetric encryption, with algorithms such as AES. It is called “symmetric encryption” because the same key is used for both encryption and decryption. And that requires that both sender and receiver share a common encryption key.
The big problem with symmetric encryption, is with the key exchange needed for that shared encryption/ decryption key. If somebody can spy on the key exchange, then the encrypted session is compromised. That’s where public key encryption comes in. With public key encryption, there is no shared key. There is as pair of keys, one made public and the other kept secret.
Elliptic Curve Cryptography, along with RSA and Diffie Hellman, are public key methods. They are typically used to exchange symmetric encryption keys.
Release candidate 2 was made available yesterday. As you might expect, I have already downloaded it and attempted a couple of installs.
This seems to correct most of the problems with earlier pre-release versions. The installed system is running kernel 3.11.3. KDE is at version 4.11.2 and Gnome is at version 3.10.1. The release will have code name “Bottle”, and is expected to be an LTS release. That is to say, after the normal end of support, it will go to evergreen extended support. Read More…
Today, I tried “upgrading” my Win 8 box to Win 8.1. It did not go well.
First a little background. I was looking for a replacement linux box. It turned out that I could get a better price for a box with Win 8 preinstalled, than for a box without Windows (or with linux). So I went with Win 8.
I could have deleted Win 8, but decided to keep it, to gain experience with dual booting Win 8 and linux in a UEFI box. I have not had any actual use for the Win 8 system.
However, I am not seeing that problem. Right now, I can see the tray icon for liferea 1.8.14, while I am running KDE 4.10.5 (under opensuse 12.3). On another computer, I can see the tray icon for liferea 1.10.2 under KDE 4.11.2 (using opensuse 13.1 RC1).
Bruce Schneier has a new blog post:
It’s about a new research paper on the weaknesses of random number generators such as the one use for “/dev/random” and “/dev/urandom” in linux. Check Schneier’s post for the abstract of the paper, and a link to the full paper.
Thus far, I have only skimmed the paper, so I won’t be explaining it here. But I shall use this post to explain why it is important.
The main use of random numbers is in cryptography.