Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARC revision 1.1 (clarification): security issues #12

Closed
cleymour opened this issue Jun 16, 2015 · 3 comments
Closed

WARC revision 1.1 (clarification): security issues #12

cleymour opened this issue Jun 16, 2015 · 3 comments

Comments

@cleymour
Copy link

Definition: It is written in the WARC standards (6.3.2 and 6.5.2) : "This document does not specify conventions for recording information about the 'https' secure socket transaction, such as certificates exchanged, consulted, or verified".
This sentence looks misleading: it should not mean that implementers shouldn't record this kind of information (which is provenance information), but that the standard doesn't give any advice on how to do it.

Decision: This should be more clearly explained. One or two examples with possible (optional) solutions could be provided.

Action: Jack Cushman to propose a formulation.

@anjackson
Copy link
Member

Implementation first please! :-) Could consider clarification that this is not in scope as practice is not established..

@saraaubry
Copy link

The following changes have been integrated in the revised ISO draft during the ISO working group meeting on November 16-17, 2015:
at the end of section 6.3.2 and 6.5.2, replace/add last sentence: Conventions for recording information about the 'https' secure socket transaction, such as certificates exchanged, consulted, or verified, are not in the scope of this International Standard.

@saraaubry
Copy link

Included in WARC 1.1.

@anjackson anjackson added this to the The WARC Format 1.1 milestone Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants