Комментарии:
Can someone give a proper intuitive explanation for this? I just tried it myself, randomising the last 512 bits and it found the result in the first step of ceil(sqrt(n)). How can it pinpoint to the solution so easily.
ОтветитьInteresting that you only have <d> in the private key, all the reference implementations I've found (and the one ChatGPT spat out) all have a two-part private key, made of (<n>, <d>) and also using both…
ОтветитьWhy is 65537 the best integer?
Ответитьplease make a cryptography playlist of Dr. Mike Pound videos
ОтветитьYou explained very well for a person that doesn't know anything about math
ОтветитьNot sure if anyone has mentioned this, but I love how you've repurposed continuous feed (dot matrix) paper! Also, your writing is so clean and legible, which makes it perfect for this application!
ОтветитьWhilst it is true in practical terms, as any odd number can indeed be written as a2-b2, if N is divisible by 2 and not 4 (6 = 3 * 2, or 14 = 7 * 2), the statement that "any composite number N can be written as the difference of two square numbers" is not true. Again, in the case of RSA, this is a non issue since for this not to work, p or q must be 2 (the only even prime), which is obviously a terrible idea.
ОтветитьA side note - any modulo with a prime base creates a group under multiplication, which is why you mentioned finding the inverse of phi_n - I think this is an awesome example of pure maths such as group theory actually being used in action! :)
ОтветитьAwesome video, however u cant apply this formula u made (N = a² - b²) for all cases... just the one you picked ;)
ОтветитьWow! There should be some software that confirms a public key is strong.... I'm guessing this already exists.
Ответитьso the lesson here is to mind your Ps and Qs
ОтветитьThat dot matrix printer paper though.
Ответить"I'm not a genius, it just wasn't difficult". I'm using this
ОтветитьDefinitely stealing this method for CTFs. I've been using a number field sieve to factor low-bit modulo numbers. This is awesome!
ОтветитьThe good news is since getting the weak primes out of the keys is so trivial, it's equally trivial to make a test at key creation and just reject the keys and start over.
ОтветитьSo. How is openssl generating p, q?
Ответитьplz ! i hope you make a video about chacha20/xchacha20 cipher with more details !!
Ответитьput your key away, waltuh; I don't wanna exchange with you, waltuh;
ОтветитьNot good tutorial. Don’t explain how to break internet.
ОтветитьWhen I started following Numberphile I couldn't understand what was all the fuss about with the primes. Then I started following computerphile and it slowly started to make sense.
ОтветитьThanks Peter Parker
ОтветитьI thought it was Elijah Wood explaining rsa
ОтветитьFermat is pronounced "Fer-mah"
ОтветитьWow YT video compression hates ur sweater.
Ответитьthat is so clever! omg
ОтветитьProtect this man at all costs.
ОтветитьI don't understand one thing though, 1 mod anything is always 1 right? So what's the point of writing 1 mod (euler totient (n))?
ОтветитьHow do we know if our RSA implementation avoids this? Could NSA sneak something in that causes this weakness?
ОтветитьGenerate the primes.... do this test to 100 iterations. if it fails throw them out, if it passes keep them. ???
ОтветитьThis is exactly the reason why one must never implement cryptographic algorithms as they are explained in textbooks. They lack all these real world tweaks which are necessary to prevent very specialized attacks for specific cases.
There even have been smartphone apps in the past (sorry for not remembering the names - they were short lived), where cryptographers essentially criticized exactly that: It was a textbook implementation which does not hold up against real world scenarios, resulting from specific hardware, bad random number generators, limited memory, similar user mindsets, etc...
Very nice! A video with a practical example! Not only dry theory as most of your videos.
ОтветитьCommon factor attack: Given two private keys n1 = p * q1, n2 = p * q2, using the same p, then p = gcd(n1, n2), which is easy to compute with Euclid's algorithm, then q = n / p.
This actually happened for a large number of public keys in the wild, that had been generated using a faulty prime number generator. This finding was revealed in a paper from February 2012.
I have no idea what he’s talking about but I can’t stop watching
ОтветитьThe hilarious part is that, unless it was some clever editing, it took longer to verify that p and q were primes than it did to derive them.
Ответитьclickbait title.
ОтветитьThis demo program would have better when it also printed the number of iterations needed.
ОтветитьI tried many ways, I even modified my iptables rules, firewall restrictions, and all the possible ways, but still I cant get reverse shell. Netcat doesn't listen to my reverse shell, so I stucked in the root me room for more than a week. I need help, please anyone suggest me any ideas to overcome this.
ОтветитьHence P = NP
ОтветитьI cannot watch another second while that marker is making those sounds on that paper. An annoying phobia of mine, don't know why. Even though I really want to watch this well explained, super interesting video.
ОтветитьIs it time to go back to the one time pad, but that of course depends on truly random numbers……
ОтветитьHow fast could you calculate 'd' (public key) when using optimized code for QBit Processor? Even when 'p' and 'q' are "difficult" numbers?
Ответитьplease post more computerphile. I find my computer science classes incredibly boring, but these videos I cant stop watching. Makes me love computers!
ОтветитьWhen you realize it's a coding thing and not about RSA (Republic of South Africa)
Ответить