Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.mageia > #20240

Re: Accessing Hunt's pwned database.

Cross-posted to 2 groups.

Show all headers | View raw

On 30/01/2019 23.43, William Unruh wrote:
> On 2019-01-30, Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 30/01/2019 19.06, William Unruh wrote:
>>> On 2019-01-30, Richard Kettlewell <invalid@invalid.invalid> wrote:
>>>> Jasen Betts <jasen@xnet.co.nz> writes:
>>>>> 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.
>>>
>>> I did think of that but also know that the amount of time it does so is
>>> very small, but could not think of a way of doing so with my knowledge. 
>>
>> I don't think it is an issue, as it runs in your own computer and would
>> only be visible to people with the right access in that computer.
>>
>> Just don't run it on an internet café machine.
>>
> 
> Yes, that was a part of my argument to myself. Mind you, it is always
> better to make sure that insecurities do not exist than to hope that
> noone makes use of them for whatever reason. 

It is no problem at all when run on a computer that you control. There
are other applications that can leak information that way (I think one
of the pgp tools, no less). So, just tell the problem with the code, do
not use on a computer shared with other people, and that's it.

-- 
Cheers, Carlos.

Back to alt.os.linux.mageia | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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