Re: [websec] #55: Clarify that the newest pinning information takes precedenceRe: [websec] #55: Clarify that the newest pinning information takes precedence
Yoav Nir
2013-03-29
websec
/arch/msg/websec/HLXHaBL0nCj3Iz4hPNCeEZjUWA0/
1505025
1665168
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Yoav Nir
2013-03-29
websec
/arch/msg/websec/D12rTOXLElmeYXD1wnreDshaWXI/
1505024
1665128
Re: [websec] #55: Clarify that the newest pinning information takes precedenceRe: [websec] #55: Clarify that the newest pinning information takes precedence
Tom Ritter
2013-03-28
websec
/arch/msg/websec/2vunaM9YNBRblRZy736EuiucCpg/
1505023
1665168
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Joseph Bonneau
2013-03-27
websec
/arch/msg/websec/tZyUpX4RdzFOlrfCXDPL1SRCeHg/
1505022
1665128
Re: [websec] #55: Clarify that the newest pinning information takes precedenceRe: [websec] #55: Clarify that the newest pinning information takes precedence
websec issue tracker
2013-03-27
websec
/arch/msg/websec/HVQqDVI0LbRaozkye5zL8qApNRk/
1505021
1665168
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Chris Palmer
2013-03-27
websec
/arch/msg/websec/CJ43ij9gRoA1NcJBnNHebIwr2F0/
1505020
1665128
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Trevor Perrin
2013-03-23
websec
/arch/msg/websec/FG2UZb2Ximi-0GsJlM_mUWilB1c/
1505019
1665128
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Tobias Gondrom
2013-03-23
websec
/arch/msg/websec/_eogWPT9Nn3VRVYEZC7um45kzuM/
1505018
1665128
Re: [websec] #56: Specify includeSubdomains directive for HPKPRe: [websec] #56: Specify includeSubdomains directive for HPKP
Yoav Nir
2013-03-23
websec
/arch/msg/websec/cP2TAEGiAee6372DR7zBSWv9wlU/
1505017
1665158
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Yoav Nir
2013-03-23
websec
/arch/msg/websec/cjdmv3CV65scjB4PgHuV8N3tjC8/
1505016
1665128
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Joseph Bonneau
2013-03-22
websec
/arch/msg/websec/CwZtlmYCfBLdB-1srk6zU-Gy57A/
1505015
1665128
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
Trevor Perrin
2013-03-22
websec
/arch/msg/websec/gTlMENnnUoMBbnzohwyUYsNiE0c/
1505014
1665128
Re: [websec] #56: Specify includeSubdomains directive for HPKPRe: [websec] #56: Specify includeSubdomains directive for HPKP
websec issue tracker
2013-03-22
websec
/arch/msg/websec/TZzPcMimeNZr3fupFtPWBbGnM4o/
1505013
1665158
Re: [websec] #56: Specify includeSubdomains directive for HPKPRe: [websec] #56: Specify includeSubdomains directive for HPKP
websec issue tracker
2013-03-22
websec
/arch/msg/websec/eU-eanjOrXgxCE1tvUJjFUchfVo/
1505012
1665158
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
websec issue tracker
2013-03-22
websec
/arch/msg/websec/SChidPFlTU_paR9NUxDX_tUZ0AY/
1505011
1665128
Re: [websec] #57: Re-add an upper limit to max-ageRe: [websec] #57: Re-add an upper limit to max-age
websec issue tracker
2013-03-22
websec
/arch/msg/websec/bdjC8pbLd9Mun55tCDlMr_-9_78/
1505010
1665128
[websec] #57: Re-add an upper limit to max-age[websec] #57: Re-add an upper limit to max-age
websec issue tracker
2013-03-22
websec
/arch/msg/websec/mZK-48jmO72C3nwFF60bfDxj5_0/
1505009
1665128
Re: [websec] Session Continuation = Session Bound State?Re: [websec] Session Continuation = Session Bound State?
Richard Barnes
2013-03-20
websec
/arch/msg/websec/ENszr5BRytxaGfyjevEHEMKISQc/
1505008
1665130
[websec] Starting work on Session Continuation/Bound State/Management (was: Session Continuation = Session Bound State?)[websec] Starting work on Session Continuation/Bound State/Management (was: Session Continuation = Session Bound State?)
Yoav Nir
2013-03-20
websec
/arch/msg/websec/SSE-R6I4Ubln6oc-PWR00N-y3uM/
1505007
1665130
Re: [websec] Session Continuation = Session Bound State?Re: [websec] Session Continuation = Session Bound State?
Nico Williams
2013-03-19
websec
/arch/msg/websec/AmQpWb51OvHxMdKKD3Rl3Xm2Mwk/
1505006
1665130
Re: [websec] Session Continuation = Session Bound State?Re: [websec] Session Continuation = Session Bound State?
Harry Halpin
2013-03-19
websec
/arch/msg/websec/1uQr-jXUyvinWLGC-wccD_YVv3g/
1505005
1665130
Re: [websec] Session Continuation = Session Bound State?Re: [websec] Session Continuation = Session Bound State?
Tobias Gondrom
2013-03-19
websec
/arch/msg/websec/8BfS7OLiAvdiJkvOFQXUNg6saTk/
1505004
1665130
Re: [websec] Session Continuation = Session Bound State?Re: [websec] Session Continuation = Session Bound State?
Yoav Nir
2013-03-18
websec
/arch/msg/websec/ME1vq1fJb94I9AWsyFunATzYXPw/
1505003
1665130
[websec] Some issues with key-pinning[websec] Some issues with key-pinning
Yoav Nir
2013-03-18
websec
/arch/msg/websec/oPywokuzsAe0dSboPBruGLljnGg/
1505002
1665129
Re: [websec] #52: Clarification of section 2.3.1Re: [websec] #52: Clarification of section 2.3.1
websec issue tracker
2013-03-14
websec
/arch/msg/websec/AO1XE9mMenRdSzW-lWc9extnRuE/
1505001
1665191
[websec] Session Continuation = Session Bound State?[websec] Session Continuation = Session Bound State?
Phillip Hallam-Baker
2013-03-14
websec
/arch/msg/websec/mCZm7ERLAf9XwUEf3OCqAdBdjWE/
1505000
1665130
[websec] Preliminary Minutes Uploaded[websec] Preliminary Minutes Uploaded
Yoav Nir
2013-03-14
websec
/arch/msg/websec/0NaDfNqQl5DK-uaJQa8q9ZBPx-8/
1504999
1665131
[websec] Slides uploaded[websec] Slides uploaded
Yoav Nir
2013-03-12
websec
/arch/msg/websec/itnkytNJc5n68erImm97rUD5s-s/
1504998
1665132
Re: [websec] Issue 55 - Key pinning should clarify that the newest pinning information takes precedenceRe: [websec] Issue 55 - Key pinning should clarify that the newest pinning information takes precedence
Tom Ritter
2013-03-07
websec
/arch/msg/websec/ND6TFawmxYXe3SE96LyNYB2MlVA/
1504997
1665135
Re: [websec] [Ietf-message-headers] HTTP 'Origin' permanent and provisionalRe: [websec] [Ietf-message-headers] HTTP 'Origin' permanent and provisional
Bjoern Hoehrmann
2013-03-07
websec
/arch/msg/websec/-2Uz79lmGrRZpi1P1KXJjN_ip-s/
1504996
1665141
Re: [websec] Issue 52 - Key pinning draft should clarify max-age as requiredRe: [websec] Issue 52 - Key pinning draft should clarify max-age as required
Yoav Nir
2013-03-06
websec
/arch/msg/websec/cv-FEqTzqiotP2xwBCtrIzqjunI/
1504995
1665137
Re: [websec] Issue 55 - Key pinning should clarify that the newest pinning information takes precedenceRe: [websec] Issue 55 - Key pinning should clarify that the newest pinning information takes precedence
Ryan Sleevi
2013-03-06
websec
/arch/msg/websec/vzteiMsFnEkmULxMb2aIHY1v_GI/
1504994
1665135
Re: [websec] Issue 52 - Key pinning draft should clarify max-age as requiredRe: [websec] Issue 52 - Key pinning draft should clarify max-age as required
Tom Ritter
2013-03-06
websec
/arch/msg/websec/DkZR1YAR0aDD10TPtadRRT-XuaU/
1504993
1665137
Re: [websec] Issue 55 - Key pinning should clarify that the newest pinning information takes precedenceRe: [websec] Issue 55 - Key pinning should clarify that the newest pinning information takes precedence
Tom Ritter
2013-03-06
websec
/arch/msg/websec/OJ4C04TXrVKVHPBG9sG3_p9dlGQ/
1504992
1665135
Re: [websec] Issue 56 - specify includeSubDomains for key pinningRe: [websec] Issue 56 - specify includeSubDomains for key pinning
Tom Ritter
2013-03-06
websec
/arch/msg/websec/zATo0HDrKOWd5v7eAf4uNnIDAgs/
1504991
1665134
Re: [websec] Issue 54 - Adding a report-only modeRe: [websec] Issue 54 - Adding a report-only mode
Tom Ritter
2013-03-06
websec
/arch/msg/websec/rB6MXDWeDV6fD5lScSuXCTjFNIY/
1504990
1665133
Re: [websec] Issue 53 - Key pinning should clarify status of pin validation with private trust anchorsRe: [websec] Issue 53 - Key pinning should clarify status of pin validation with private trust anchors
Tom Ritter
2013-03-06
websec
/arch/msg/websec/1wNOMHvKh3bL336YD7SJnpAJ9Cc/
1504989
1665136
Re: [websec] Issue 53 - Key pinning should clarify status of pin validation with private trust anchorsRe: [websec] Issue 53 - Key pinning should clarify status of pin validation with private trust anchors
Yoav Nir
2013-03-05
websec
/arch/msg/websec/25piQ98LtauKYNHHSBQi0IT2DEc/
1504988
1665136
Re: [websec] Issue 53 - Key pinning should clarify status of pin validation with private trust anchorsRe: [websec] Issue 53 - Key pinning should clarify status of pin validation with private trust anchors
Daniel Kahn Gillmor
2013-03-05
websec
/arch/msg/websec/irLQVQBDysqR5RWFDQz_UJm-2oI/
1504987
1665136
[websec] Issue 54 - Adding a report-only mode[websec] Issue 54 - Adding a report-only mode
Ryan Sleevi
2013-03-05
websec
/arch/msg/websec/nKLtICFnpe7qG9ZhN4NFyoSArO4/
1504986
1665133
40 Messages