summaryrefslogtreecommitdiff
path: root/regress/limit-keytype.sh
Commit message (Collapse)AuthorAgeFilesLines
* upstream: s/PubkeyAcceptedKeyTypes/PubkeyAcceptedAlgorithms/djm@openbsd.org2021-02-251-9/+9
| | | | OpenBSD-Regress-ID: 3dbc005fa29f69dc23d97e433b6dffed6fe7cb69
* upstream: test security key host keys in addition to user keysdjm@openbsd.org2019-12-211-2/+2
| | | | OpenBSD-Regress-ID: 9fb45326106669a27e4bf150575c321806e275b1
* upstream: test FIDO2/U2F key types; ok markus@djm@openbsd.org2019-11-271-3/+14
| | | | OpenBSD-Regress-ID: 367e06d5a260407619b4b113ea0bd7004a435474
* upstream: skip security-key key types for tests until we have adjm@openbsd.org2019-11-011-2/+2
| | | | | | dummy U2F middleware to use. OpenBSD-Regress-ID: 37200462b44334a4ad45e6a1f7ad1bd717521a95
* upstream: Restrict limit-keytype to types supported by build. Thisdtucker@openbsd.org2019-07-261-16/+40
| | | | | | means we have to skip a couple tests when only one key type is supported. OpenBSD-Regress-ID: 22d05befb9c7ce21ce8dc22acf1ffe9e2ef2e95e
* upstream: exlicitly include RSA/SHA-2 keytypes indjm@openbsd.org2018-03-141-4/+5
| | | | | | PubkeyAcceptedKeyTypes here OpenBSD-Regress-ID: 954d19e0032a74e31697fb1dc7e7d3d1b2d65fe9
* upstream commitdjm@openbsd.org2015-10-291-1/+19
| | | | | | | regress test for "PubkeyAcceptedKeyTypes +..." inside a Match block Upstream-Regress-ID: 246c37ed64a2e5704d4c158ccdca1ff700e10647
* upstream commitdtucker@openbsd.org2015-10-291-2/+2
| | | | | | | | Fix typo certopt->certopts in shell variable. This would cause the test to hang at a host key prompt if you have an A or CNAME for "proxy" in your local domain. Upstream-Regress-ID: 6ea03bcd39443a83c89e2c5606392ceb9585836a
* upstream commitdjm@openbsd.org2015-10-061-10/+9
| | | | | | | regress test for CertificateFile; patch from Meghana Bhat via bz#2436 Upstream-Regress-ID: e7a6e980cbe0f8081ba2e83de40d06c17be8bd25
* upstream commitdjm@openbsd.org2015-01-151-0/+80
regress test for PubkeyAcceptedKeyTypes; ok markus@
View Lorry Controller Status