Menu

#46 Mcrypt sporadically fails with fatal error "Signal 11 caught."

Production/Stable
open
nobody
Signal 11 (1)
1
2018-08-15
2018-03-14
No

Mcrypt sporadically fails with fatal error "Signal 11 caught. Exiting." during encryption and/or decryption, using default options.
File type, name, owner, mode, and size do not seem to matter.

Sample:
-rw-r--r-- 1 serapis users 20480 Mar 14 17:36 testfile.txt
testfile.txt: ASCII text
"
mcrypt testfile.txt
Enter the passphrase (maximum of 512 characters)
Please use a combination of upper and lower case letters and numbers.
Enter passphrase:
Enter passphrase:

Signal 11 caught. Exiting.
"
Output file is created, but appears to be corrupted:
-rw------- 1 serapis users 15 Mar 14 17:39 testfile.txt.nc
testfile.txt.nc: data
"
mdecrypt testfile.txt.nc
mdecrypt: testfile.txt already exists; do you wish to overwrite (y or n)?y
Enter passphrase:
File testfile.txt.nc was NOT decrypted successfully.
"
mcrypt -v
Mcrypt v.0.9.9 (x86_64-dragnux-linux-gnu)
Linked against libmcrypt v.2.5.8
Build Host: opensuse:tumbleweed:20180311

1 Attachments

Discussion

  • Brandon Garrison

    yes, I have plenty of available disk space (blocks & inodes) and ram.

     

Log in to post a comment.