Slashdot Mirror
New SWEET32 Crypto Attacks Speed Up Deprecation of 3DES, Blowfish (threatpost.com)
Researchers "have devised a new way to decrypt secret cookies which could leave your passwords vulnerable to theft," reports Digital Trends. Slashdot reader msm1267 writes: New attacks revealed today against 64-bit block ciphers push cryptographic ciphers such as Triple-DES (3DES) and Blowfish closer to extinction. The attacks, known as SWEET32, allow for the recovery of authentication cookies from HTTPS traffic protected by 3DES, and BasicAUTH credentials from OpenVPN traffic protected by default by Blowfish.
In response, OpenSSL is expected to remove 3DES from its default bulid in 1.1.0, and lower its designation from High to Medium 1.0.2 and 1.0.1. OpenVPN, meanwhile, is expected to release a new version as well with a warning about Blowfish and new configuration advice protecting against the SWEET32 attacks. The researchers behind SWEET32 said this is a practical attack because collisions begin after a relatively short amount of data is introduced. By luring a victim to a malicious site, the attacker can inject JavaScript into the browser that forces the victim to connect over and over to a site they're authenticated to. The attacker can then collect enough of that traffic -- from a connection that is kept alive for a long period of time -- to recover the session cookie.
In response, OpenSSL is expected to remove 3DES from its default bulid in 1.1.0, and lower its designation from High to Medium 1.0.2 and 1.0.1. OpenVPN, meanwhile, is expected to release a new version as well with a warning about Blowfish and new configuration advice protecting against the SWEET32 attacks. The researchers behind SWEET32 said this is a practical attack because collisions begin after a relatively short amount of data is introduced. By luring a victim to a malicious site, the attacker can inject JavaScript into the browser that forces the victim to connect over and over to a site they're authenticated to. The attacker can then collect enough of that traffic -- from a connection that is kept alive for a long period of time -- to recover the session cookie.
Wake me up when SWEET64 is available.
Use this.
This is one of only two ciphers that are public that hasn't been breached. Also, it wasn't invented by NSA, who's mandate is to backdoor and weaken US crypto at all costs. The authors of AES are Belgian. The NSA protested the adoption of AES as a US standard vehemently.
Make up your own mind.
They want to link all of your accounts. Only a state sponsored group would do all of this bullshit to any given person or company or entity.
to wit: US Government
3DES and Blowfish are fine.
>By luring a victim to a malicious site, the attacker can inject JavaScript into the browser that forces the victim to connect over and over to a site they're authenticated to. The attacker can then collect enough of that traffic -- from a connection that is kept alive for a long period of time -- to recover the session cookie.
Use Firefox less than or equal to 45.0 only. Disable all Javascript with the NoScript add-on. In the settings of NoScript remove all default permissions (google, twitter, etc) from the XSS menu and in the ABE menu uncheck all boxes.
https://sourceforge.net/projects/portableapps/files/Mozilla%20Firefox%2C%20Portable%20Ed./
^Use those if you are on any version of 64 bit Windows. Firefox 44.0.2 is your best bet right now. 45.0 removed time spoofing ability. Simply extract to anywhere you want to store the folder and create a shortcut to the executable. Don't update it, so disable all automatic updates. To associate and make as default browser use the stupid ass Windows file association wizard.
https://support.mozilla.org/en-US/kb/how-stop-firefox-making-automatic-connections
^ perform all steps. Import your bookmarks from other browsers etc.
Also you should install Adblock Plus. Import this custom rule set in addition to your Easylist or whichever ones you choose.
http://pasted.co/6aeed3e0
^ simply save as a .txt file and import under Custom filters. It is additional and self explanatory. You can disable/enable on the fly whenever you need google and facebook to track you etc. You *will* need to toggle the dialog box to Custom to import, it is easily overlooked.
Any huge changes of encryption or protocol right now are all social engineering. The US Gov also tried to push for a change to TCP/IP recently.
two words: Fuck. You.
(you should also always keep your PC clock set to fucked up at home unless you need accurate for outgoing email timestamps. Send your email and mess it back up to WAY OFF. It hoses US Government default tracking which is time logging.)
from what i read here, this seems 'practical' only if victim is very stupid and has no common sense practical ability, committing several silly mistakes in succession, from being lured to a fake sites to having full tracking and scripting enabled for all sites etc.
of course, with people like hillary clinton around, who fit that description, this is useful.
too bad being stupid and incompetent seems not to stop the careers( or have any consequence) of establishment elites no matter how many times they are exposed as easy penetrations for hacking or corruption. .
They gave it a name using psychology. What would make the world go OH SWEET I WILL INSTALL THIS?
Mass disconnecting has already been invented, it's called Comcast.
Table-ized A.I.
How will this affect bcrypt? Will the algo need to be redesigned?
-SR
What is this, 2004?
http://blog.cryptographyengine...
Both of the links in the post are useless hot takes, otherwise.
So by your described metric, all of our non-technical families and friends are very stupid and have no common sense practical ability and it's their fault. Who cares, because as techies we know better, and "We're all right Jack." Correct?
Well no, obviously that is not correct, because the Internet is for everybody and not just for techies, and non-technical users should not be placed at risk this way for the "crime" of being non-technical. The blame for this does not lie with them, it lies with the blinkered techies who made this kind of attack possible in the first place.
And that means the morons who added Javascript to HTML. A decade or two ago, the technically competent used to advise everyone never to download and execute untrusted 3rd party programs to their machines, because you'd get exploited in nothing flat. And then the technically competent suffered complete brain death and turned the web into a system where everybody is required to download and execute untrusted 3rd party code on their machines, different untrusted code for every page.
It makes you want to cry for the profession, totally riddled with blindness and incompetence. The blame doesn't lie with anyone else.
"The exploit, dubbed ‘Sweet32’, isn’t easy to carry out, however. It involves mining hundreds of gigabytes of data, and targeting specific users who have accessed a malicious website which saddled them with a bit of malware" ref
First, DES is 56 bit (near enough 60). Triple DES as per first mode (the authorised standard) is 168 bits. The article fails to distinguish, implying the authors are just a little bit naff. 3DES seems to be quite safe, as long as not used in DES emulation mode. And who the hell emulates a mode that was broken in the 80s?
Second, Blowfish was replaced by TwoFish, ThreeFish and Speck. Skein, an entrant to the DES3 challenge, makes use of ThreeFish.
Third, the Wikipedia page states it has been known for a long time that weak keys are bad. This particular attack, though, is a birthday attack. You can find all the ciphers vulnerable or free that you should be using. Anything not on the list is something you are solely responsible for.
http://csrc.nist.gov/archive/a...
In other words, this information is about as useful as telling up that Model T Fords weren't good at cornering at highway speeds. Below are some links, I can't be buggered to HTML-ify them.
https://en.m.wikipedia.org/wik...
http://www.skein-hash.info/
https://en.m.wikipedia.org/wik...
https://en.m.wikipedia.org/wik...
I do not trust most encryption software these days, but that's because programmers these days are sloppy and arrogant.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
See subject: The exact opposite of "security by obscurity" of lesser used OS - malware makers etc. are like pickpockets & don't operate on "crowds of 1 member only" but instead go where the masses are (Windows or on smartphones, ANDROID) for a better "return on investment" of their time & efforts as well as a MORE than potentially better "catch".
* That IS how it is & reality...
(... & not all your attempts @ creating "FUD" can change it...)
APK
P.S.=> It amazes me with the "anti-windows/anti-microsoft" fanboys around here STILL trying that line of bullshit you did - it doesn't work & never really did for anyone w/ an ounce of common-sense... apk
See subject: ~2% only & that's a "social problem" w/ end users (probably pirated too & unpatched) but it's one on android too (due to handset makers not patching from what I've read here & elsewhere online) - how do you stop that?
* Again - it STILL shows you that "most used = MOST attacked" (Windows as a whole, android as well considering it's a LINUX variant no questions asked (as it surely isn't MacOS X/iOS or Windows kernel based)) - which you agreed with no less.
The encryption methods I agree w/ for the MOST part, but what I don't like about secure sockets & encryption is that it ALWAYS gets broken & backward compatibility often doesn't get looked into + passed on for older applications that use it (which breaks them).
APK
P.S.=> Eventually that will pass as far as XP is concerned since it, like DOS/Win3x or even for the most part 9x will be dropped by end users, but what "hits it" as you seem to think (& I do NOT agree with MOSTLY since I've been a professional dev since 1994 & long before it in academia + on my own as well as a network admin & security tech professionally in my time since then) doesn't affect "modern Windows"?
I must differ (Win32/64 code is still often usable from Win9x-most NT series OS for MOST types of wares by virtue of the API itself being MUCH the same (yes, some 'security changes' but not the majority))... apk