Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Peter Gutmann
2016-10-11
saag
/arch/msg/saag/jikHpB8xXAaz0q6QdDOXTCj9aYk/
2283096
1589531
Re: [saag] software update for teeny-weeny devicesRe: [saag] software update for teeny-weeny devices
Peter Gutmann
2016-10-11
saag
/arch/msg/saag/EQ5Fq4VHUNuWsbbqF8BOJyax5_g/
2283094
1589530
Re: [saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)Re: [saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)
Peter Gutmann
2016-10-11
saag
/arch/msg/saag/ALv8eUIoCzQhCNRW4-56ykR7ml8/
2283091
1589530
Re: [saag] software update for teeny-weeny devicesRe: [saag] software update for teeny-weeny devices
Peter Gutmann
2016-10-11
saag
/arch/msg/saag/IglOKFS7YYVaExUFIYIqfdA3opg/
2283087
1589530
[saag] Proposed item for SAAG agenda - Crypto-conditions[saag] Proposed item for SAAG agenda - Crypto-conditions
Adrian Hope-Bailie
2016-10-10
saag
/arch/msg/saag/2ggKYvNcoMERSQexsGGK1Vj_514/
2282957
1589528
Re: [saag] [IPsec] trapdoor'ed DH (and RFC-5114 again)Re: [saag] [IPsec] trapdoor'ed DH (and RFC-5114 again)
Paul Wouters
2016-10-10
saag
/arch/msg/saag/aUDSn2GXIU_Vb8DJEO3OFQeS2CA/
2282865
1589529
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Mark D. Baushke
2016-10-10
saag
/arch/msg/saag/fnH5emEQ5yponj-pW1PecJsb9Pk/
2282847
1589531
Re: [saag] [IPsec] trapdoor'ed DH (and RFC-5114 again)Re: [saag] [IPsec] trapdoor'ed DH (and RFC-5114 again)
Dang, Quynh (Fed)
2016-10-10
saag
/arch/msg/saag/92M9ZFScRpFw9ZvAp3Ydwuxd398/
2282802
1589529
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Tero Kivinen
2016-10-10
saag
/arch/msg/saag/czHZnBfjGSwAtpETpev-qmORRbI/
2282784
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Tero Kivinen
2016-10-10
saag
/arch/msg/saag/slAM8hDPehElJ8RUBdWmE42Sfl8/
2282777
1589531
Re: [saag] software update for teeny-weeny devicesRe: [saag] software update for teeny-weeny devices
Hannes Tschofenig
2016-10-10
saag
/arch/msg/saag/k9zXlzyt1qkLsSmDy951aSMn_Ys/
2282743
1589530
Re: [saag] software update for teeny-weeny devicesRe: [saag] software update for teeny-weeny devices
Hannes Tschofenig
2016-10-10
saag
/arch/msg/saag/c-q1UID-cBxH_mZIbGT4ABWNdSA/
2282740
1589530
[saag] trapdoor'ed DH (and RFC-5114 again)[saag] trapdoor'ed DH (and RFC-5114 again)
Paul Wouters
2016-10-09
saag
/arch/msg/saag/l-LXRcfRuellCDoJNIGK9WhasQk/
2282659
1589529
Re: [saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)Re: [saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)
David Woodhouse
2016-10-09
saag
/arch/msg/saag/P5sjYtqiuZGikydAZNOxuEJkjsY/
2282645
1589530
Re: [saag] software update for teeny-weeny devicesRe: [saag] software update for teeny-weeny devices
Stephen Farrell
2016-10-09
saag
/arch/msg/saag/IM9axI9F3nfBgIAV3CDCFKwuhKw/
2282643
1589530
Re: [saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)Re: [saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)
Peter Gutmann
2016-10-09
saag
/arch/msg/saag/W5hYzc5QdRP-405_WLRnIxHv-lE/
2282579
1589530
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Watson Ladd
2016-10-08
saag
/arch/msg/saag/58WshRSj-23Wn3zmU5YsQDGp-EA/
2282513
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Dang, Quynh (Fed)
2016-10-08
saag
/arch/msg/saag/0p4Tacw-WJEtiR7dPaZkeCl1OHM/
2282505
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Watson Ladd
2016-10-08
saag
/arch/msg/saag/E54HMmrLdyq3Sq2mPyvfLPHVPUk/
2282501
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Dang, Quynh (Fed)
2016-10-08
saag
/arch/msg/saag/QrTirxfkY2DaQ8KNYkiVAfOpdR8/
2282499
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Watson Ladd
2016-10-07
saag
/arch/msg/saag/lVYmBWrsZoyoFQl8dUiFe4bfMHY/
2282406
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Panos Kampanakis (pkampana)
2016-10-07
saag
/arch/msg/saag/-hqvMiGHabBWJ34tRiJyqsiWA_g/
2282394
1589531
[saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)[saag] software update for teeny-weeny devices (was: Fwd: [Iotsu] Initial version of the IoTSU workshop report submitted)
Stephen Farrell
2016-10-07
saag
/arch/msg/saag/DjrFhtsCgubc53FFXjXoyY7NGto/
2282330
1589530
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Yoav Nir
2016-10-07
saag
/arch/msg/saag/1Lix9teLE4NHfhgTwJAOKTjIJw4/
2282223
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Tero Kivinen
2016-10-07
saag
/arch/msg/saag/Onj21JeKIBgkmshV5m7b0VR03Pg/
2282168
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Stephen Farrell
2016-10-07
saag
/arch/msg/saag/CiVlZgyrScTw2dujUhliMV1azQw/
2282110
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Jeremy Harris
2016-10-07
saag
/arch/msg/saag/qgGwKUMhf_PAqMtCpkzSn4jh7As/
2282069
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Peter Gutmann
2016-10-07
saag
/arch/msg/saag/bnuURcz2_P8JaYbNcAyhzcAbNmc/
2282012
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Viktor Dukhovni
2016-10-06
saag
/arch/msg/saag/3WjsJHO2IEzT5JIpuvkCNb8RxDU/
2281816
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Watson Ladd
2016-10-06
saag
/arch/msg/saag/CaGJDQe4enX5vPidh1FRp-d_r6o/
2281814
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Jeffrey Walton
2016-10-06
saag
/arch/msg/saag/SonOi7i-mZOv20kE5BG1kHJuvhE/
2281811
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Yoav Nir
2016-10-06
saag
/arch/msg/saag/fq_OslKs5spW7DizIWPdgXP-8Rs/
2281801
1589531
Re: [saag] Possible backdoor in RFC 5114Re: [saag] Possible backdoor in RFC 5114
Jeffrey Walton
2016-10-06
saag
/arch/msg/saag/Rmu4h-G-PbJ48PrcYkHVSufvdt8/
2281794
1589531
[saag] Possible backdoor in RFC 5114[saag] Possible backdoor in RFC 5114
Watson Ladd
2016-10-06
saag
/arch/msg/saag/GYTtVmXjUdIPZtS_vHmf8MzrJMg/
2281786
1589531
Re: [saag] SecEvent CharterRe: [saag] SecEvent Charter
Kent Watsen
2016-09-28
saag
/arch/msg/saag/t724NNQOYf7RdcXvK78efK8W2Ag/
2279000
1589532
[saag] SecEvent Charter[saag] SecEvent Charter
Kathleen Moriarty
2016-09-27
saag
/arch/msg/saag/U40sy01fbT_ZrqPhcxicShCmh08/
2278908
1589532
Re: [saag] [Spasm] Best practices for applications using X.509 client certificatesRe: [saag] [Spasm] Best practices for applications using X.509 client certificates
Olle E. Johansson
2016-09-27
saag
/arch/msg/saag/6Fifc5yod_GkuT-5iJwIl2PehAw/
2278593
1589535
Re: [saag] [Spasm] Best practices for applications using X.509 client certificatesRe: [saag] [Spasm] Best practices for applications using X.509 client certificates
Nikos Mavrogiannopoulos
2016-09-27
saag
/arch/msg/saag/4pIZWyN9CDhopoFw39J3W0RQ0Zs/
2278546
1589535
Re: [saag] [Spasm] Best practices for applications using X.509 client certificatesRe: [saag] [Spasm] Best practices for applications using X.509 client certificates
David Woodhouse
2016-09-26
saag
/arch/msg/saag/LVk8CiZyCyn1zu6UeEtpHZQvfWA/
2278452
1589535
Re: [saag] [Spasm] Best practices for applications using X.509 client certificatesRe: [saag] [Spasm] Best practices for applications using X.509 client certificates
David Woodhouse
2016-09-26
saag
/arch/msg/saag/YvMJz48jFtBejw7VnRBEx8iUGe4/
2278447
1589535