Rava wrote:Bogomips wrote:@ Bogomips
Since when need TrueCrypt systemd ?
truecrypt-1:7.1a-2-i686.pkg.tar.xz.html > device-mapper > systemd
Sometimes, a named dependency still is not obligatory as in: program won't run without it...
Code: Select all
root@porteus:/home/guest# activate tru_310815.xzm # truecrypt
Updating shared library links: /sbin/ldconfig
Updating KDE menu: kbuildsycoca4
guest@porteus:~$ file /usr/bin/truecrypt
/usr/bin/truecrypt: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), BuildID[sha1]=63a7ed7559bfae4b806a234abdd42c8f5703e94f, stripped
guest@porteus:~$ ldd /usr/bin/truecrypt | grep not
/usr/bin/truecrypt: /lib/liblzma.so.5: no version information available (required by /usr/lib/i386-linux-gnu/libtiff.so.5)
guest@porteus:~$ file /lib/liblzma.so.5
/lib/liblzma.so.5: symbolic link to `liblzma.so.5.0.5'
guest@porteus:~$ file /lib/liblzma.so.5.0.5
/lib/liblzma.so.5.0.5: ELF 32-bit LSB shared object, Intel 80386, version 1 (
Program will not run without versioned library.
Code: Select all
root@porteus:/home/guest# deactivate tru_310815.xzm # truecrypt
Updating shared library links: /sbin/ldconfig
Updating KDE menu: kbuildsycoca4
root@porteus:/home/guest# activate syd_310815.xzm # systemd
Updating shared library links: /sbin/ldconfig
root@porteus:/home/guest# activate tru_310815.xzm # truecrypt
Updating shared library links: /sbin/ldconfig
Updating KDE menu: kbuildsycoca4
guest@porteus:~$ ldd /usr/bin/truecrypt | grep not
Program now runs.
WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues
Rava wrote:It is years ago I last used truecrypt. Even when it is officially no longer supported, I saw no article anywhere that I can recall that tc has severe security issues.
Maybe some folks *cough*NSA*cough* just were not pleased cause they could not access truecrypted containers as they wanted and the ones developing it were ... threatened "convinced" to drop the project...
I know of only one issue with a criminal, and the federal police not being able to crack his encrypted container or encrypted file system... even after trying for at least 6 month.
Red warning says program is not secure, but it is not from viewpoint that it may crash or leave one with something that cannot be decrypted, but rather it is to do with security issues, the way I read it. The confirmation for this viewpoint being inability of authorities to crack encrypted container/filesystem after six moths of trying. So, in my book this is pretty secure. Having encryption defying decryption for six months, would probably satisfy most people.
So as long as there is no case in which truecrypt cannot decrypt the container/filesytem it has encrypted, one would say: Go for It!
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB