Skip to content

Conversation

ch4r10t33r
Copy link
Collaborator

No description provided.

Comment on lines +26 to +34
1. **Key Derivation Function (KDF)**
- Replaces PBKDF2 with more secure, memory-hard alternatives:
- `argon2id` (preferred)

2. **Authenticated Encryption**
- Encryption must use an AEAD (Authenticated Encryption with Associated Data) scheme:
- `aes-256-gcm`
- or `xchacha20-poly1305`
- MAC (message authentication code) is integrated into the encryption tag, eliminating the need for a separate field
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gballet you have any opinions here?

@RazorClient
Copy link

hey
tamaghna from zeam here
do we know how much the private keys sizes are

here are some ballpark no (there are with the sha hash fn)

  • (SHA3-256, $L=2^{18}$):**

  • $w=4,: ≈ 560 MiB

  • $w=2, : ≈ 1.15 GiB

so the idea would be to store the prf keys and generate the epoch based keys when required
PRF seed (32 B) + $P$ (≈32 B) → ≈ 64 B persistent secret

What have you guys implemented/thought about this ??

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

Successfully merging this pull request may close these issues.

3 participants