crypto-inventory 0.3.0 and the control-plane planner after the second run on a tree that is not ours (libsignal): BoringSSL, Noise hfs, libcrux Kyber, the libsignal Java/Node API; self-signed trust anchors are blocked, test code is LOW with its own scope
This commit is contained in:
1 parent
42b049ef04
commit
e453c0c42d
35 files changed
+675
-51
No files matched your search
@@ -0,0 +1,10 @@
|
||||
// Fixtura negativa: aceleasi nume scurte ca in API-ul @signalapp/libsignal-client (PrivateKey.generate, KEMKeyPair.generate, hkdf,
|
||||
// Aes256GcmSiv.new), dar importate din alta parte: nu sunt libsignal, deci nu produc nicio gasire.
|
||||
import { PrivateKey, KEMKeyPair, hkdf, Aes256GcmSiv } from '../chei-proprii';
|
||||
|
||||
export function chei(ikm: Buffer, key: Buffer) {
|
||||
const priv = PrivateKey.generate();
|
||||
const kem = KEMKeyPair.generate();
|
||||
const okm = hkdf(32, ikm, Buffer.from('info'), null);
|
||||
return { priv, kem, okm, siv: Aes256GcmSiv.new(key) };
|
||||
}
|
||||
Reference in new issue
Block a user