-
Following up with my [pull request](https://github.com/hyperledger/fabric/pull/3343) that implemented the support for ed25519 keys in fabric, I had trouble with signing transactions with such keys.
…
-
Current kube logstream reads agent tokens from the K8s pod spec and then writes to the agent log endpoint. This has a few flaws:
1. The agent token needs to be readable by kube logstream, which means…
-
**Background context**
Following on from #11009 consider making the signing/{id} endpoint public. There's no real need for auth here because it's just the public keys
**Specification**
- Project:…
-
The way releases are currently signed depends on a single, personal key.
We need a mechanism that allows us to sign releases in a secure way without directly attaching it to an individual person.
…
-
A pop-up window alerting the user that they are generating or using keys tweaked with the contract. They must accept to continue. There is already a function used for Export > addresses.
-
* **Version**: 73f660bee008e1e4f8d310158c1258b65b53f959
* **Platform**: All
* **Subsystem**: Server
The `spiffe_refresh_hint` parameter of a bundle represents a suggestion for when a consumer sho…
-
STR:
* Sign in on a new device
* Verify against a device which, for some reason, does not have a copy of the private cross-signing keys. (It's not entirely clear how to get into this situation; on…
-
Sparkle extracts zip, tar, and dmg archives before validating the archive and validating the Apple code signing identity of the app contained inside the archives. This allows [key rotation](https://sp…
-
I like that you're serious about [explaining people how to properly verify releases](https://github.com/LN-Zap/zap-desktop/blob/master/docs/SIGNATURES.md). And thought I would throw in this additional…
-
As promised during the previous DCP WG call, here I create the issue to introduce the value of having the parameters jwks within the openid4vci metadata, as proposed also in the federation wallet draf…