All Activity

This stream auto-updates     

  1. Earlier
  2. This is a very flexible cipher. It can be used as an encryption algorythim, as a random number generator, and a way to test randomness of a prng (I know that will make you cringe but please look at it before you come to an opinion). The sample was taken from a prng found here for medical purposes from this site(https://stattrek.com/statistics/random-number-generator.aspx#error)...see Excel sheet named prng histogram at the link or click here. http://hishouseinc.com/encryption.php Next video will be how to use this alg. as a prng.
  3. A video explaining decryption of the positional cipher With multiple passes the cipher text can equal any one of the numbers or letters of the key. Meaning the key length only needs to be as long as all letters or numbers used. Not as long as the plaintext.
  4. I'll explain in a minute: How this avoids frequency attacks. Language attacks. How to decode. Applied Diffie Helman for P.F.S Simple applied variations that make this secure.
  5. A couple of thoughts... if you have repeated characters and you can choose different positions then when you re-run the encryption you could reveal which characters are the same. If the plain text is English then we could expect the most duplicated characters to be the letter E, and the least duplicated to be letters such as Q and Z, and then just test out different character mapping arrangements. However I don't fully understand the decryption process... if you give me the key of XYZ and positions 2,1,4,3,5 how do I know which letter a position relates to unless it is in the key. How do I come up with A, B or C? Or does the key have to contain all the unique letters of the plain text? Also, with the key embedded, I am just wondering about forward secrecy implications.
  6. Decided to post this and explain my new cipher. Interested in hearing your opinioin. I can not figure out how to launch an attack.
  7. I have been working on this encryption alg. on and off for over six years. I call it the Chameleon cipher. Normally you create an account, the hashed salted password is stored and then the attackers build a database to try to guess your hash. Yes, I know there are many steps to last sentence. Here is an encryption I did on an md5 hash. Here is the way to use this. client enters their password - a hash is created. The hash is encrypted with a cipher text that changes randomly every time the user logs in. All this is done in the back ground even though they enter the same password. Once received the algorithm deciphers the cipher text into the md5 stored and gives permission for access. I know you are cringing at this point about "random" . This is a completely new cipher. Here is an encrypted md5 hash. The hash was not conditioned it was a 32 char hex. At first glance because of the high decimal numbers and the groupings of numbers is obviously less than 32, it is easy to think it is like a fairplay cipher. Sometime yes and sometimes no. The difficulty in decryption comes when you realize that 112 can mean any number or any letter, or combination of letters no matter how many times it is used or where it is located, AND this changes randomly. 112 58 61 220 207 188 25 53 110 176 221 58 234 195 19 17 63 78 232 62 242 136 The above is a common password taken from an md5 hash.
  8. This could easily be made into an impossible to decrypt cipher. Where one key of x and y organize the row into a single letter in the row randomly located and read that make up the plain text (modified book cipher)....this is more dangerous than i thought.
  9. Thank you, Decided to post this as a competition. I know it will never be succesfully attacked. I will be posting the details soon. In the mean time here is a fun encryption puzzle I made years ago using excell. You can find it here. It is free. scroll down to the bottom of the page: http://hishouseinc.com/inventions.php
  10. Why not submit it for a competition or for peer review first? https://competitions.cr.yp.to/
  11. Hey James, this cipher is suddenly making me very nervous. I've studied ciphers for over 40 years. I see no way to decrypt it without the key. How do you handle the idea that someone someday will post a cipher that is solid, unbreakable, and they have just placed it in the publics hands. I'll post it, I'm not looking for drama just nervous.
  12. You are very welcome to post here. Forum guidelines are here but basically are just about being polite to one another. For video/files etc I recommend hosting off-site with YouTube/DropBox etc and linking to them so that your copy stays safe. Looking forward to hearing more about your concept.
  13. Thanks for the reply, i am ready the links to your reply. It is close to a threshold encryption but it does have major differences. Most encryption algorithms are not patented so i will post a video of the mapping. This surpasses my ability to code although it is a very simple process. The algorithm can be used in many ways. To discover sequences in arbitrary files, change the entropy of a random file, used as a one time pad. Once again i am new here and want to abide by all rules. If this can not be discussed here please delete this and let me know where i can move this topic.
  14. One area it might be useful is for a blind auction. I think this method would rely upon a per-document key rather than a per-user key, similar to https://github.com/owncloud The process is outlined in more detail here... https://security.stackexchange.com/a/78933 However this only covers multi-user encryption, rather than your lockdown until all users have completed. Perhaps that aspect is better covered by file access after the encrypting stages?
  15. 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.
  16. The message was... !!! Happy Birthday LCS !!! (seed value b for p = 712238904468723561162000937465778229877598711342253664788091132335) Source: https://www.mersenneforum.org/showthread.php?p=516879#post516879
  17. Apple has released a video to promote End-to-End Encryption
  18. 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.
  19. 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
  20. 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
  21. 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/
  22. 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
  23. 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
  24. 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.
  25. 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/
  1. Load more activity