Re: https client
[email protected] (Don Cohen)
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
Bruno Haible writes: > Don Cohen wrote: > > > 2) https access is currently not implemented in clisp. But the web consists > > > of more and more https. > > > For https, one needs SSL support with all its intricacies (TLS protocol > > > versions, certificate checking etc.). > > > > I've used stunnel to solve this problem for a long time. > > It seems perfectly adequate and also reasonable. > > stunnel is a daemon, right? What is the point of having a separate process, > for something that most programs do through library code? Most programs do this? By using calls to the openssl library? I have no idea what's involved. If it's easy, go ahead. > Daemons are a hassle: if they are owned by the system, it requires privileges > to start them; if not, the functionality breaks when the daemon happens to > have crashed. I'd guess that a user can run stunnel if it only has to allocate user ports. If you want to listen on port 443 you're going to need the same privileges to do that in clisp as you would need to start stunnel listening there. I don't remember off hand ever seeing stunnel crash. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel