dropbear/sk-ed25519.h

#ifndef DROPBEAR_SK_ED25519_H_
#define DROPBEAR_SK_ED25519_H_

#include "includes.h"

#if DROPBEAR_SK_ED25519

#include "buffer.h"
#include "ed25519.h"

int buf_sk_ed25519_verify(buffer *buf, const dropbear_ed25519_key *key, const buffer *data_buf,
			const char* app, unsigned int applen,
			unsigned char sk_flags_mask);

#endif

#endif /* DROPBEAR_SK_ED25519_H_ */
Implement server-side support for sk-ecdsa U2F-backed keys (#142) * Implement server-side support for sk-ecdsa U2F-backed keys * Fix out-of-bounds read on normal ecdsa-sha2-[identifier] keys * Fix one more potential out-of-bounds read * Check if nistp256 curve is used in sk-ecdsa-sha2- key It's the only allowed curve per PROTOCOL.u2f specification * Implement server-side support for sk-ed25519 FIDO2-backed keys * Keys with type sk-* make no sense as host keys, so they should be disabled * fix typo * Make sk-ecdsa call buf_ecdsa_verify This reduces code duplication, the SK code just handles the different message format. * Reduce sk specific code The application id can be stored in signkey, then we don't need to call sk-specific functions from svr-authpubkey * Remove debugging output, which causes compilation errors with DEBUG_TRACE disabled * Proper cleanup of sk_app Co-authored-by: Matt Johnston <matt@codeconstruct.com.au> 2022-01-22 13:53:04 +00:00			`#ifndef DROPBEAR_SK_ED25519_H_`
			`#define DROPBEAR_SK_ED25519_H_`

			`#include "includes.h"`

			`#if DROPBEAR_SK_ED25519`

			`#include "buffer.h"`
			`#include "ed25519.h"`

Implement no-touch-required and verify-requred for authorized_keys file 2022-06-11 10:35:06 +00:00			`int buf_sk_ed25519_verify(buffer buf, const dropbear_ed25519_key key, const buffer *data_buf,`
			`const char* app, unsigned int applen,`
			`unsigned char sk_flags_mask);`
Implement server-side support for sk-ecdsa U2F-backed keys (#142) * Implement server-side support for sk-ecdsa U2F-backed keys * Fix out-of-bounds read on normal ecdsa-sha2-[identifier] keys * Fix one more potential out-of-bounds read * Check if nistp256 curve is used in sk-ecdsa-sha2- key It's the only allowed curve per PROTOCOL.u2f specification * Implement server-side support for sk-ed25519 FIDO2-backed keys * Keys with type sk-* make no sense as host keys, so they should be disabled * fix typo * Make sk-ecdsa call buf_ecdsa_verify This reduces code duplication, the SK code just handles the different message format. * Reduce sk specific code The application id can be stored in signkey, then we don't need to call sk-specific functions from svr-authpubkey * Remove debugging output, which causes compilation errors with DEBUG_TRACE disabled * Proper cleanup of sk_app Co-authored-by: Matt Johnston <matt@codeconstruct.com.au> 2022-01-22 13:53:04 +00:00
			`#endif`

			`#endif /* DROPBEAR_SK_ED25519_H_ */`