Closed GoogleCodeExporter closed 9 years ago
Original comment by j...@cp-lab.com
on 11 Aug 2010 at 1:30
A work around would be to use stunnel locally to connect to the remote server
over ssl, although it would be nicer for this to be supported natively with
transgui...
Original comment by deltafox...@gmail.com
on 26 Aug 2010 at 3:22
Original comment by j...@cp-lab.com
on 26 Aug 2010 at 2:28
Note that other transmission remote clients already support this. It should be
trivial to do this with the FPC http unit. It just means allowing for "https:"
in your RPC exchange.
Original comment by reardo...@gmail.com
on 21 Sep 2010 at 3:23
I have made the simple change to support this by using ssl_openssl unit in
main.pas. You need to make one minor change to ssl_openssl_lib.pas (removing
'uses Libc', which is extraneous).
main.pas lines 28-29, 2722-26 (based on r485)
Original comment by reardo...@gmail.com
on 10 Nov 2010 at 5:27
Attachments:
Please attach patch files instead of full source files.
Original comment by j...@cp-lab.com
on 10 Nov 2010 at 6:00
Sorry about that. I do not know how to create patch files. Help?
Original comment by reardo...@gmail.com
on 10 Nov 2010 at 6:03
"svn diff" command.
Original comment by j...@cp-lab.com
on 10 Nov 2010 at 6:04
note that this is only the TRG patch, not the Synapse patch. For synapse you
must remove the Libc reference in ssl_openssl)lib (though this appears to only
be necessary on 64-bit Linux). Libc is deprecated. Synapse compiles fine
without it.
Note on ssl & synapse:
http://sourceforge.net/mailarchive/message.php?msg_name=AANLkTik68nrv5FCFL12l397
0IZWN-ep9hue05Sj07SCi%40mail.gmail.com
Original comment by reardo...@gmail.com
on 10 Nov 2010 at 7:21
Attachments:
[deleted comment]
Implemented r492. I made proper implementation with an option in the Connection
page.
The note on sourceforge is not correct at least for FPC 2.4. It has proper
declaration for HModule on 64-bit systems:
HModule = THandle = QWord
Original comment by j...@cp-lab.com
on 10 Nov 2010 at 9:53
Note that for historical reasons Debian, among other packaging systems, does
not include the proper symlinks for libssl.so and libcrypto.so in the base
openssl package. You must either install the dev package openssl-dev (or
libssl-dev or whatever) or create the symlinks manually.
Original comment by reardo...@gmail.com
on 11 Nov 2010 at 8:52
Original issue reported on code.google.com by
cirr...@gmail.com
on 28 May 2010 at 10:35