Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #6953


Ignore:
Timestamp:
Nov 8, 2012 1:16:00 PM (9 years ago)
Author:
Andre Kelpe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6953 – Description

    initial v1  
    33I have a server, that uses SSL. The certificate used by the server is signed by our own internal root CA. I have installed this root CA in the certificate management on windows, following the documentation on http://windows.microsoft.com/is-IS/windows-vista/View-or-manage-your-certificates. After that, I verified, that IE trusts the certificate of my server signed with this root CA. This works, which means, the root CA is correctly installed. After that I tried it with cyberduck and it does not trust the server at all.
    44
    5 After some googling around, I saw that cyberduck is written in java, so I went into the control panel and installed the root CA in the java configuration thing as well. This still has no effect. Cyberduck keeps on telling me, that the cert is not valid, while all other software trusts it. What am I doing wrong?
     5After some googling around, I saw that cyberduck is written in java, so I went into the control panel and installed the root CA in the java configuration thing as well. This still has no effect. Cyberduck keeps on telling me, that the cert is not valid, while all other software trusts it.
     6
     7The hostname of the server is something like foo.secure.example.com and the cert is valid for *.secure.example.com. As I said above, it works with other windows software, just not with cyberduck.
     8
     9What am I doing wrong?