in reply to Re: Re: MySQL Status Tool
in thread MySQL Status Tool

Cool... Why not leave the -Tw and use strict; on in the release version, in case of feature creep?

Short of using javascript to encrypt the password on the client side, with a random "salt" generated from the server each time the page is issued, I don't see a lot of great solutions.

In any case, make SURE you never use such an app outside your corporate network, and even there, realize that malicious insideers could wind up with your mySQL root passwd...
--
Mike

Replies are listed 'Best First'.
Re: Re: Re: Re: MySQL Status Tool
by Anonymous Monk on Apr 16, 2002 at 15:56 UTC
    Feature creep might happen, but I add in -w, -T, and -Mstrict as a habit anyways. I will add it if you really want, though. :)<br.
    Any sniffer could also detect the salt used for encryption, so it's unavoidable.

    With a quick edit, you can hardcode in the mysql password in the file. Just change the line like:
    my $rootpwd = $q->param('rootpwd');
    to
    my $rootpwd = 'ilikeapples';.

    -qslack, posting as anon because I am not at my computer and I forgot my password :)
[reply]
[d/l]
[select]
      Seeing the salt of a 3DES or MD5 encrypted password hash isn't enough to make it nearly as easy to read as plaintext. The sniffer would know the encrypted password that one time, but they'd still have to actually crack it in order to use it in the future, or sniff the newly encrypted one next time too, and beat you to submitting the data back to the server. You could also make sure the server only accepts the password encrypted with that salt from the IP to which it sent that salt...

      In other words, don't dismiss advice out of hand without considering that it might actually be good advice.
[reply]
        Playing tricks like that will only get crackers excited. You don't want to excite the crackers. Better to just stick it on an SSL server and hope for the best!

        -sam

[reply]

In Section Cool Uses for Perl