The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Clients create Self-signed CA Certificate
Is there a way to stop clients from creating a self-signed CA certificate. Problem is that they are not publically trusted so we are inundated with security vulnerabilties.
The self signed certificate in LogMeIn is used in these cases:
- host credentials are encrypted by the host's public key and saved on the clients or in the browser for:
- autologin
- One2Many tasks (Central)
Since encrypted with the hosts public key (prior saving it) only the host can decrypt them with its own private key.
- for end-to-end encryption between the native client (Remote Control, File Manager) and the host. The client receives the host's cert in a secure channel, so it can trust it even it is self signed.
The port 2002 is used only locally in LogMeIn. The host service accepts connection from the system tray icon applet and provides some information about the state of the service
11 Replies
- Thanks for this post. Following a security test I completed, TCP 2002 was returning an unexpected response with TLS1.2 and a certificate. Having looked into this I believe this is the reason!
The self signed certificate in LogMeIn is used in these cases:
- host credentials are encrypted by the host's public key and saved on the clients or in the browser for:
- autologin
- One2Many tasks (Central)
Since encrypted with the hosts public key (prior saving it) only the host can decrypt them with its own private key.
- for end-to-end encryption between the native client (Remote Control, File Manager) and the host. The client receives the host's cert in a secure channel, so it can trust it even it is self signed.
The port 2002 is used only locally in LogMeIn. The host service accepts connection from the system tray icon applet and provides some information about the state of the service
Found this command which I believe confirms the cert being used is self signed.
What is port 2002 used for? Is there a way to apply a locally signed cert to this or what are my other options for locking this down?
C:\Users\mricker>openssl s_client -connect
Computer IP:2002 CONNECTED(00000164) Can't use SSL_get_servername depth=1 C = US, CN = Default CA verify error:num=19:self-signed certificate in certificate chain verify return:1 depth=1 C = US, CN = Default CA verify return:1 depth=0 CN =Computer Nameverify return:1 --- Certificate chain 0 s:CN =Computer Namei:C = US, CN = Default CA a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: May 10 02:39:50 2022 GMT; NotAfter: May 9 02:39:50 2027 GMT 1 s:C = US, CN = Default CA i:C = US, CN = Default CA a:PKEY: rsaEncryption, 1024 (bit); sigalg: RSA-SHA256 v:NotBefore: May 10 02:39:49 2022 GMT; NotAfter: May 8 02:39:49 2031 GMT --- Server certificate -----BEGIN CERTIFICATE----- MIIDazCCAtSgAwIBAgIICHzm51qoC88wDQYJKoZIhvcNAQELBQAwIjELMAkGA1UEHi MRicker, welcome to the community.
I am going to open a support ticket for you and I will private message you a zip file with a registry file that will fully enable the Debug mode of your Central client. Once the file is run, reboot the PC and it will start to generate the required log files (LogMeIn.log) that will be saved in C:\programdata\LogMeIn
It's been a few years since this was posted but I'm running into the same thing.
Was a solution ever found? My security team is showing that the TLS/SSL certificate is signed by an unknown/untrusted CA for all of our workstations that have the Log Me In client installed.
How would I check what certificate is being used to verify if it is self-signed or just a CA that the scanning application does not recognize?
Use the client's private key to generate a cert request. Issue the client certificate using the cert request and the CA cert/key prepaidgiftbalance.
- Following... Nessus is giving us fits with this
We use Tenable Nessus for vulnerability scanning, but I'd assume any scanner would detect a self-signed CA certificate as a vulnerability. Here are more details on the vulnerability:
The following certificate was found at the top of the certificate chain sent by the remote host, but is self-signed and was not found in the list of known certificate authorities. This nullifies the use of SSL as anyone could establish a man-in-the-middle attack against the remote host. Thanks!
