because the larger an epidemic grows the more expensive it is to deal with and the greater the chance of an infected person escaping and starting an outbreak elsewhere. The ebola epidemic got big enough to suck badly for the three main countries involved and there were a few minor outbreaks in other countries but fortunately the outbreak was contained in time to avoid any signficant outbreaks in the rest of the world.
2K had rail, dunno about the original.
If the shit hits the fan at a domain registrar there is a good chance your domain will remain active but with no way to reconfigure it until things are straightened out. If the shit hits the fan at a hosting provider there is a good chance your server will disappear.
So putting both at the same place seems stupid to me.
My question is how could OpenSSL still have had this potential backdoor? Why was this not removed at first opportunity?
The trouble with removing old/weak modes is that you break interoperability with systems that only support those modes. Implementations that were limited to export modes only didn't disappear the instant the export restrictions were lifted. In some cases old versions of software stick around for many years because there is some problem that blocks upgrading.
So someone has to make the difficult call as to when the risk posed by supporting the old/weak modes outweighs the interoperability issues that will be caused by removing support for them. Inevitablly making changes is harder than doing nothing so said calls tend to err on the side of "too late" rather than "too early".
Furthermore SSL/TLS is supposed to protect against downgrade attacks. So removing support for old modes doesn't seem as urgent as it otherwise would be. Recently however we are finding that the protection against downgrade attacks is not as good as it should be.
The thing is with a petrol/diesel/lpg/etc powered car you can drive until the tank is nearly empty. Then at a conviniant location along the route stop, fill the fuel tank, go to the toilet, stretch grab a snack etc and be back on the road quickly. Especially if you have more than one person in the car and so can share the burden of driving this allows travelling for long periods with minimal stopped time.
With an electric car so far you can't do that. You have to go out of your way to find a charging station (which are far less common than petrol stations) and then wait a considerable time for your vehicle to charge (how long depends on the particular station but even tesla superchargers which are few and far between apparently take 40 minuites to bring the car to 80% charge)
What about vets? do they take any oaths that would prevent them acting as executioners or assisting in the planning?
Like all companies, they are worth what someone is willing to pay.
And like all companies some sucker paying $x for y% of of the company does not imply that there is anyone who will pay $(x*y/100) for the whole company.
time_t has been 64 bits on every *nix system I've used for over a decade.
all widely used 32-bit linux ports still have 32-bit time_t (x32 has 64-bit time_t but that is not widely used and it's debatable whether it counts as a 32-bit system). While x86-64 is taking over on the desktop and dedicated servers many embedded systems and low cost hosted vms are still 32-bit (the latter due to the lower memory footprint).
Why in the name of any sanity at all would NTP not have been updated by now?
Afaict it has, the NTP "DATE" format provides a 32-bit era number and a 32-bit era offset number which between them provide a 64-bit seconds count. The NTP "timestamp" format uses a 32-bit seconds count but AIUI that is only supposed to be used for comparing to other nearby timestamps.
On the other hand in a language like C or java any code that needs to work with a custom numeric type (complex numbers, integers modulo something other than a power of 2, integers larger than the compiler supports, matricies etc) becomes a horrible mess of function calls (or macros in the case of C) that obscure the maths you are trying to write/read.
Chrome/chromium stopped working properly on at least some systems running kernels without the tsync feature (which is a very new feature). At the time people assumed that google was intentionally requiring the new feature. Chromium is one of those programs where the only reasonable way to support it is to keep upgrading to new upstream versions. Even Debian breaks from their normal policies when it comes to major web browsers.
It's one thing to break with your normal policies of "security and major bugfixes only" for updates to a web browser. It's altogether more contraversial if doing so requires making changes to core system components to support said web browser hence why this situation blew up a few days ago.
Google has now clarified that chromium is supposed to work without the kernel feature in question.
Where things get tricky is the "mere aggregation" clause in the GPL. AIUI a storage or distribution medium containing two unrelated programs is a derivative work of both those programs but thanks to the "mere aggregation" clause it's perfectly OK if one of those is GPL and one is propietary.
So the question becomes what level of interaction/interconnection/integration does there need to be between two works distributed together such that they no longer satisfy the "mere aggregation" clause and hence violate the GPL. This becomes especially tricky if the interface definition is under a GPL-compatible non-copyleft license such that both the GPL and propietary work could have been created without reference to the other. There is also the question of whether interfaces are copyrightable at all (see the recent oracle VS google lawsuits).
Heres an article from 2009 which talks about similar things happening in Dubai.
Just configuring openssl is not enough. Theres at least THREE different SSL libraries in common use on linux and the chances are you have applications using all of them.
The SSL implementation is NOT part of the kernel.
uhhh.. it's actually very hard to find a modern motherboard which still has an LPT port..
No it isn't. I just looked at LGA1150 boards on newegg, sorted by price and found serveral with paralell ports on the first page.
The most difficult thing in the world is to know how to do a thing and to watch someone else doing it wrong, without commenting. -- T.H. White
