Try   HackMD

Scribble

tags: random

Notes

Jan 20 2022 scoping meeting notes

Repo: wabbit-networks.io/softwares

Supported cases:

  1. wabbit-networks.io/software <– repo match
  2. wabbit-networks.io/software/* <– match immediate namespace
    wabbit-networks.io/software/prod-good
  3. wabbit-networks.io/software/*/* <– wabbit-networks.io/software/prod/asd <– will add if requried in future
  4. wabbit-networks.io/software/** <– match all nested namespaces inside software namespace

Invalid cases:

  1. wabbit-networks.io/software* <– parse error
  2. wabbit-networks.io/software/prod-* <– parse error
  3. wabbit-networks.io/software/prod-bad/<– parse error
  4. wabbit-networks.io/soft* <– parse error

wabbit-networks.io/software/iamge

wabbit-networks.io/software/*
wabbit-networks.io/software/**

wabbit-networks.io/software/prod-good/image1

Comments

fwiw, Bash hides ** under the "globstar" feature, which might have some wording that's worth looking at for documenting this: https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#The-Shopt-Builtin-1
https://git-scm.com/docs/gitignore

wabbit-networks.io/software/iamge1
wabbit-networks.io/software/dev/testimage1

Last changed by 
 
Pritesh Bandi
8
565

Read more

Untitled

// Verifier is a generic interface for verifying an artifact.type Verifier interface {// Verify verifies the signature blob signature against the target OCI// artifact with manifest descriptor desc, and returns the outcome upon// successful verification.// If nil signature is present and the verification level is not &#39;skip&#39;,// an error will be returned.Verify(ctx context.Context, desc ocispec.Descriptor, signature []byte, opts VerifierVerifyOptions) (*VerificationOutcome, error)}

Mar 18, 2024
Sign arbitrary data

To support signing of

Oct 28, 2023
Notation Debug Logs

➜ ./notation verify $IMAGE -d Warning: Always sign the artifact using digest(`@sha256:...`) rather than a tag(`:v1`) because tags are mutable and a tag reference can point to a different artifact than the one signed Resolved artifact tag `v1` to digest `sha256:cd5eef6b6a6750c9850a8d7b1a5435f35f1a1808d66c74e265f6b7ec290bea47` before signing INFO[2022-12-02T13:14:39+08:00] passing a nil signature to check &apos;skip&apos; level DEBU[2022-12-02T13:14:39+08:00] verify signature against artifact referenced as localhost:5000/net-monitor@sha256:cd5eef6b6a6750c9850a8d7b1a5435f35f1a1808d66c74e265f6b7ec290bea47 DEBU[2022-12-02T13:14:39+08:00] verification level: &amp;{Name:strict Enforcement:map[authenticTimestamp:enforce authenticity:enforce expiry:enforce integrity:enforce revocation:enforce]} ERRO[2022-12-02T13:14:39+08:00] integrity validation failed. Failure reason: unable to parse the digital signature, error : signature envelope format with media type &quot;&quot; is not supported INFO[2022-12-02T13:14:39+08:00] check over. not &apos;skip&apos; level DEBU[2022-12-02T13:14:39+08:00] Request URL: &quot;http://localhost:5000/v2/net-monitor/manifests/sha256:cd5eef6b6a6750c9850a8d7b1a5435f35f1a1808d66c74e265f6b7ec290bea47&quot; DEBU[2022-12-02T13:14:39+08:00] Request method: &quot;HEAD&quot;

Mar 14, 2023
[Draft] Verification extensibility

This is a continuation of [Draft] Notation Extensibility for Signing and Verification doc. Requirements The plugin&apos;s verification API MUST be signature envelope format agnostic and MUST work seamlessly with different signature envelope formats. If signature needs plugin for verification then the signature MUST convey plugin name and version required for verification. During signature verification, if the required plugin is unavailable then Notary v2 MUST fails the signature verification. :::info PR Begins - This is in early brainstorming stage

Feb 5, 2022
Read more from Pritesh Bandi
Published on HackMD