Subject
From
Date
List
[Acme] Directory metadata; wildcard support; conditional authz creation[Acme] Directory metadata; wildcard support; conditional authz creation
Hugo Landau
2016-01-31
acme
/arch/msg/acme/RNiPetVQZengyDpd3kkwqTgq_pI/
2151773
1067618
Re: [Acme] Directory metadata; wildcard support; conditional authz creationRe: [Acme] Directory metadata; wildcard support; conditional authz creation
Andrew Ayer
2016-01-31
acme
/arch/msg/acme/eLu_xKqW9BYrJvS11qCAwzByUdk/
2151782
1067618
Re: [Acme] Directory metadata; wildcard support; conditional authz creationRe: [Acme] Directory metadata; wildcard support; conditional authz creation
Hugo Landau
2016-01-31
acme
/arch/msg/acme/EE-ldAa6Yt38oJT2w_2Gd2QGOUc/
2151786
1067618
Re: [Acme] Directory metadata; wildcard support; conditional authz creationRe: [Acme] Directory metadata; wildcard support; conditional authz creation
Andrew Ayer
2016-01-31
acme
/arch/msg/acme/Nn1fnjCkx2qZjqdprWvCouxoOtY/
2151824
1067618
Re: [Acme] Directory metadata; wildcard support; conditional authz creationRe: [Acme] Directory metadata; wildcard support; conditional authz creation
Richard Körber
2016-01-31
acme
/arch/msg/acme/8BgR2thgILhM76AzClJXApRBJiA/
2151844
1067618
Re: [Acme] Directory metadata; wildcard support; conditional authz creationRe: [Acme] Directory metadata; wildcard support; conditional authz creation
Hugo Landau
2016-01-31
acme
/arch/msg/acme/Lsx80JngVt2UYvngj-0GUe9cbC4/
2151859
1067618
[Acme] Do you have an (open source) ACME server?[Acme] Do you have an (open source) ACME server?
Salz, Rich
2016-01-29
acme
/arch/msg/acme/UwofKw4T-UmzW9hlx0oUxrWVz6U/
2151640
1067619
[Acme] dns challenges and dynamic dns services (security considerations for domain holders)[Acme] dns challenges and dynamic dns services (security considerations for domain holders)
Frederik Braun
2016-01-29
acme
/arch/msg/acme/b_e1R7wxSe-aos_kAN9lRxftKuo/
2151445
1067620
Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)
Patrick Burroughs
2016-01-29
acme
/arch/msg/acme/Zdt2fPi6-MzyPgM3hFwDTvXwcLg/
2151465
1067620
Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)
moparisthebest
2016-01-29
acme
/arch/msg/acme/E0fSZSVjz67x6V3665A92vMaawM/
2151481
1067620
Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)
Frederik Braun
2016-01-29
acme
/arch/msg/acme/bShHMj36X57y47Rj7LkY_qWcnzY/
2151488
1067620
Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)
James Cloos
2016-01-29
acme
/arch/msg/acme/FIFPdcK2YQcUnp-SKNK7vedMR1w/
2151529
1067620
Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)Re: [Acme] dns challenges and dynamic dns services (security considerations for domain holders)
Andrew Ayer
2016-01-29
acme
/arch/msg/acme/-cqQQS2Jx_lHko1vfoWYCx85Bmo/
2151544
1067620
[Acme] Predictability of http-01 challenge response[Acme] Predictability of http-01 challenge response
Hugo Landau
2016-01-26
acme
/arch/msg/acme/AzbC_ZCoQmD3PScHvJdDFQjg1zA/
2149765
1067621
Re: [Acme] Predictability of http-01 challenge responseRe: [Acme] Predictability of http-01 challenge response
Niklas Keller
2016-01-26
acme
/arch/msg/acme/ggwIVJaJcJX-wI-95MbKKwAYiiI/
2149875
1067621
Re: [Acme] Predictability of http-01 challenge responseRe: [Acme] Predictability of http-01 challenge response
Jacob Hoffman-Andrews
2016-01-26
acme
/arch/msg/acme/RoWyf5p1YBmKobuHbxF1X1KAVbk/
2150136
1067621
[Acme] Proposed changes to TLS-SNI, autorenewal removal[Acme] Proposed changes to TLS-SNI, autorenewal removal
Hugo Landau
2016-01-22
acme
/arch/msg/acme/OnLEcxUa_K30ERLIZl5kAreyyh8/
2148709
1067622
Re: [Acme] Proposed changes to TLS-SNI, autorenewal removalRe: [Acme] Proposed changes to TLS-SNI, autorenewal removal
Andrew Ayer
2016-01-22
acme
/arch/msg/acme/xy6DYIXHg2JZh29Wa9c6xRIUD2U/
2148793
1067622
Re: [Acme] Proposed changes to TLS-SNI, autorenewal removalRe: [Acme] Proposed changes to TLS-SNI, autorenewal removal
Hugo Landau
2016-01-22
acme
/arch/msg/acme/ILEqZSeQ3aodLUg98eiKeJ8p-VA/
2148813
1067622
Re: [Acme] Proposed changes to TLS-SNI, autorenewal removalRe: [Acme] Proposed changes to TLS-SNI, autorenewal removal
Andrew Ayer
2016-01-22
acme
/arch/msg/acme/LBuofru6OWUd9dc2Asb8agIik-g/
2148833
1067622
Re: [Acme] Proposed changes to TLS-SNI, autorenewal removalRe: [Acme] Proposed changes to TLS-SNI, autorenewal removal
Salz, Rich
2016-01-22
acme
/arch/msg/acme/m7idqdjX8Fau7elzvVYcAl4oO0o/
2148835
1067622
[Acme] tls-sni-01 validation compromise[Acme] tls-sni-01 validation compromise
Jehiah Czebotar
2016-01-22
acme
/arch/msg/acme/s8gaZ6ev-iqoSQjOZWUpZ41mA0M/
2148510
1067623
Re: [Acme] tls-sni-01 validation compromiseRe: [Acme] tls-sni-01 validation compromise
Martin Thomson
2016-01-22
acme
/arch/msg/acme/JK5ARGG7Gy02QlLyQ65G-H6PjXY/
2148515
1067623
Re: [Acme] tls-sni-01 validation compromiseRe: [Acme] tls-sni-01 validation compromise
Martin Thomson
2016-01-22
acme
/arch/msg/acme/bGNeK-u_Jr5ue-5nuOMf324IU6M/
2148528
1067623
Re: [Acme] tls-sni-01 validation compromiseRe: [Acme] tls-sni-01 validation compromise
Jehiah Czebotar
2016-01-22
acme
/arch/msg/acme/2TfJpQ_0rKPgHc5lHHdFePJzt54/
2148530
1067623
Re: [Acme] tls-sni-01 validation compromiseRe: [Acme] tls-sni-01 validation compromise
Peter Eckersley
2016-01-22
acme
/arch/msg/acme/VVH8IYWSbwf9QVBF6i-27hbmEC0/
2148851
1067623
Re: [Acme] tls-sni-01 validation compromiseRe: [Acme] tls-sni-01 validation compromise
Thomas Lußnig
2016-01-22
acme
/arch/msg/acme/F-yRyYk1dZuB3gGAp8cOAKG1UjA/
2148869
1067623
[Acme] Cleartext JavaScript/JSON signatures using ES6 + Google V8[Acme] Cleartext JavaScript/JSON signatures using ES6 + Google V8
Anders Rundgren
2016-01-16
acme
/arch/msg/acme/SHQaRpTllaEg-zKGMjYeu2Y3tKA/
2146488
1067624
[Acme] acme - Update to a Meeting Session Request for IETF 95[Acme] acme - Update to a Meeting Session Request for IETF 95
"IETF Meeting Session Request Tool"
2016-01-14
acme
/arch/msg/acme/ZL_jHkX_Odqjhqf8-wcajYZuSco/
2145926
1067625
[Acme] acme - New Meeting Session Request for IETF 95[Acme] acme - New Meeting Session Request for IETF 95
"IETF Meeting Session Request Tool"
2016-01-14
acme
/arch/msg/acme/4eNyGmYJ0kvP52AOvd-ukkkIFbY/
2145916
1067626
[Acme] Revoking certificates issued by an unknown ACME server[Acme] Revoking certificates issued by an unknown ACME server
Hugo Landau
2016-01-14
acme
/arch/msg/acme/UNCH86fmBaE8ceRxWTHvQng_bYM/
2145770
1067627
Re: [Acme] Revoking certificates issued by an unknown ACME serverRe: [Acme] Revoking certificates issued by an unknown ACME server
Martin Thomson
2016-01-15
acme
/arch/msg/acme/YTBc5VkeRSzelWQn-7vHGJH9xXY/
2146002
1067627
Re: [Acme] Revoking certificates issued by an unknown ACME serverRe: [Acme] Revoking certificates issued by an unknown ACME server
Hugo Landau
2016-01-15
acme
/arch/msg/acme/cb3xvQ0u2Y2NWGAIxTVK6gb0YUc/
2146086
1067627
Re: [Acme] Revoking certificates issued by an unknown ACME serverRe: [Acme] Revoking certificates issued by an unknown ACME server
Martin Thomson
2016-01-15
acme
/arch/msg/acme/NWy-eG7td9x591eErFX7iiqXIS4/
2146102
1067627
Re: [Acme] Revoking certificates issued by an unknown ACME serverRe: [Acme] Revoking certificates issued by an unknown ACME server
Salz, Rich
2016-01-15
acme
/arch/msg/acme/0NFGFHlgBMXMiGWFTSCJc71agcg/
2146284
1067627
[Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01[Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01
Albert ARIBAUD
2016-01-08
acme
/arch/msg/acme/LuqFKIYFU3CgMkfOJIFmLCEsRJE/
2137440
1067628
Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01
Salz, Rich
2016-01-08
acme
/arch/msg/acme/SK0niUV5AfLUuXUl4nUVnLSWZFA/
2137443
1067628
Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01
Albert ARIBAUD
2016-01-08
acme
/arch/msg/acme/D7criamYN8QWYueOTbNBP5izL0c/
2137458
1067628
Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01
Albert ARIBAUD
2016-01-08
acme
/arch/msg/acme/QgxRrhfivVggjqsJrQtSMSQiggc/
2141019
1067628
Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01Re: [Acme] The path to the "directory" resource should not be "/" and should be specified in draft-ietf-acme-acme-01
Martin Thomson
2016-01-08
acme
/arch/msg/acme/YULH1df5RDPfeMwaTCa5PdSShhQ/
2143698
1067628