search

Treferwynd / transmission-remote-gtk

Automatically exported from code.google.com/p/transmission-remote-gtk
GNU General Public License v2.0
0 stars 0 forks source link

SSL sef-signed certificate doesn't work #262

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What is the expected output? What do you see instead?
I have a error when I want used with SSL:

"SSL peer certificate or SSH remote key was not OK"

What version of the product are you using? On what operating system?
Server: Debian Sid - Transmission 2.82 in the repository with self-signed 
certificate on port 443
Client: Debian-Sid - Transmission Remote GTK 1.1.1 in the repository

Please provide any additional information below.
Work great with Transmission remote gui on Windows 7, 8 and Android KitKat
And with the gnome-shell extension

Original issue reported on code.google.com by valentin.becu on 13 May 2014 at 10:50

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by valentin.becu on 13 May 2014 at 10:57

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello,

Self signed SSL certificates have always been allowed, since obviously very few 
people will secure a transmission-daemon with a real CA.

I have tested with 1.1.1 and with the latest git, and have found that my 
self-signed cert (on stunnel, I've used apache previously) works fine.

The git version makes cert verification on/off configurable, off by default. 
Perhaps you could try it, but I doubt it will make a difference.

I'm guessing that there is some "issue" with the cert, according to libcurl. 
Perhaps you could try curl -v --insecure on the command line and see if that 
tells you what it is.

Original comment by a...@eth0.org.uk on 20 May 2014 at 9:33

GoogleCodeExporter commented 9 years ago 
Hi,

The result for "curl -v --insecure":

george@Portable:/home/george$ curl -v --insecure https://**.*******.**/
* Hostname was NOT found in DNS cache
*   Trying ***.***.***.***...
* Connected to **.*******.** (***.***.***.***) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using TLSv1.0 / AES256-SHA
* Server certificate:

**********************

*    SSL certificate verify result: unable to get local issuer certificate (20), 
continuing anyway.
> GET / HTTP/1.1
> User-Agent: curl/7.36.0
> Host: **.*******.**
> Accept: */*
> 
* HTTP 1.0, assume close after body
< HTTP/1.0 301 Moved Permanently
< Date: Thu, 22 May 2014 15:08:33 GMT
< Server: Apache/2.4.9 (Debian)
< Location: https://**.*******.**/transmission
< Content-Length: 329
< Content-Type: text/html; charset=iso-8859-1
< X-Cache: MISS from localhost
< X-Cache-Lookup: MISS from localhost:3128
< Via: 1.0 localhost (squid/3.1.22)
* HTTP/1.0 connection set to keep alive!
< Connection: keep-alive
< 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a 
href="https://**.*******.**/transmission">here</a>.</p>
<hr>
<address>Apache/2.4.9 (Debian) Server at **.*******.** Port 443</address>
</body></html>
* Connection #0 to host **.*******.** left intact

Thanks for help

Original comment by valentin.becu on 22 May 2014 at 3:07

GoogleCodeExporter commented 9 years ago 
Same problem... can't get the cert from the url when using Ubuntu client. It 
works with the Windows version without any issue.

Original comment by murdr...@gmail.com on 17 Jun 2015 at 2:12

Treferwynd commented 8 years ago

@gkranis sorry for the late response, this is my personal fork, I just added a few features I liked and it's not up to date. Maybe try here: transmission-remote-gtk/transmission-remote-gtk

gkranis commented 8 years ago

sorry for the noise, don't even know how i missed that it was a fork :), will delete both comments

Treferwynd commented 8 years ago

No problem, there's no need to delete the comments though!