|
Members in Shoutbox
None.
Shoutbox Search
Shoutbox Commands
/w [name] > Whisper
/r > Reply to last whisper /me > Marks as action Shoutbox Information
Moderators may delete any and all shouts at will.
|
Global Shoutbox
Please log in to shout.
[2017-10-18. : 8:48 am] Lanthanide -- well actually, this being in the mirror universe would explain a lot...[2017-10-18. : 8:48 am] Lanthanide -- don't the star trek writers know that they're only allowed gaity in the mirror universe?[2017-10-18. : 6:34 am] Lanthanide -- Star Trek's technobabbly often uses the term "protocol' when what they're describing is really an algorithm or procedure[2017-10-18. : 6:34 am] Lanthanide -- the fact he said algorithm instead of protocol isn't material, I was just being a pedant[2017-10-18. : 6:33 am] Lanthanide -- jjf28jjf28 shouted: Lanthanide what's the distinction between protocol and algorithm in this case? in context of what Moose actually said, my correcting him of algorithm to protocol was immaterial; his main point is that the implementations had bugs in them, but actually it's the opposite case - any implementation that correctly didn't have bugs would be vulnerable[2017-10-18. : 6:31 am] Lanthanide -- TCP 3-way handshake requires a SYN to be followed by a SYN-ACK, any other response is incorrect according to the protocol[2017-10-18. : 6:30 am] Lanthanide -- a protocol is a set of rules and guidelines for how to carry out a conversation[2017-10-18. : 6:30 am] Lanthanide -- jjf28jjf28 shouted: Lanthanide what's the distinction between protocol and algorithm in this case? an algorithm is when you have data and some instructions to follow, you 'crank the handle' and the algorithm gives you a result of the input you gave it[2017-10-18. : 1:39 am] O)FaRTy1billion[MM] -- CaptainWillCaptainWill shouted: One way of using them is to put them where you'd naturally take a breath while speaking. except then people start putting commas in weird places xD[2017-10-18. : 12:26 am] CaptainWill -- Speaking of chamone https://www.youtube.com/watch?v=zk1C0AhshtU[2017-10-17. : 8:58 pm] Corbo -- and the best thing that has ever happened to building and project management[2017-10-17. : 8:35 pm] CaptainWill -- The only place where a comma would have been best is after "algorithm". It separates the subordinate clause from the main clause. Most people who speak English natively don't actually know this, they just do it through experience.[2017-10-17. : 8:25 pm] CaptainWill -- One way of using them is to put them where you'd naturally take a breath while speaking.[2017-10-17. : 5:19 pm] NudeRaider -- insert commas where apropriate Even in German I'm really bad at correctly placing them and I was told in English it's even more confusing to do it correctly, so I straight gave up[2017-10-17. : 4:59 pm] NudeRaider -- while it's probably technically correct to call it an algorithm in communications a set of intructions on how to exchange information is usually called a protocol[2017-10-17. : 4:10 pm] jjf28 -- it seems to me that the latter is governed by an algorithm as well, and that both together are also an algorithm *shrug*[2017-10-17. : 4:01 pm] NudeRaider -- I read it as the distinction between the math that encrypts the key vs. the process of information exchange during the handshake. The latter is vulnerable to an attack. So while you can't read out the session key (still securely encrypted) you can intercept the encrypted key and use it to inject yourself into the communication stream.[2017-10-17. : 2:06 pm] jjf28 -- LanthanideLanthanide shouted: Mini Moose 2707 actually it's a protocol buy (not an 'algorithm'), so properly functioning implementations were vulnerable. It's only if you had a buggy / incorrect implementation that could make you safe from this bug - but you'd undoubtedly suffer from other issues. That's why *everything* needs patching and why this is so wide ranging. bugs in encryption protocols are relatively uncommon; implementation bugs that are exploited are the norm what's the distinction between protocol and algorithm in this case?[2017-10-17. : 11:50 am] jjf28 -- NudeRaiderNudeRaider shouted: one is not like the others ... https://i.imgur.com/W1qlow1.jpg does the white panel van have candy?[2017-10-17. : 11:07 am] NudeRaider -- lil-Infernolil-Inferno shouted: NudeRaider ya, I've never been to an EB Games ... but you've had fun inside white vans? ![]() [2017-10-17. : 10:11 am] lil-Inferno -- NudeRaiderNudeRaider shouted: one is not like the others ... https://i.imgur.com/W1qlow1.jpg ya, I've never been to an EB Games[2017-10-17. : 5:48 am] Lanthanide -- Mini Moose 2707Mini Moose 2707 shouted: Well, yeah, the algorithm is fine but the implementations were not. Which is why you can get your patches and continue using WPA2 securely. actually it's a protocol buy (not an 'algorithm'), so properly functioning implementations were vulnerable. It's only if you had a buggy / incorrect implementation that could make you safe from this bug - but you'd undoubtedly suffer from other issues. That's why *everything* needs patching and why this is so wide ranging. bugs in encryption protocols are relatively uncommon; implementation bugs that are exploited are the norm[2017-10-17. : 12:23 am] Jack -- If I understand correctly, when the tool clones the network both networks are still there. If the channel that the attacker is on is congested or physically farther away, the real network will be able to send all the necessary packets before the fake one.[2017-10-17. : 12:18 am] Jack -- "We remark that the reliability of our proof-of-concept script may depend on how close the victim is to the real network. If the victim is very close to the real network, the script may fail because the victim will always directly communicate with the real network, even if the victim is (forced) onto a different Wi-Fi channel than this network."[2017-10-17. : 12:16 am] CaptainWill -- Yeah I've connected to open networks before and used wireshark with vpn on and off. Quite interesting output.[2017-10-17. : 12:16 am] Jack -- Also, 4G and wired connections are fine, and theoretically if you're very physically close to the router then you might be OK too[2017-10-17. : 12:15 am] Jack -- so you need to wait for your client vendor to release a patch. Until then you can use a VPN that encrypts everything. Theoretically, HTTPS works too but you can't easily guarantee that it's all encrypted and your PC sends out other traffic besides your web traffic too.[2017-10-17. : 12:13 am] CaptainWill -- So does this attack work at the router end or the client end?[2017-10-16. : 11:37 pm] Moose -- CorboCorbo shouted: Mini Moose 2707 "...attack is excepcionally devastating against linux..." nice os "excepcionally" nice spelling[2017-10-16. : 11:35 pm] Corbo -- Mini Moose 2707Mini Moose 2707 shouted: wpasupplicant package updated for Linux, good luck Windows ROFL "...attack is excepcionally devastating against linux..." nice os[2017-10-16. : 11:19 pm] jjf28 -- If the math is destroyed, then it will fall, and it's fall will be so low that none can foresee it defending networks ever again.[2017-10-16. : 11:15 pm] Moose -- Well, yeah, the algorithm is fine but the implementations were not. Which is why you can get your patches and continue using WPA2 securely.[2017-10-16. : 11:14 pm] jjf28 -- WPA2 is defeated, but not destroyed, so long as the core of the algorithm remains mathematically sound it shall never be truly defeated.[2017-10-16. : 10:05 pm] jjf28 -- https://www.tunnelbear.com/download is a good free option, as per my research earlier this year |
DarkenedFantasies