TLS module on Windows

[Anael]

Hi Guys,

I'm just updating my SVN windows version of aMSN.
My computer is based on windows XP SP3.

The pop-up requesting the installation of the TLS module appears (in order to use MSN Protocol 9)


I select Windows on the combo-list, and download the file.
But appears an Error Message saying the downloaded file couldn't be opened (permission problem).
View that i'm using an administrator account, I hope the problem is linked to the file path

D:\Documents and Settings\Anael\Mes documents\Logs\amsn_received

And particullary to the space character.




I try the how-to explaineb by kakaroto an another thread, the repertory amsn/lib/tls is existing :

I paste the zip file content in. Nothing change.

And another few graphical bug : If you make cancel on the TLS notification window, you got a truncated error message :


Have a good day,
Anael

[alexandernst]

Could you check if you really have read/write perms in that folder?
Go to that folder, right click > properties > security.

[Anael]

Hi alexandernst,

Yes I have rights (full control) on these folders.
I try to foud where to copy the content of the downloaded file, and become crazy :-/
The good path isn't /lib/tls1.50 nor /scripts/plugins/tls1.50
What is this path ? Have you any idea ?

Regards,
Anael

[kakaroto]

hi Anael, the issue is different. for windows, it should never download the tls plugin.. actually, the 'permission error' is because it downloads a zip file then tries to execute it or tries to run 'tar -xzvf $filename' when there is no 'tar' command on windows. And it's simply because it should *never* download tls under windows (and mac).
I see you have tls installed, but it's tls1.4... wtf, it's old, and maybe that's why it's not working... go check if your previous installation of aMSN (the old 'scripts' directory) had tls in it's scripts/utils/windows directory. If yes, copy that one over to your current SVN installation... if not, then try to install the latest aMSN version, and upgrade that one to SVN. (rename your scripts folder to scripts-svn, so you don't need to download it again after the install of 0.98.3).
Hope it works.

[Anael]

Hello kakaroto,

I check, unsuccesfully, the repertory scripts/utils/windows and doesn't found the requested file.
So I delete all the content of the amsn directory, and install the latest release (0.98.3)
I update to the latest SVN, with new files (not a copy / past).
The TLS directory is now updated :


The window always appears requesting the download of the tls module.

Another idea to check ?
I haven't change anything to windows before the bug appears.

[kakaroto]

ok, this should be fine.. you have 1.6 now, so that's good.. now go to your c:\documents and settings\anael\amsn\plugins and see if there's a tls directory in there, if yes, delete it.
If it still doesn't work, then open aMSN, press ctrl-shift-C to have the amsn console appear, and type "package require tls".. paste here the output.

[Anael]

Hello kakaroto,

You find the answer :-)
Thanks !!

Can this problem to be linked with the fact i'm using amsn on windows & ubuntu with the same data profile ?

Have a nice day,
Anael

[kakaroto]

cool, glad it worked... I'm not sure, but yes, I think that it might be the cause.. amsn in linux put tls in your ~/.amsn/plugins directory, and aMSN windows tries to load that version as well.. install tls directly on your ubuntu system with apt-get install tcl-tls.

[Anael]

You're true again kakaroto ;-)

Maybe an idea that including the tls module on amsn/utils/linux ?
It can be hopefully for a really few users...

Yes, I know "take a bath" :p

See you,
Anael

[kakaroto]

if you apt-get install amsn, then tcl-tls is a dependency and will be installed automatically.
If you don't, then we have no choice because we won't have write access to /usr/share/amsn/utils/linux without being run as root...
and I don't get the 'take a bath' joke...

[Anael]

Hi,

Ok, you're 100% good !
Forgot my (not good) idea.

Anael

[kevmif]

I had this on Fedora 13 yesterday. Same fix applied - simply delete the TLS data from the profile.

The issue popped up for me after using preupgrade to go from Fedora 12 to Fedora 13.