unsubscribe

[David N Murray]

Good bye David N Murray dmur...@jsbsystems.com :-(
You are now unsubscribed


-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

unbind?

[David N Murray]

Hi all,

I'm tinkering with the app/main.l code, specifically:

(de go ()
   (pw 12)
   (task (port 4040)  # Set up query server in the background
  (let? Sock (accept @)
 (unless (fork)  # Child process
(in Sock
   (while (rd)
  (sync)
  (out Sock
 (pr (eval @)) ) ) )
(bye) )
 (close Sock) ) )
   (forked)
   (rollback)
   (server 8080 @start) )

I use emacs and love running picolisp in an emacs buffer.  My problem is,
if I stop the server and try and restart it:

: (go)
!? (port 4040)
IP bind error: Address already in use
?

My question is, how do I unbind the port?  I've played around with
various incantations of (task 4040) and (close 4040) and can't seem to get
rid of the error without exiting and restarting picolisp.

TIA,
Dave

-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: wiki password

[David N Murray]

On Oct 27, Alexander Burger scribed:


 Why not?

 Nobody could stop me anyway. I could trace the program during execution,
 for example, to get the passwords.


Pardon me for jumping in (short time lurker; reading the archives alot).
In general, I've always designed systems with passwords stored in a
database as a one-way hash so that if the database gets compromised,
you're not giving up users' passwords (it's a PITA to tell everyone to
change their password).  I encrypt the passwords in the browser (using the
same algorithm) and always transmit an encrypted password.  There's no
place to peek.  I provide a one-time link to a password reset page if they
forgot their password.  That's sent to the email on file (which they gave
me).

hth,
Dave
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: wiki password

[David N Murray]

On Oct 27, Tomas Hlavaty scribed:


 not sure if I understand it well but it seems to me that your hash
 becomes the password.  In other words, if I find out the hash, I can log
 in (e.g. using my own client).


Yes, I suppose, but the only way I see you getting the hash is:
a) steal the database
b) be a MITM over https (I don't do passwords over http when I design a
site)
c) browser exploit?  not sure if that's possible

Dave
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Subscribe

[David N Murray]

Hello David N Murray dmur...@jsbsystems.com :-)
You are now subscribed


-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe