Date: Tue, 18 Jun 2013 03:52:20 +0200 From: Polytropon <freebsd@edvax.de> To: RW <rwmaillists@googlemail.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD maximum password length Message-ID: <20130618035220.2b01f4af.freebsd@edvax.de> In-Reply-To: <20130618005608.488c72a0@gumby.homeunix.com> References: <CAPkyVLw=m5-3HX7YC-Zqm=OgTLMhNYq4trBSWso8qEmPzqV38Q@mail.gmail.com> <44li69diyv.fsf@be-well.ilk.org> <CAPkyVLwNAUU_2E0d8Go6OP4m7jqHeHKCWEt5WRhtYcgRBSQ2nQ@mail.gmail.com> <20130617164744.1c4e3d02e57de825d500e309@yahoo.es> <13CA24D6AB415D428143D44749F57D7201F936C4@ltcfiswmsgmb21> <op.wyt2tgk934t2sn@tech304.office.supranet.net> <13CA24D6AB415D428143D44749F57D7201F93897@ltcfiswmsgmb21> <20130618005608.488c72a0@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
One _little_ terminology detail: On Tue, 18 Jun 2013 00:56:08 +0100, RW wrote: > What's important is the > amount of work needed to evaluate a password in a bruteforce dictionary > attack. I'd say that bruteforce != dictionary. It's bruteforce _or_ dictionary attack instead. A dictionary attack is more sophisticated because it uses words from a dictionary, whereas a _real_ bruteforce will stupidly run through _all_ combinations of the given charsets and length ranges. It will _eventually_ be successful, even if our planet doesn't exist anymore at that time. Finite time, far far away. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130618035220.2b01f4af.freebsd>