Fishy not working under Snow Leopard
-
Henning Kiel- State changed from new to open
- Milestone set to 0.5.0
I uploaded some changes to Github yesterday which make FiSHy compile in 32/64Bit universal. The problem, though, is that the underlying library does not seem to be ready for 64Bit. I have not looked any further, so there might be a simple solution, but for now I do not have the time to do it.
-
Gabriele
ok I was trying to compile the plugin by myself and I noticed what you're saying, libcrypto refuses to link, it seems there's an easy solution to this (quoting from: http://www.cocoabuilder.com/archive/message/cocoa/2009/8/29/243785)
The solution to this is pretty simple, don't link to libcrypto. Instead, just #import <CommonCrypto/CommonDigest.h> in your file and use the CC_ prefixed functions in your app, such as CC_MD5.
I also tried to link libcrypto and libssl 0.9.8 from the 10.6 SDK, it compiled successfully and it's running on Colloquy 64bit, everything seems to work perfectly, but messages are decrypted incorrectly :(
hope this help!
-
Henning Kiel
Yes, I got it to link by just using the 10.5 SDK, and got the same problem. It seems that during en-/decryption there are some problems. It might be just as easy as to make sure that all data types inside the crypt-functions are still 32bit, but at least in the next weeks I probably will not get around to spend more than a few minutes on this.
-
Gabriele
I'm not an expert, but is it normal that I was able to compile Fishy after completely removing both libcrypt and libssl library links? also cheching with: "otool -L /Volumes/FiSHy/FiSHy.plugin/Contents/MacOS/FiSHy" confirms that libcrypt and libssl aren't linked. The behavior of the plugin is the same, text is still incorrectly decrypted. I'm not sure what this mean but it may be a pointer for you, as I don't exactly know which functions you're using from those libraries.
-
Henning Kiel
Thanks for the information.
The last time I looked at the encryption parts was quite some time ago, so I am not sure if and how the code uses those libraries. Maybe it uses them but Colloquy does link to them.
Nevertheless, I do not think that the problem is how those libraries are linked, but instead how the encryption/decryption is handled. My first guess, atm, without looking at the code is that the code uses ints, which are now 64 Bits, and does not take this into account.
I hope I will have some time in the next week to fix this.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.