pastebin - collaborative debugging tool RSS

Tails Linux 0.16 - two curious security issues
Posted by Anonymous on Sat 9th Feb 2013 11:50
raw | new post

  1. Tails Linux 0.16 - two curious security issues
  3. WTF Tails 0.16 uses an ancient version of OpenSSL!  And has it been crippled somehow?
  5. Look at this (from my Tor client logs):
  7. [notice] No AES engine found; using AES_* functions.
  8. [notice] This version of OpenSSL has a slow implementation of counter mode; not using it.
  9. [notice] OpenSSL OpenSSL 0.9.8o 01 Jun 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
  10. [notice] We weren't able to find support for all of the TLS ciphersuites that we wanted to advertise. This won't hurt security, but it might make your Tor (if run as a client) more easy for censors to block.
  11. [notice] To correct this, use a more recent OpenSSL, built without disabling any secure ciphers or features.
  13. Someone explain this please. This coming from the distro which still uses:
  15. network-manager 0.8.1-6+squeeze2
  16. network-manager-gnome 0.8.1-2
  18. LOL!
  20. ===============================
  22. Tails 0.16: DEBsig-verify disabled by default! EXCELLENT so I can get pwned and never know it, thanks guys.
  24. cat /etc/dpkg/dpkg.cfg
  25. # dpkg configuration file
  26. #
  27. # This file can contain default options for dpkg.  All command-line
  28. # options are allowed.  Values can be specified by putting them after
  29. # the option, separated by whitespace and/or an `=' sign.
  30. #
  32. # Do not enable debsig-verify by default; since the distribution is not using
  33. # embedded signatures, debsig-verify would reject all packages.
  34. no-debsig
  36. # Log status changes and actions to a file.
  37. log /var/log/dpkg.log

Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.

Syntax highlighting:

To highlight particular lines, prefix each line with {%HIGHLIGHT}

All content is user-submitted.
The administrators of this site ( are not responsible for their content.
Abuse reports should be emailed to us at