Hacker Newsnew | past | comments | ask | show | jobs | submit | more PythonicAlpha's commentslogin

In theory, yes. But currently, there exist enough structural problems, as much I know, that Bitcoin or similar schemes can not replace cash.

Further, even with a total secure system, there will always be the pressure of the governments to control it.


One reason: Using a distribution that uses old OpenSSL versions (see my own post).


According to the info page, SSLv2 can only be disabled on OpenSSL by having the right (newer) version of OpenSSL installed.

I just checked Debian versions.

Wheezy (oldstable): Much to old OpenSSL versions, according to the info site

Jessy (stable): Still to old OpenSSL version.

Stretch (testing): Still to old OpenSSL version.

Sid (unstable): The same version of OpenSSL as Stretch -- Still to old.

What to do?


From the recent Debian security advisory (DSA-3500-1) about this:

"Additionally the EXPORT and LOW ciphers were disabled since thay could be used as part of the DROWN (CVE-2016-0800) and SLOTH (CVE-2015-7575) attacks, but note that the oldstable (wheezye)[sic!] and stable (jessie) distributions are not affected by those attacks since the SSLv2 protocol has already been dropped in the openssl package version 1.0.0c-2."

So it seems that neither Jessie nor Wheezy are affected by this.


Thank you very much!


Typically, most server software has configuration options that allow you to specify which protocol versions are permitted (i.e. ssl_protocols in nginx, SSLProtocol in apache). Sometimes, they also bring defaults that are stricter than what OpenSSL supports by default.

The difference between older OpenSSL versions shipped by distributions and the latest version is not that newer protocols aren't supported, but that they haven't completely removed support for older, insecure protocols. For example, SSLv2 was only disabled by default in OpenSSL 1.0.2g, which was released today. Meanwhile, a lot of server software (e.g. nginx) had it disabled by default for quite some time now.

This is mostly relevant if you have code that uses OpenSSL directly - but then it's probably not a good idea to rely on OpenSSL defaults anyway.

tl;dr Older OpenSSL versions are probably fine as long as your server software has good defaults.


Ok, can you tell in short, which server software is involved?

Nginx is not the only one, I guess. At least ssh should also be in the boat ... and the mail server .... and ....


OpenSSH is a different project that doesn't use OpenSSL, so that's not affected.

As for other software, it depends on the defaults and how their code disables SSLv2 (i.e. whether they just disable all SSLv2 ciphers, or disable the actual protocol with SSL_OP_NO_SSLv2).

Anyway, it's likely that most distributions will backport the fix soon for all supported OS versions (either by disabling SSLv2 too or by including the fix from OpenSSL 1.0.2f that allows SSLv2 handshakes even if SSLv2 ciphers are disabled).


> According to the info page, SSLv2 can only be disabled on OpenSSL by having the right (newer) version of OpenSSL installed.

Not quite. If you disable the SSLv2 protocol, you're fine. If you have the SSLv2 protocol enabled but all the SSLv2 ciphersuites disabled, you're not fine. You can disable the SSLv2 protocol in versions of openssl previous to today's.


Jessie has 5 changesets on top of 1.0.1k which fix 14 CVE's:

http://anonscm.debian.org/viewvc/pkg-openssl/openssl/branche...

And similar for the other debian versions.


Ok, is there any CVE that covers this attack / disables SSLv2?

This is rather in-transparent to me. Would be nice, if somebody could give better advice on this soon.


DROWN is CVE-2016-0800. There are a lot of CVE's in openssl's advisory released 10 minutes ago: https://www.openssl.org/news/secadv/20160301.txt

None are fixed yet of course in debian. And not in ubuntu either: http://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/...


Actually Ubuntu is not affected because it already has SSLv2 disabled: http://people.canonical.com/~ubuntu-security/cve/2016/CVE-20...

You won't see a fix appear in the changelog because there is nothing to fix in the Ubuntu packages.


Disable SSLv2 everywhere.


To make it more clear:

According to the info page, I can disable SSLv2 on OpenSSL only by installing a newer version of OpenSSL, that is not available on Debian (as I found).

(I also updated my original post)


You misunderstand how Debian works.

Debian practically never updates to new versions of software (until you upgrade Debian). Instead they "backport" security fixes into the older software versions, preserving the old version numbers but adding some stuff on the end to reflect Debian's changes. The intent is that you get "only" security fixes, never features or improvements.

So when you see "OpenSSL-1.0.c-stuffgoeshere" you are not looking at "OpenSSL" openssl anymore, but a version that Debian customized, probably to add security fixes. I say "Debian" here, but really most distros do it (RHEL, Ubuntu, CentOS, etc.) I'm just not familiar enough with their processes to comment specifically.

Debian has disabled SSLv2 in its OpenSSL packages since 2010 [0], and if you are running a Debian OpenSSL version later than 1.0.0c-2 your OpenSSL version is not vulnerable. The current version of OpenSSL in stable is 1.0.1k-3+deb8u2, so unless your server has been under a rock for 5 years you should be fine. And if it's been under a rock for 5 years you have a lot of security vulnerabilities to be worried about.

Of course you may have installed OpenSSL from somewhere else, or you may be using some other software for SSLv2 that doesn't involve OpenSSL at all. So merely upgrading your OpenSSL version is not a silver bullet, you need to think about every TLS deployment you have and how it might be used.

More broadly, use this vulnerability as a wakeup call to learn about "where your software comes from", because everybody has a role to play in staying secure, including users. Debian is maintained by volunteers; you might be happier with a commercial vendor who guarantees response times. Debian backports security fixes; you might be happier with a distribution that upgrades to new vendor versions which may have avoided the confusion here.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589706


> you might be happier with a commercial vendor

Might be a viable option.

I just don't know a commercial vendor, that also gives more transparency.

I knew, that there are also fixes from the Debian team, that add to the core functionality. But still my problem is the transparency. It is just very difficult in such a case, to find out the relevant changes, if you lack the time to observe all security changes in the distribution.

When such a thing pops up, like today, it is very tedious work for people like me, to find all the strings involved. So many packages, that can potentially involved, so many applications (eg. WebServer, SSH-Server, ...) and everywhere could be a hole. Here, I would appreciate, some more focused information, about the particular distribution.

I am using Debian because of its good reputation -- but of course if you could point out a commercial distribution with more transparency, it would be worthwhile!


SSLv2 and SSLv3 are dropped at compile time in Jessie.


The point of wealth inequality is, that it is rapidly increasing -- particularly in the last 20 years.

The parent poster implied, that by increasing the wealth of some, all will benefit. In my country, this was not the case in the last 20 years. The middle class that was rather broad and healthy, is loosing particularly in the less wealthy part -- many of those people fall down the ladder and are poor and will be even poorer when they are in old age.

My country once was one of the wealthiest of the world, because many people where wealthy and earned good money. It was unthinkable once, that big parts of the society might be poor or have to live from "soup kitchens" -- today it is reality and all projections show, that it will become even worse!

To be complete: My country is still one of the wealthiest of the world -- but with a much much smaller fraction of people owning the biggest part of this wealth.


> In 1911 the Xinhai Revolution in China, which the quote alludes to, demonstrates what is possible when income disparities reach a tipping point...

That is just the reason, many countries and many people of a specific fraction already arm themselves against revolutions.

What fantastic innovations are robots and drones!


Fun fact: Drones can be disabled by blinding them with excess visual or IR noise, jamming their control signals, or applying a fast-moving chunk of metal of appropriate size.

Further, drones are still limited to mostly open spaces. You can't clear a room with a quadcopter (yet), and a Predator missile strike is just as likely to kill loyal citizens as it is to kill the target.

Tanks are easily outmaneuvered by humans on foot. Planes cannot take a building and leave it intact. Drones have electronic weaknesses in addition to the usual flaws. And nukes are practically a joke--the fallout, physical and political, would ruin any nation.

TL;DR: Drones make terrible soldiers. Why do you think ISIS is still live and kicking?


The mere fact that a military tactic is stupid is no guarantee that it won't be employed.


But a stupid tactic is one that may result in defeat.

Sun Tzu's slightly-less-famous quote--"If fighting is sure to result in victory, then you must fight"--has two meanings, like a lot of Asian philosophy does. The obvious part is, as the saying goes, sieze the day. The less obvious part is that you should only sieze the day if you know you can hang onto it.

In the case of nukes, only a damn fool would nuke his own food supply or factories, or perhaps a spiteful loser.


Good, that the usage of antibiotics is rising in cattle-breeding.

The blind usage of the fruits of progress is one of our biggest problems in a world, where many problems of human beings have relieved by the same.


The problem is, in a world, where profits are the most important thing and everything else is secondary, human life does not count -- even when human health is destroyed, it can be good -- to increase the profit margins of some corporations.


Even when it was successful for some things ... when it hurts innocent people, the state has to find other tools to hunt down criminals.

You can't simply drop an atomic bomb on NYC -- and justify it, by saying you killed at least 100,000 criminals ...


I'm not sold that civil forfeiture is an atomic bomb. It's more like guns in the hands of police. It's a very dangerous tool in the hands of people who are charged with achieving something that occasionally needs dangerous tools to solve.

Guns have obviously led to killing innocents by police, and I'd like that number to go down. Heck, I'd like most police officers to not carry guns most of the time, leaving guns to SWAT teams that can be called in when needed. In other words, I want the dangerous tool used effectively in a manner that respects everyone's rights.

Same with civil forfeiture. It's clearly being used in an abusive fashion. Innocents are losing money and property to help pay for police. It blows my mind that it's being used this way and needs to be reformed. To me it would make sense to hold the property in some form of escrow until the finding of guilt or innocence, essentially freezing assets.


I did not say, that cf is an atomic bomb. I just wanted to use a picture to make it more clear, that the end does not justify all means.

I don't know, if cf can be reformed, so that it stays useful and has not such by-effects. The usefulness of cf is largely drawn from the aspect of being arbitrary.

The side effect of a constitutional state is, that some times the bad guys can use it to protect their bad ways. But the alternative would be bad for all.

cf does not only make innocent people to victims, but does change those to crooks, that should protect the innocent -- and thus an even bigger harm is done to the whole society -- with very bad consequences in the long run!


And still, Ronald Reagan is one of the most popular presidents of the US in the last 100 years.


You have to remember what the country was like at the end of Carter's term to understand why he's so popular.


Perhaps to people that guzzle talk radio whatever News Corp puts out. But to anyone else? Average at best.


The Prohibition of the state grabbing the possession of innocent people dates back to the Magna Carta and thus to the foundations of the legal systems of our civilization.

This practice simply is breaking the civil pact that holds together our countries.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: