Valentines
Feb. 14th, 2003 01:53 pmOK so in the end I did have a go with the LVS. Oddly enough (when I finally got the notification, well done to Steve the author for sorting that out quickly and graciously) I found ewx and I had nominated each other. Neither of my two other nominees had nominated me back though. And I apparently have two mystery admirers. Wonder if they're brave enough to tell me who they are? You never can tell if I might not have been interested anyway, just out of slots.
no subject
Date: 2003-02-14 05:58 am (UTC)no subject
Date: 2003-02-14 06:01 am (UTC)I seem to have one of those... Dammit, this double-blind thing is most irritating! [confused now]
no subject
Date: 2003-02-14 06:17 am (UTC)no subject
Date: 2003-02-14 06:22 am (UTC)no subject
Date: 2003-02-14 07:36 am (UTC)*hugs*
no subject
Date: 2003-02-14 07:49 am (UTC)I passed on your comment in brackets to the author BTW, since he's been asking for suggestions, and he says he was a bit worried about the privacy implications of it which is why he left it out. I can see why you might not have time to think something like that through and work out if it's OK or not when you're just coding something up for a bit of a giggle.
no subject
Date: 2003-02-16 06:42 am (UTC)no subject
Date: 2003-02-17 01:00 pm (UTC)(Looks) yes, that should be really easy. The URL has a username and an opaque string in it; replace the username with the want you want and the opaque string with any old rubbish. If the user exists, you'll get one message, if they don't you'll get a different one. Voila.
The code to choose the hex string is rather poor too.
I believe that a better approach would be to encrypt the username using a secret key with a symmetric cipher, and quote the result (and not the username) in the URL send back by join.cgi. If the value received by validate.cgi decrypts to a known username, proceed for that user; if not then send back an error.
I notice lots of clone and hack in validate.cgi, where he ought to be using a loop. Yuck!