this post was submitted on 30 Dec 2025
3 points (80.0% liked)

Secure Coms

85 readers
1 users here now

This is a community for enthusiest who love to ponder new ways for Alice to communicate with Bob in a world where global passive adversarys probably record every bit that ever crosses the wire.

Discuss cryptography, secure key exchange, private messangers, radios, encoding, networking tools, authentication mechanisms and anything relevant to coming up for ways to Alice to get a message to Bob.

founded 3 months ago
MODERATORS
 

you are viewing a single comment's thread
view the rest of the comments
[–] jasory@programming.dev 1 points 1 week ago (1 children)

"Making frequency analysis ineffective"

Oh boy, let's hope nobody uses it for large plain texts. If x maps to k1,K2,... then one simply needs enough instances of x to reconstruct the key. It must at the very minimum need multiple symbols to map to the same strings to achieve ambiguity.

The cryptographic claims seem laughable.

[–] hereforawhile@programming.dev 1 points 1 week ago (1 children)

It must at the very minimum need multiple symbols to map to the same strings to achieve ambiguity.

It does this.

The only conventional cryptography is the shuffle function which takes entropy from the OS.

[–] jasory@programming.dev 1 points 6 days ago (1 children)

What motivated you to write this program?

Your choice of "codebook", is an immediate red flag and reeks of pop-crypto. There is a reason why this approach was abandoned some 100+ years ago, even properly implemented they have severe shortcomings.

[–] hereforawhile@programming.dev 1 points 6 days ago* (last edited 6 days ago) (1 children)

What motivated you to write this program?

Just for fun basically.

I've had the idea for awhile but the problem is was always a huge amount of grunt work to get the initial database created. With the use of LLM I basically mined all the unique entries, common phrases.

I'm not claiming it's the best or anything at all. But for codebook standards...I tried to implement all the things that would make a good code book.

  • Ability to say the same thing over and over and make it look different for mitigation against frequency analysis.
  • Easy, secure, shuffling
  • customizable
  • Assisted composing
  • Exportable
  • Long term rotating key schema
  • Conclusive and established database
  • Portable
[–] jasory@programming.dev 1 points 3 days ago (1 children)

Why did you use an LLM for the frequency tables? The "most common words used" is very useful data and as such there are many already existing compilations, used by things like spell checkers. The Linux system dictionaries are one example.

The fact that you completely ignore that simply using a larger RSA key would both be faster and more secure than your approach, doesn't inspire confidence either.

(It's also in python which is basically unusable. )

I used a LLM to create my database because it is not only a collection of words, but common phrases. Plus not only can the LLM format the database how I want it so it's interpretable to the program, it can build the database and included all the appropriate amount of duplicates.

The fact that you completely ignore that simply using a larger RSA key would both be faster and more secure than your approach, doesn't inspire confidence either.

The goal was to not use any modern crypto... Codebooks have been used for a very long time and are secure with proper key management.

This is an attempt at a modern codebook. It tackles most all of the shortcomings of previous iterations.

(It's also in python which is basically unusable. )

Haha.