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 <[email protected]>

def pytest_addoption(parser):
    parser.addoption("--port", type=str, help="default is 2244 local, 22 remote")
    parser.addoption("--dbclient", type=str, default="../dbclient")
    parser.addoption("--dropbear", type=str, default="../dropbear")
    parser.addoption("--hostkey", type=str, help="required unless --remote")
    parser.addoption("--remote", type=str, help="remote host")
    parser.addoption("--user", type=str, help="optional username")

def pytest_configure(config):
    opt = config.option
    if not opt.hostkey and not opt.remote:
        raise Exception("--hostkey must be given")
    if not opt.port:
        if opt.remote:
            opt.port = "22"
        else:
            opt.port = "2244"