Bug 62156 - p11-kit specific format for storing objects
Summary: p11-kit specific format for storing objects
Status: RESOLVED FIXED
Alias: None
Product: p11-glue
Classification: Unclassified
Component: p11-kit (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Stef Walter
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 62064
  Show dependency treegraph
 
Reported: 2013-03-11 09:27 UTC by Stef Walter
Modified: 2013-03-19 13:55 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
url: Split out the URL encoding and decoding functions (17.79 KB, patch)
2013-03-15 17:18 UTC, Stef Walter
Details | Splinter Review
trust: Support a p11-kit specific serialization format (45.50 KB, patch)
2013-03-15 17:18 UTC, Stef Walter
Details | Splinter Review
lexer: Make a lexer for our config file format (23.53 KB, patch)
2013-03-15 17:19 UTC, Stef Walter
Details | Splinter Review

Description Stef Walter 2013-03-11 09:27:30 UTC
We need to create a p11-kit specific PKCS#11 attribute/object storage format for storage of arbitrary objects.

This is required by the future tools which will create and modify trust policy information in arbitrary ways.

Since there is no way to represent distrust information for a serial+issuer in the formats currently loaded by the p11-kit trust module, this is needed to represent those.
Comment 1 Stef Walter 2013-03-15 17:18:52 UTC
Created attachment 76583 [details] [review]
url: Split out the URL encoding and decoding functions
Comment 2 Stef Walter 2013-03-15 17:18:56 UTC
Created attachment 76584 [details] [review]
trust: Support a p11-kit specific serialization format
Comment 3 Stef Walter 2013-03-15 17:19:12 UTC
Created attachment 76585 [details] [review]
lexer: Make a lexer for our config file format
Comment 4 Stef Walter 2013-03-19 13:55:31 UTC
Merged into git master and 0.17.x releases.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.