Slashdot Mirror
FreeBSD-Current Random Number Generator Broken
First time accepted submitter bobo the hobo writesThe FreeBSD random number has been discovered to be generating possibly predictable SSH keys and SSL certificates for months. Time to regenerate your keys and certs if using FreeBSD-Current. A message to the freebsd-current mailing list reads in part: "If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys. I discovered an issue where the new framework code was not calling
randomdev_init_reader, which means that read_random(9) was not returning
good random data. read_random(9) is used by arc4random(9) which is
the primary method that arc4random(3) is seeded from."
I discovered an issue where the new framework code was not calling randomdev_init_reader
So who was responsible for introducing that change? Let's smoke out the mole.
I've heard the same things said. However, and I don't say this in jest, that while no security in any OS is perfect, OpenBSD comes the closest due to their audits. Hence, out of the BSDs I do use and endorse, it's OpenBSD.
Some dislike Theo, but he's intensely good at running a tight ship, and since 1999 when I first started using OpenBSD for security-based boxes, I've never had an issue.
since 1999 when I first started using OpenBSD for security-based boxes, I've never had an issue.
That you know about.
According to many people on this site almost every Linux user have now switched to FreeBSD because of Systemd.
The -current is not a release — it is the trunk of the development tree. Using for anything important — such as data, that may be worthwhile enough for your enemies to hack for — is silly. Far worse bugs may exist in -current — or be introduced at any point.
Stick to releases — or one of the -stable branches — for anything, that's not about working on FreeBSD itself.
In Soviet Washington the swamp drains you.
Bleeding edge software has bugs?? what
All of these problems will be solved when systemd integrates Rand
No, you should be on -STABLE or at least RELENG_? if you only want security fixes. -RELEASE is just that, the release version, no updates.
The bug was in the unreleased FreeBSD-11 work-in-progress developer tree.
If you are running an actual release, or one of the stable branches, you are not affected.
The main cause for concern is if you are generating keys in some form on the developer tree.
FreeBSD is the new Linux. Full of religious fan boys who act like it was written by God. This old tired line of "Linux is immune to security issues" is now more commonly used with FreeBSD (by idiots).
You know who started the original BSD? This guy did. He also created the original vi editor, was the creator of the modern day TCP/IP stack, and had a huge hand in the creation of Java. What, praytell, have you done?
"Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
Why do I get both my 7 mana-cost cards on my first two draws?
Why does the best card in my hand always wind up being the card that gets discarded on random discards?
Why is the board-clear that I need always at position 30 in the draw pile?
It is because they built their server backend on FreeBSD!
It is all so clear now.
This seems like an odd bug to have happen, how bad were the effects? Just 'weaker' randomness, or without randomdev_init_reader do the random routines just return the same series of pseudorandom digits every time?
Also, obligatory Dilbert reference
I do not deploy Linux. Ever.
I just checked on openbsd.org, and I loved the FAQ section! ...
4.13 - Common installation problems
4.13.1 - My Compaq only recognizes 16M RAM
4.13.2 - My i386 won't boot after install
When blackboxed, even "return 5" is indistinguishable from a true random number generator.
People want noisy numbers, not random numbers. Which is a good thing, because a true random number generator will never exist.
So who cares??
http://saveie6.com/
Just don't use keys for remote ssh logins. I know, keys are supposed to be all that any more. But based on my experience fending off billions of script kiddy attempts from my home system, it appears they aren't worth the effort and may even be counter productive.
I say this because my home server faces the world and allows anyone who wants to, to make an attempt to login via ssh on port 22. You may say this is completely insane, but my logs suggest it isn't that bad. The overwhelming majority of all attempts on my system attempt to come straight in as root. As everyone knows, you can very easily disable root login in your sshd.conf file which leaves the person on the other end completely incapable of knowing whether or not they ever got your root password right as the response is the same.
The end result is they make their 10,000+ attempts in a couple hours, then leave and never come back. They might take a few parting shots at other well known account names but they won't get in that way either.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Netcraft Confirms FreeBSD is dying
Facebook is too confusing!
Don't you have a Twitter link to share?
You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
No, and who mods this "Informative"?
Both -CURRENT and -STABLE are development branches.
-RELEASE is meant for production and of course gets supplied with security relevant fixes (then referred to as patchlevels).
But yes, please go on educating people about things you don't know jack about.
CLI paste? paste.pr0.tips!
As apparently nobody bothered to find out, this is a bleeding-edge developer snapshot, not anything that was in any way "released", hence no normal users are affected.
I do have two questions though:
1. Why was that code touched in the first place?
2. Who touched that code and broke it?
It may be simple incompetence (it usually is), but it may also be a mole in the FreeBSD project. It should be ascertained that the person that did this did so in good faith. Still, some level of shaming is required even then to make people pay attention when they touch security-critical code and keep their fingers off it unless they have the required level of skill and understanding and there is actually a real need to touch that code.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
This guy is the low hanging fruit that keeps all those automated attacks from China from developing something more sophisticated :P Not that i'm suggesting security through obscurity is the only way or anything... just an extra line of Darwinian defence.