Doesn't matter, I'm in the targeted group. I assume the worst because being compromised is a zero-sum game. What are the chances you were in the part of the barrel they scraped? For a small list of unknowns:ģ) What software/websites/people are they choosing to attackĤ) Are you even using any of the software/websites that are being attacked?ĥ) Are they going to accept cracking 50%~ accounts? Many crackers only care to scrape the bottom of a barrel. The chances of 0 becoming 1 are not quantifiable because it requires knowing unknowns. I'm worried about given that they do exist what is the risk to me? What is the likelihood that my account has been broken into? To my understanding, they would not require physical access and would be able to guess any passwords generated (once an attack has been found/created). So I'll let someone else quantify potential specifics. I'm not a security expert, more of a hobbyist. Some require physical access some do not. Rather than worry about whether or not a practical attack already or will one day exist, I'd use cryptography that hasn't been shown to be broken. Therefore when something is shown that "attacking it is possible" you can make one of two assumptionsġ) No practical attack exists and you'll be safe until it existsĢ) A practical attack already exists and it is only a matter of time until you get pwned
#KEEWEB REVIEW CRACKER#
By the time the threat level hits 100% the cracker may have already broken into your account(s) before you even hear about the attack.
There is no guarantee that a practical attack exists that hasn't been brought to academic or mainstream attention (e.g some cracker has a practical attack that they're keeping under wraps). This threat level immediately goes to 100% when a practical attack is discovered. In order to gauge that, I need a little more info about the threat level. I care about whether the existence of the bug is something I should be so concerned about as to not use the software. >I don't care about why the bug happened or how easy it is/isn't to fix.
0 kommentar(er)
