LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Authorization problem with LogMeIn - SSL configuration? (http://www.linuxquestions.org/questions/slackware-14/authorization-problem-with-logmein-ssl-configuration-768226/)

Johncc330 11-10-2009 12:56 PM

Authorization problem with LogMeIn - SSL configuration?
 
Hello people.

I first thought it might be a problem with Firefox, but after installing Opera, I had exactly the same problem (thanks to those who helped there!).

A friend of mine had asked me to help him out with a problem, and gave me access through LogMeIn. I had entered previously, while I still had Slackware 12.x installed (32 bit), but now, with SW64, and FF3.5.x, I can't get in. I mean, I can _log_ in, but clicking on 'Remote control', the system advances past 'Connected' and then disconnects (there seems to be a timeout).

I configged the logging in LMI for including debug information, and got this:

2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL cipher AES256-SHA (256 bits) TLSv1/SSLv3 selected.
2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL session: REUSED, timeout is 600 seconds
2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - Assigned remote address: 201.253.152.112:46619
2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - Connected (SSL: yes).
2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL handshake started.
2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - SSL shut down - socket stays connected
2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - SSL handshake started.
2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - Error (in recv): Se ha forzado la interrupción de una conexión existente por el host remoto. (10054)
2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - Closed (rcvd 176 bytes, sent 345 bytes).
2009-11-09 01:22:40.453 - Error - LogMeIn - Socket - 201.253.152.112:46619/rawssl - SSL error: SSLv2/v3 read client hello A (in accept).
2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL handshake done.
2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL cipher AES256-SHA (256 bits) TLSv1/SSLv3 selected.
2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL session: REUSED, timeout is 600 seconds
2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - Assigned remote address: 201.253.152.112:58874

The line before the 'Error' line, translated to English, says as much as 'The existing connection was dropped (interrupted) by the host". The user forums at LMI aren't very helpful - the problem is discussed but no solution.

There is one line marked as 'Error', I've tried to google this message, read a lot of mails commenting it, but most of the issues were Ubuntu-related. I couldn't find any difference in configuration of OpenSSL, /etc/ssl/xxx, etc, as compared to before changing to SW64. They just all look identical. I can't find any .pem file on the disk, but then there wasn't one before, either.

I'd appreciate suggestions...
John

wfh 11-10-2009 01:50 PM

Do you have the system set up with reverse DNS....a TXT http://en.wikipedia.org/wiki/Reverse_DNS_lookup?

Reverse DNS lookup

Johncc330 11-10-2009 03:10 PM

Quote:

Originally Posted by wfh (Post 3751940)
Do you have the system set up with reverse DNS....a TXT http://en.wikipedia.org/wiki/Reverse_DNS_lookup?

Reverse DNS lookup

I have just an ADSL connection - my IP regularly changes. I can't say I remember ever having worried about reverse DNS. Wouldn't this be under control of the ISP?

John

Johncc330 11-10-2009 03:17 PM

... Anyway, I just tried

dig -x xxx.xxx.xxx.xxx ptr (xxx... is my IP)

from another machine, and it resolves correctly to the domain name assigned dynamically.

John

agentdcooper 11-10-2009 11:50 PM

Quote:

Originally Posted by Johncc330 (Post 3751865)
A friend of mine had asked me to help him out with a problem, and gave me access through LogMeIn. I had entered previously, while I still had Slackware 12.x installed (32 bit), but now, with SW64, and FF3.5.x, I can't get in. I mean, I can _log_ in, but clicking on 'Remote control', the system advances past 'Connected' and then disconnects (there seems to be a timeout).

this is a known issue with 64-bit flavors of linux (known for a while actually...) but yr in luck! I found this link for ya, try it out and lemme know what u think - otherwise I will give 'er a whirl and see what happens, as I have yet to give this one a shot ;;

from = http://community.logmein.com/logmein...message.id=541 ;;
Quote:

So what I did, was I downloaded the 32-bit version of this plugin and installed it by using nspluginwrapper (the same procedure typically used for flash support in 64-bit linux). If you download the .tar.gz version, you should find an .so file.
After you download that file you have to follow the following instructions:
1) untar the file: (e.g. tar xvf ./logmein-client-1.0.387-1.tar.gz)
2) make sure you have it in a directory that you can reference and store for future use (I have mine in ~/Source/logmein-client-1.0.387-1/libractrl.so)
3) make sure you have nspluginwrapper installed (in ubuntu 9.10, if you don't, you should be able to type "sudo apt-get install nspluginwrapper" to get this to work)
4) run the following command as root or sudo: "sudo nspluginwrapper -i ~/Source/logmein-client-1.0.387-1/libractrl.so"
5) restart firefox

Number four is important to run as root, installing the plugin in user space did NOT appear to work.

Hope this helps someone.
otherwise, u are dead in the water... I actually have been running win7x64 via kvm and/or virtualbox, and then getting into logmein that way on my slackware 13.0 x64 machine, until I just found this link. so please report back yr luck, and we shall go from there! :D

Johncc330 11-11-2009 03:17 PM

Quote:

Originally Posted by agentdcooper (Post 3752487)
this is a known issue with 64-bit flavors of linux (known for a while actually...) but yr in luck! I found this link for ya, try it out and lemme know what u think - otherwise I will give 'er a whirl and see what happens, as I have yet to give this one a shot ;;

Hello agentdcooper,

Thanks for the info.

I'm quite convinced this is not my problem - I'm not using any plugin to access LMI - never have. The thread speaks about using the plugin if java fails - but I have a running Java installation. As far as I understand things, I don't need a plugin.

John

Johncc330 11-11-2009 03:24 PM

Welllll.... Maybe not - I had missed the last part of the thread, where it says the 64bit java plugin is incompatible with LMI. Is this really true? I thought Java was the flagship of compatibility?

I have very little incentive (LMI is not enough) to install 32-bit Java again, and invite problems with ndiswrapper etc.

Thanks again,
John


All times are GMT -5. The time now is 01:26 AM.