On Thu, Nov 04, 1999 at 08:55:50PM -0500, Greg Wooledge wrote
> Pann McCuaig ([EMAIL PROTECTED]) wrote:
> > On Wed, Nov 03, 1999 at 22:24, Greg Wooledge wrote:
> > > Pann McCuaig ([EMAIL PROTECTED]) wrote:
>
> > > > What do you call "discovering" a weak password using the tools created
> > > > for
Pann McCuaig ([EMAIL PROTECTED]) wrote:
> On Wed, Nov 03, 1999 at 22:24, Greg Wooledge wrote:
> > Pann McCuaig ([EMAIL PROTECTED]) wrote:
> > > What do you call "discovering" a weak password using the tools created
> > > for that purpose?
> > It is most certainly not decryption. We usually call
On Wed, 3 Nov 1999, Pann McCuaig wrote:
: On Wed, Nov 03, 1999 at 22:24, Greg Wooledge wrote:
: > Pann McCuaig ([EMAIL PROTECTED]) wrote:
: >
: > > What do you call "discovering" a weak password using the tools created
: > > for that purpose?
: >
: > It is most certainly not decryption.
On Wed, 3 Nov 1999, Pann McCuaig wrote:
: On Thu, Nov 04, 1999 at 00:40, Oliver Elphick wrote:
:
: > Strictly, password encryption is authentication, rather than encryption,
: > because password encryption is one-way: you cannot decrypt a password.
:
: Well, yes, but . . .
:
: What do y
On Wed, Nov 03, 1999 at 22:24, Greg Wooledge wrote:
> Pann McCuaig ([EMAIL PROTECTED]) wrote:
>
> > What do you call "discovering" a weak password using the tools created
> > for that purpose?
>
> It is most certainly not decryption. We usually call it "cracking",
> or more specifically, "brute-
Pann McCuaig ([EMAIL PROTECTED]) wrote:
> What do you call "discovering" a weak password using the tools created
> for that purpose?
It is most certainly not decryption. We usually call it "cracking",
or more specifically, "brute-force cracking".
--
Greg Wooledge| "Truth be
Pann McCuaig wrote:
>
> On Thu, Nov 04, 1999 at 00:40, Oliver Elphick wrote:
>
> > Strictly, password encryption is authentication, rather than encryption,
> > because password encryption is one-way: you cannot decrypt a password.
>
> Well, yes, but . . .
>
> What do you call "discovering" a
On Thu, Nov 04, 1999 at 00:40, Oliver Elphick wrote:
> Strictly, password encryption is authentication, rather than encryption,
> because password encryption is one-way: you cannot decrypt a password.
Well, yes, but . . .
What do you call "discovering" a weak password using the tools created
for
"Jens B. Jorgensen" wrote:
>Most likely because it uses some kind of regular DES which isn't strong enou
>gh to fall under
>export controls.
Strictly, password encryption is authentication, rather than encryption,
because password encryption is one-way: you cannot decrypt a password.
Most likely because it uses some kind of regular DES which isn't strong enough
to fall under
export controls.
Sami Dalouche wrote:
> Hi everyone,
>
> Today, I've just realized that the passwd package uses encryption. The
> problem is that I wonder why it's not in the non-US section.
> Every pack
Butch Kemper <[EMAIL PROTECTED]> writes:
> I know how to propagate the password file to the second machine but the
> problem I have not solved is how to have both machines use the same "seed"
> for encrypting the passwords. Right now, if I add a user to machine A and
> copy their encrypted passwo
On Wed, 21 Jan 1998, Craig Sanders wrote:
> how do you convert a passwd/shadow file to md5 passwords?
>
> say i've got a shadow file full of old-style crypted passwords, how do i
> convert them all to md5crypt (without having to know what the plaintext
> password is)?
I dont think that is poss
On Tue, 20 Jan 1998, Scott Ellis wrote:
> On 20 Jan 1998, Torsten Hilbrich wrote:
>
> For the most part, shadow aware libc6 programs should recognise md5
> passwords, since libc6 includes a transparent crypt function that
> recognises a md5 salt and does the crypt accordingly. Programs that
> do
On 20 Jan 1998, Torsten Hilbrich wrote:
> In BO with libc5 I had trouble with a lot of programs that they don't
> recognize any other password system than no-shadow and shadow. For
> example, su and xlock didn't worked with md5 activated.
>
> Will these problems has been gone with hamm and libc6
On 20 Jan 1998, Torsten Hilbrich wrote:
> Will these problems has been gone with hamm and libc6? I would really
> prefer a password system with more than 8 significant characters in my
> passwords.
libc6 supports MD5 passwords (almost) transparently. There may be some
stupid programs that do thi
15 matches
Mail list logo
