Thanks Kris ;) On Wednesday, July 24, 2013 6:14:26 AM UTC+2, Kristopher Micinski wrote: > > The traditional technique is to send a challenge to the person after a > certain number of attempts (e.g., extra information given by the user) > or throttle the number of login attempts after a certain number of > attempts for some amount of time. I know of a few cases (e.g., Virgin > Mobile) where these steps were not taken and many accounts were > compromised. > > Kris > > > On Tue, Jul 23, 2013 at 7:13 PM, Keith Makan > <[email protected]<javascript:>> > wrote: > > Hi Guys, > > > > Quick question, how would you prevent a login app from being > > bruteforce-able? > > Is there anything else I should do besides limit the number of login > > attempts before throwing out a CAPTCHA? > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Android Security Discussions" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to > > [email protected]<javascript:>. > > > To post to this group, send email to > > [email protected] <javascript:>. > > Visit this group at > http://groups.google.com/group/android-security-discuss. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > >
-- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/android-security-discuss. For more options, visit https://groups.google.com/groups/opt_out.
