| 1 |
Again, your not understanding that brute force is not entirely how you |
| 2 |
think it works. As a former employee of a large tech company. They are much |
| 3 |
more cunning how they do it these days.. |
| 4 |
|
| 5 |
If you wanted to break into an account, would you really start with a and |
| 6 |
work your way up? |
| 7 |
|
| 8 |
Come on. |
| 9 |
|
| 10 |
Accounts are broken into all the time and they claimed their passwords were |
| 11 |
awesome.. |
| 12 |
|
| 13 |
Your not an idiot, you just need to do more research on how hackers get in. |
| 14 |
|
| 15 |
On Tue, Nov 10, 2015 at 12:31 PM, Michael Orlitzky <mjo@g.o> wrote: |
| 16 |
|
| 17 |
> On 11/10/2015 02:23 PM, Stanislav Nikolov wrote: |
| 18 |
> > |
| 19 |
> > |
| 20 |
> > On 11/10/2015 09:17 PM, Michael Orlitzky wrote: |
| 21 |
> >> On 11/10/2015 02:00 PM, Jeff Smelser wrote: |
| 22 |
> >>> I guess from this your assuming that everyones passwords that |
| 23 |
> >>> have been hacked are god, birthdays and such? |
| 24 |
> >>> |
| 25 |
> >> Again: assume that I'm not an idiot, and that I know how to choose |
| 26 |
> >> a long, random password. It cannot be brute-forced. And if it |
| 27 |
> >> could, adding an SSH key encrypted with a password of the same |
| 28 |
> >> length would provide no extra security. |
| 29 |
> >> |
| 30 |
> >> |
| 31 |
> > Are you sure you know how such keys work? An extremely 15 character |
| 32 |
> > password (Upper case, lower case, numbers, 8 more symbols) gives you |
| 33 |
> > ~4747561509943000000000000000 combinations |
| 34 |
> |
| 35 |
> |
| 36 |
> And since no one seems to believe me, if you could try a million |
| 37 |
> passwords a second (over the network!), it would take you about |
| 38 |
> 75,272,093,955,210 years to try half of those combinations. |
| 39 |
> |
| 40 |
> |
| 41 |
> |
Archives