9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] offered without comment or judgement
Date: Wed, 30 Jun 2010 12:22:16 -0400	[thread overview]
Message-ID: <AANLkTimOdfnLw03yYAFhJViDi1o_i3fNrI5n3FFidvfl@mail.gmail.com> (raw)
In-Reply-To: <b4d080b142b3f461c31e2bbc4aa840d3@kw.quanstro.net>

2010/6/30 erik quanstrom <quanstro@quanstro.net>:
>> I certainly have several nonsensical words / names for my cats. None
>> of them contain numbers or punctuation or anything associated with a
>> strong passphrase. The longest of these is probably about 12
>> characters. And a system that can try a billion RSA keys per second is
>> going to quickly exhaust the relatively short combination of these,
>> even brute forcing. And you're right -- as I also alluded above, the
>
> assuming the attackers have a dictionary of only 500000 words that
> contains your nonsense words and assuming unicase and no spaces
> or other punctuation you get 18.9 bits/word.  for a neat 3 word phrase,
> that's 56.8 bits.
>
> for a login, that's plenty since there should be some protection
> against password guessers.  general slowness or just a slow connection
> should be enough to prevent 1e9 guesses/sec.

As networks get faster, it becomes more of an issue. Luckily, most
places that have information about you / your money will lock your
account after N invalid login attempts within a certain time period.
The places that don't probably don't matter. But usually there are
easier ways to get that information anyway.

>> People have enough difficulty remembering short passwords. Or creating
>> "good" passwords in the first place. Upper bounds along with enforcing
>> permutations are placed to reduce peoples' likelihood of forgetting
>> them while still providing some level of security. It's not the best
>> approach, but until people start treating passwords like an ATM card
>> with a PIN, it's not going to matter much anyway. (Ignoring that PINs
>> for most cards are only have 9990 or fewer permutations.)
>
> people will learn.  real computer passwords have not
> been common for very long.
>
> also, an atm card is a 2-factor authentication scheme.  and
> you get 3 guesses.  assuming you can steal the card your chances
> of success are about 3/10000.  (wiki says 6/10000 due to unused
> numbers http://en.wikipedia.org/wiki/Pin_number#PIN_security)
>
> a better attack might be to shoulder surf and then socially
> engineer the bank into sending you a card.  say by stealing
> it out of the mailbox.

What people do these days is put magnetic readers on the outside of
the reader you're putting your card through. They store information
about N cards, and then write their own cards based on that
information. There's little guesswork involved; there are plenty of
online shops that don't check CVV or shipping address, especially
internationally.

Then you also have keyloggers and screen scrapers. Lots of ways to get
all that information, very, very easily. Social engineering, indeed,
works charms.

> - erik
>
>



  parent reply	other threads:[~2010-06-30 16:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 22:32 ron minnich
2010-06-28 23:10 ` Ethan Grammatikidis
2010-06-29  2:28 ` Wes Kussmaul
2010-06-29  2:46   ` Stanley Lieber
2010-06-29 17:13     ` Wes Kussmaul
2010-06-29 17:27       ` Devon H. O'Dell
2010-06-29 18:30         ` Steve Simon
2010-06-29 18:41           ` Devon H. O'Dell
2010-06-29 18:57             ` erik quanstrom
2010-06-29 19:13               ` Devon H. O'Dell
2010-06-29 19:32                 ` erik quanstrom
2010-06-29 20:00                   ` Devon H. O'Dell
2010-06-30 11:28                     ` erik quanstrom
2010-06-30 15:22                       ` Wes Kussmaul
2010-06-30 16:22                       ` Devon H. O'Dell [this message]
2010-06-29 20:09                 ` Wes Kussmaul
2010-06-29 21:34                   ` Steve Simon
2010-06-29 19:19         ` Wes Kussmaul
2010-06-29  3:46   ` erik quanstrom
2010-06-29  8:07 ` Akshat Kumar
2010-06-29  9:14   ` hiro
2010-06-29  9:17     ` erik quanstrom
2010-06-29 19:59     ` ron minnich
2010-06-29 13:43 ` Gabriel Díaz
2010-06-29 16:54   ` hiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimOdfnLw03yYAFhJViDi1o_i3fNrI5n3FFidvfl@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).