If it gets added to trunk, could the binding to libcrypto and libopenssl please be optional? I mean rather than compiling with a dependency on those libs, add code to dynamically load these libraries and disable https: support if they cannot be found. Those libraries are available standard on linux boxes, but not on windows. Not sure about FreeBSD & OS X. The mingw dll's are about 1 MB in size if I remember well. Also, older posix systems may not have the right version available. An alternative would be to consider something like the cyassl library, a 150K binary, which could be made a co-build, next to Fossil. How would SSL support work in the case where fossil is hosted at a cheapo ISP and the cgi setup is used to serve requests? Paul
________________________________ From: [email protected] on behalf of Ron Aaron Sent: Tue 1/12/2010 7:12 AM To: [email protected] Subject: Re: [fossil-users] Fossil HTTPS Support On Tuesday 12 January 2010 08:09:21 George King wrote: > Hi list, > > Given the recent security discussion, I would like to inquire about the > current state of HTTPS support.... Unless there are > compelling reasons not to, could these additions be merged into trunk? I would also like this. No need for it to be a default -- if the repo address begins 'https', then use that ... otherwise, don't. -- Sending me something private? Use my GPG public key: AD29415D
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
