Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux.mageia > #20243
| From | Jasen Betts <jasen@xnet.co.nz> |
|---|---|
| Newsgroups | alt.os.linux.mageia, alt.os.linux |
| Subject | Re: Accessing Hunt's pwned database. |
| Organization | JJ's own news server |
| Message-ID | <q2tor4$rg7$1@gonzo.alcatraz> (permalink) |
| References | <q2q5op$j03$1@dont-email.me> <87womm5xms.fsf@LkoBDZeT.terraraq.uk> <q2rvcd$nep$1@gonzo.alcatraz> |
| Date | 2019-01-31 03:08 +0000 |
Cross-posted to 2 groups.
On 2019-01-30, Jasen Betts <jasen@xnet.co.nz> wrote: > On 2019-01-30, Richard Kettlewell <invalid@invalid.invalid> wrote: >> William Unruh <unruh@invalid.ca> writes: >>> Here is a bash script to impliment this. >>> >>> >>> #!/bin/bash -x >>> T=/tmp/t1 >>> read -s -p Password: passwd >>> echo >>> hash=`echo -n "$passwd"|sha1sum|tr 'a-f' 'A-F'|sed 's/^...../& /g'` >> >> This not a secure approach. The candidate password will briefly appear >> in ps output. >> > > > hash = $( (tr -d $'\n' << pwd > $passwd > pwd > ) | sha1sum | tr 'a-f' 'A-F'|sed 's/^...../& /g') > > > blech! > > maybe there's a better way. > there is: echo -n Password: # turn off input echo stty -echo # read a single line, trim the newline, hash and slice. hash=$(head -1 | tr -d $'\n' | sha1sum | tr 'a-f' 'A-F'|sed 's/^...../& /g' ) stty echo # move cursor to next line echo this one supports leading and trailing spaces on the password. but pwned database doesn't seem to include any password like that. -- When I tried casting out nines I made a hash of it.
Back to alt.os.linux.mageia | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-29 18:24 +0000
Re: Accessing Hunt's pwned database. Jasen Betts <jasen@xnet.co.nz> - 2019-01-30 02:54 +0000
Re: Accessing Hunt's pwned database. Richard Kettlewell <invalid@invalid.invalid> - 2019-01-30 08:59 +0000
Re: Accessing Hunt's pwned database. Jasen Betts <jasen@xnet.co.nz> - 2019-01-30 10:47 +0000
Re: Accessing Hunt's pwned database. Richard Kettlewell <invalid@invalid.invalid> - 2019-01-30 11:05 +0000
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-30 18:06 +0000
Re: Accessing Hunt's pwned database. Richard Kettlewell <invalid@invalid.invalid> - 2019-01-30 20:02 +0000
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-30 22:41 +0000
Re: Accessing Hunt's pwned database. Richard Kettlewell <invalid@invalid.invalid> - 2019-01-31 08:24 +0000
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-31 16:50 +0000
Re: Accessing Hunt's pwned database. Richard Kettlewell <invalid@invalid.invalid> - 2019-02-01 14:19 +0000
Re: Accessing Hunt's pwned database. Jim Beard <jim.beard@verizon.net> - 2019-02-01 14:45 +0000
Re: Accessing Hunt's pwned database. Richard Kettlewell <invalid@invalid.invalid> - 2019-02-01 15:06 +0000
Re: Accessing Hunt's pwned database. "Carlos E.R." <robin_listas@es.invalid> - 2019-01-30 23:23 +0100
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-30 22:43 +0000
Re: Accessing Hunt's pwned database. "Carlos E.R." <robin_listas@es.invalid> - 2019-01-31 03:03 +0100
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-31 02:11 +0000
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-30 20:16 +0000
Re: Accessing Hunt's pwned database. Jasen Betts <jasen@xnet.co.nz> - 2019-01-31 03:08 +0000
Re: Accessing Hunt's pwned database. William Unruh <unruh@invalid.ca> - 2019-01-31 04:18 +0000
csiph-web