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

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

Re: Accessing Hunt's pwned database.

Cross-posted to 2 groups.

Show all headers | View raw

On 2019-01-31, Richard Kettlewell <invalid@invalid.invalid> wrote:
> William Unruh <unruh@invalid.ca> writes:
>> Richard Kettlewell <invalid@invalid.invalid> wrote:
>>> William Unruh <unruh@invalid.ca> writes:
>>>> On 2019-01-30, Richard Kettlewell <invalid@invalid.invalid> wrote:
>>>>> Jasen Betts <jasen@xnet.co.nz> writes:
>>>>>> maybe there's a better way.
>>>>>
>>>>> There is: use a more sensible language than shell.
>>>>
>>>> Helpful aren't you?
>>>> When a hammer is the only tool you have you have to make everything look
>>>> like a nail.
>>>
>>> Personally I prefer to find the right tool for the job. Life’s a lot
>>> better than way. In this particular case, better-design languages are
>>> readily available on Linux.
>>
>> It depends on the job. In this case one would have to learn those other
>> languages first, and that would take days (or weeks or months) and this
>> problem simply is not worth that time committment on my part. 
>> Of course if you happen to know other languages, then using them (the
>> lerning commitment is already in place) is probably a good idea.
>
> Unless you only ever have one problem to solve, the cost of learning new
> languages is ammortized over the whole set of problems you address with
> them.

I am certainly not arguing against learning other languages. But to use
the tools you have readily available to kludge together a solution to a
problem is better than to not do anything because you do not have
exactly the right tools at hand. 
>
>> It is like, you have a hammer, and if you were to use some other tool
>> you would first have to make the tool (eg smelt some steel, create a
>> rod, and then file down the rod to make a screwdriver).
>> It is not the availability of the language, but the knowledge of how to
>> use the language that is the impediment.
>
> I’ve not encountered anyone arguing in _favour_ of “when the only tool
> you have is a hammer, every problem looks like a nail” before. Usually
> it’s seen as something to avoid.

I changed it to "every problem must be made to look like a nail"
So when one of our favourite posters wrote his programs in ADA, you
rushed out to learn Ada in case it was useful for many other programs?

In this case Jason improved my version in bash sufficiently that it now
looks reasonable (but somewhat less transparent). (I am sure you could have whipped up a perl routine
even faster than I made the original bash script, but didn't.) 

>
>> Plus as I said, I wanted the program to be obvious in what it does, and
>> I suspect that a bash script is more readable than a perl script say, or
>> whatever your favourite interpreted language is.
>
> That’s only true for readers who have already learned shell scripting.

Well, not really. While the details might be obscure, the script is
simple enough that one could read it even without knowing shell. 
And one could always run it with bash -x and explicity see what is sent out. 
I do agree that you would have to know about -x. 

Can you read Troy's html and see that what he does is essentially
equivalent to what I did? Not his explanation, but the actual code.
If I am going to be entering all my passwords into a program being
shipped out to someone I do not know, I am not going to take his word as
to what his program does. 
That would seem to be an even more important security aspect than
worrying about whether the password would be revealed in a ps listing
for a millisecond of time. 

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