[websec] #54: Specify a report-only mode

2012-10-18 Thread websec issue tracker
#54: Specify a report-only mode Should there be a report-only mode, allowing site operators to see how using HPKP would affect their site's operation in browsers supporting HPKP? (Probably.) If so, specify how that mode would work. -- -+--

Re: [websec] #54: Specify a report-only mode

2012-10-18 Thread websec issue tracker
#54: Specify a report-only mode Changes (by palmer@…): * status: new = assigned -- -+--- Reporter: palmer@… | Owner: palmer@… Type: defect | Status: assigned Priority: major| Milestone: Component:

Re: [websec] #54: Specify a report-only mode

2012-10-18 Thread Chris Palmer
On Thu, Oct 18, 2012 at 4:56 PM, websec issue tracker trac+web...@trac.tools.ietf.org wrote: #54: Specify a report-only mode Should there be a report-only mode, allowing site operators to see how using HPKP would affect their site's operation in browsers supporting HPKP? (Probably.) If

Re: [websec] Fwd: New Version Notification for draft-ietf-websec-key-pinning-03.txt

2012-10-18 Thread Chris Palmer
On Tue, Oct 16, 2012 at 1:16 PM, Yoav Nir y...@checkpoint.com wrote: Good to see this. Do you intend to publish another revision by the draft submission cutoff date next Monday? It's quite possible, but I can't guarantee it right now. Or would you like us to discuss these issues to resolve

Re: [websec] #54: Specify a report-only mode

2012-10-18 Thread Ryan Sleevi
On Thu, October 18, 2012 5:17 pm, Chris Palmer wrote: On Thu, Oct 18, 2012 at 4:56 PM, websec issue tracker trac+web...@trac.tools.ietf.org wrote: #54: Specify a report-only mode Should there be a report-only mode, allowing site operators to see how using HPKP would affect their