All Activity

This stream auto-updates     

  1. Yesterday
  2. Just invented this. At the moment it is a pen and paper cipher. Does this have a practical application. One or more people want a document sealed/encrypted and only opened if all agree for it to be opened. Each encrypt it with their password and pass it on to the next. When all have it encrypted everyone gets a copy. Perhaps this already exists.
  3. Last week
  4. The message was... !!! Happy Birthday LCS !!! (seed value b for p = 712238904468723561162000937465778229877598711342253664788091132335) Source: https://www.mersenneforum.org/showthread.php?p=516879#post516879
  5. Earlier
  6. Apple has released a video to promote End-to-End Encryption
  7. Self-taught Belgian bloke cracks crypto conundrum that was supposed to be uncrackable until 2034 By Katyanna Quach 30 Apr 2019 at 06:04 https://www.theregister.co.uk/2019/04/30/cryptography_conundrum_cracked/ 'It was easy, for some definition of easy,' solver tells El Reg A cryptographic puzzle proposed two decades ago that involves roughly 80 trillion squarings has been cracked much earlier than expected - in just three and a half years. On Monday, the puzzle was solved by Bernard Fabrot, a self-taught independent Java developer from Belgium. The time capsule will, thus, be cracked open by Rivest for the world to see on May 15, and the secret message revealed.
  8. Description of the LCS35 Time Capsule Crypto-Puzzle by Ronald L. Rivest April 4, 1999 As part of the celebration of the 35th birthday of MIT's Laboratory for Computer Science, LCS Director Michael Dertouzos will present an "LCS Time Capsule of Innovations" to architect Frank Gehry. The Time Capsule will reside in the new building, designed by Gehry, that will house LCS. The time capsule will be unsealed on the earlier of 70 years from the inception of the Laboratory (on or about 2033), or upon solution of a cryptographic puzzle, described herein. This puzzle is designed to take approximately 35 years to solve. It uses the ideas described in the paper "Time-lock puzzles and timed-release Crypto" by myself, Adi Shamir, and David Wagner. A copy of this paper can be found at http://theory.lcs.mit.edu/~rivest/RivestShamirWagner-timelock.ps. The puzzle is designed to foil attempts of a solver to exploit parallel or distributed computing to speed up the computation. The computation required to solve the puzzle is "intrinsically sequential". https://people.csail.mit.edu/rivest/lcs35-puzzle-description.txt
  9. The European Commission has issued a product recall for the ENOX Safe-KID-One. The device is a smartwatch designed for children. The EC recall states: the mobile application accompanying the watch has unencrypted communications with its backend server and the server enables unauthenticated access to data. As a consequence, the data such as location history, phone numbers, serial number can easily be retrieved and changed. A malicious user can send commands to any watch making it call another number of his choosing, can communicate with the child wearing the device or locate the child through GPS. The product does not comply with the Radio Equipment Directive. Further information: https://ec.europa.eu/consumers/consumers_safety/safety_products/rapex/alerts/?event=viewProduct&reference=A12/0157/19&lng=en
  10. Microsoft has revealed details of an incident where an automated process, designed to trigger when custom keys are removed from KeyVault, caused TDE databases to be dropped from Azure on 29 January 2019. Microsoft tried to restore customer data from a five-minutes-ago snapshot resulting in empty databases and new database names for some. Transactions, product orders, and other updates during that five minute period were lost. Compensation is available to affected customers. For more information see https://www.theregister.co.uk/2019/01/30/azure_sql_delete/
  11. James

    kleopatra

    The reference guide is here... https://docs.kde.org/stable5/en/pim/kleopatra/index.html The support forum is here... https://forum.kde.org/index.php
  12. congo

    kleopatra

    Had to reload windows 10.my encryption program changed.I did have just gnu4pg v2 then when I reloaded i,it became kleopatra.All my encryption works in that interface.Before the change i could copy an encrypted message drop it in my clipboard decrypt and use passphrase and the message would open.Now it says no secret keys or no open pgp data.Can any1 help?? date 10/21/2018, Ron
  13. Here is a Javascript implementation of the NEW version of the Hutton Cipher. The original version had the problem where the password should not contain the letter Z because otherwise, the ciphertext would periodically contain plaintext letters. But if you don't have Z in the password, plaintext letters will NEVER encrypt to themselves, and you end up with the same problem ENIGMA had. The new rule in Hutton v2 is instead of just counting to the right as many spaces as dictated by the base26 value of the key letter, you sum that value with the base26 value of whatever letter happens to be first in the scrambled alphabet. With this modification, the cipher now produces ciphertext with a 1/26 chance to encrypt a plaintext letter to itself. Which is exactly what one would want to have. Also, the keyed alphabet is now created by appending the alphabet portion in REVERSE to the key. This is because most keyed alphabets were predictably ending in XYZ.
  14. Every day this week, Cloudflare will be announcing support for a new technology that uses cryptography to make the Internet better. https://blog.cloudflare.com/crypto-week-2018/
  15. Here is a video illustrating how it works.
  16. If you use multiple keys whose lengths are relatively prime, your effective Vigenere key length is the product of the lengths of all the keys. Imagine using keys with relatively prime lengths 9, 10, and 11. Your effective key length would be 1,320 characters long! Using an easily-remembered phrase that you can break up until lengths of perhaps 29, 30, and 31, you're practically using a one-time pad 26,970 letters long that you can store in your head! Is there any way to crack such a ciphertext if it's shorter than the effective key length?
  17. Someone calling themselves Hutton invented a new pen-and-paper cipher that seems to be incredibly secure. He offered a reward of over $1,000 to anyone who could crack it, although he disappeared from the internet a month ago so I'm not sure if the challenge is still ongoing. Anyway, here is how it works. You come up with a scrambled alphabet and a key. Write your key repeatedly under your plaintext just like Vigenere. To encrypt the first plaintext letter, find it in the scrambled alphabet. Count to the right (wrapping if you reach the end) as many letters as the number which your key-letter represents (treating it as a base26 number where A = 0, Z = 25). The letter you land on is your first ciphertext letter. Before you move on to encrypting the next letter though, scratch out those two letters (the plaintext and ciphertext ones) from the scrambled alphabet, and write them under each other. This effectively swaps them. For example, if you first plaintext letter is B and your first ciphertext letter is X, scratch out B and write X under it. Scratch out X and write B under it. Here is a Javascript version of the cipher. Note that it treats password letters as numbers where A = 1 and Z = 26. This is only because I was creating it precisely according to the author's instructions and only realized the problem afterwards and couldn't be bothered to update it. It would be very interesting to know if anyone can find any real weakness with this marvelously practical pen-and-paper cipher.
  18. Server Name Indication (SNI) transmits a virtual domain name during the TLS negotiation process so that a server with a single IP address can support multiple virtual domains, instead of requiring a unique IP address for each TLS host. SNI does not conceal the requested hostname so it can be used for network filtering which is a privacy concern. ESNI - Encrypted SNI - replaces the server name in the ClientHello message with an encrypted equivalent. It is placed in the DNS records as a TXT record. It has a checksum which uses the first 4 octets of the SHA-256 message digest, padding, and a validity period. However the specifications suggest the expiry date should not be used for caching to allow servers to rotate the encryption keys.
  1. Load more activity