Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why do all Triplesec ciphertexts start with "1c94d7de0000000"? #84

Open
firepacket opened this issue Aug 27, 2021 · 2 comments
Open

Why do all Triplesec ciphertexts start with "1c94d7de0000000"? #84

firepacket opened this issue Aug 27, 2021 · 2 comments

Comments

@firepacket
Copy link

firepacket commented Aug 27, 2021

You know some of us in the security field value not having blatantly identifiable markings in our ciphertext.

Now I understand there may be reasons for some type of header that denotes... something.

But if this text is LITERALLY ALAWAYS THE SAME why is there at all?

@AndersTornkvist
Copy link

The first four bytes (8 characters in the hex representation) is a magic marker. The next four bytes is the version number (8 characters in the hex representation). So for version 4, it will start with
1c 94 d7 de (magic)
00 00 00 04 (version 4)

You can find it in the source:

header : [ 0x1c94d7de, 4 ] # The magic #, and also the version #

And read more about the format at Keybase TripleSec website: https://keybase.io/triplesec

@firepacket
Copy link
Author

firepacket commented Jan 19, 2022

Read my updated complaint issue #86

I didn't even realize I had already posted this last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants