RNCryptor-Spec
RNCryptor-Spec copied to clipboard
Spec does not define or discuss padding
If the padding is application specific the spec should at least warn implementiere about it. Defining a padding as part of the format might be better.
It's not application specific. It requires PKCS#7 padding. I'll update the spec to say so.
It's not application specific. It requires PKCS#7 padding. I'll update the spec to say so.
@rnapier I see v4 spec mentions this, https://github.com/RNCryptor/RNCryptor-Spec/blob/7aa27298df4d66476e06efeeeeecc6228df6cfbd/draft-RNCryptor-Spec-v4.0.md?plain=1#L55 Does this apply to the previous (current) specs? I've not dug into the code to determine this.
It’s not in the draft yet, btw when you touch the draft I would also specify the encoding of the password bytes, namely utf-8 (utf-16 is typically regarded as having too much structure with the 0 bytes).
and also I am afraid the primitives all get outdated by now (cbc, sha1, etm, no chunking, …)