Packetizer Forums

Ok, did printf tracing. It was bombing out on the first memset in aescrypt.c/main() line 989.

the password entered was good, being "1234" was received properly into pass_input. However, passlen = -1 after returning from passwd_to_utf16 call (just straight before the memset call).

just an update.

Looks like it works with /lib/libc-2.7.so (or earlier). This was from slax.

But the one I was using in tinycore is libc-2.13.so, which resulted in Seg Fault. That was tinycore 4.1, I loaded tinycore 3.0 which had libc-2.10.so ??? but still Seg Faulted.

Ok,

I managed to get gdb running and backtrace the seg fault with the following result:

#0 0xb76e8ace in memset () from /lib/libc.so.6
#1 0x0804ae00 in main()

Thank you for the quick reply.

I am not using anything fancy for the password, just "1234", "123", etc to test things out. Also tried password123 just in case it was expecting longer passwords. But same result.

The thing is, I also compiled it on a very older version of fedora (Fed 6, uname -a ...

Hi,

I downloaded aescrypt for linux sources and managed to compile in Tiny Core Linux with no errors. When I try to execute an encryption,

# aescrypt -e Readme.txt

it prompts for password and re-enter password, then Segmentation Fault, with echo $0 = 139.

Any suggestions???

thanks in advance.