Comments (6)
My feeling is no. Signing-spec/DSSE is intended to be "dead simple" to minimize attack surface. JWS already exists and has the requested feature. If we added it here, we'd basically be reinventing JWS.
The workaround described in the original post is a reasonable solution. Or alternatively just use JWS if it provides the features you need.
from dsse.
Can you provide some examples?
from dsse.
You may want to include information about where (e.g. machine name), when (e.g. @dlorenc's suggestion in #33), who (e.g. a decentralized identity. This is along the same lines as HTTP or SMTP headers, arguably the payloadType is just a specialized Content-Type header and could even move into this header section.
from dsse.
IMO the timestamp is conceptually part of the signature, so it might make sense in the envelope.
The machine name, etc should probably go into the payload. There's not a great spot for the machine name in the ITE-6 payload right now, though.
from dsse.
@dlorenc you're right, anything can go in the payload but that assumes you have control over the payload. If you wanted to take some arbitrary content and wrap this around it then it's nice to have a side-channel you can annotate without having to manipulate the payload.
from dsse.
Are you asking for something like a plain old 'metadata' field that can be any dict the producer wants but that people shouldn't depend on for making policy decisinos?
from dsse.
Related Issues (20)
- Add envelope version HOT 8
- Communicating signing algorithm and parameters HOT 10
- Extending DSSE to accept optional signature specific metadata HOT 26
- How to verify an envelope properly? HOT 5
- Add field for certificate chains, or explain alternative solution HOT 26
- Clarify design philosphy
- Document the sigstore/sigstore client libraries? HOT 3
- Specify DSSE Signature encoding in the Protocol or as a Parameter HOT 6
- "DSSE Multi-signature Verification" protocol lacks detail about threshold verification HOT 3
- Have you considered signing a hash digest of the payload instead of the payload itself? HOT 3
- Feature: generate DSSE language clients from the protobuf HOT 4
- reconsider threshold (aka multi-sig) verification HOT 7
- DSSE Maintainers HOT 4
- Process to enhance DSSE HOT 2
- Extending DSSE Signatures HOT 22
- DSSE Extension for Timestamping and PKI Support
- Document rationale for DSSE vs COSE etc. HOT 4
- Reducing overhead for payload encoding HOT 15
- What should be listed as parameters for signature in the protocol?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dsse.