git/master snapshot debuginfod deployed to fedora.stg server

2024-06-07 Thread Frank Ch. Eigler
Hi -

Open for your experimentation needs, on a recent fedora client and a
fresh build of elfutils,

env DEBUGINFOD_URLS='ima:enforcing https://debuginfod.stg.fedoraproject.org' \
DEBUGINFOD_IMA_CERT_PATH=/etc/keys/ima \
DEBUGINFOD_VERBOSE=1 \
debuginfod-find debuginfo /bin/ls

should result in content similar to:

Loaded pem pubkey /etc/keys/ima/fedora-39-ima.pem, keyid 388b603e
Loaded der certificate /etc/keys/ima/fedora-39-ima.der, keyid = 388b603e
Loaded pem certificate /etc/keys/ima/fedora-39-ima.cert, keyid = 388b603e
Loaded der certificate /etc/keys/ima/fedora-38-ima.der, keyid = e7b0c859
Loaded pem certificate /etc/keys/ima/fedora-38-ima.cert, keyid = e7b0c859
Loaded pem pubkey /etc/keys/ima/fedora-38-ima.pem, keyid e7b0c859
debuginfod_find_debuginfo e79defd2793644d11e45a043e6c1e6559e7c149f
server urls "ima:enforcing https://debuginfod.stg.fedoraproject.org/";
[...]
init server 0 https://debuginfod.stg.fedoraproject.org/buildid [IMA 
verification policy: enforcing]
url 0 
https://debuginfod.stg.fedoraproject.org/buildid/e79defd2793644d11e45a043e6c1e6559e7c149f/debuginfo
query 1 urls in parallel
header HTTP/2 200
[...]
header x-debuginfod-size: 453232
header x-debuginfod-archive: 
/mnt/fedora_koji_prod/koji/packages/coreutils/9.3/5.fc39/x86_64/coreutils-debuginfo-9.3-5.fc39.x86_64.rpm
header x-debuginfod-file: /usr/lib/debug/usr/bin/ls-9.3-5.fc39.x86_64.debug
header x-debuginfod-imasignature: 
030204388b603e00483046022100dd67332b59c2f9431958d0cc80ed332955c89f765dbf8aeeb4262159e457511d022100a2513d0807be86be7bda1802fe6f22b04e9e753891f106120498ca16fa28a20a
header last-modified: Thu, 18 Jan 2024 00:00:00 GMT
[...]
got file from server
Searching for ima keyid 388b603e
Computed ima signature verification res=0
valid signature


Metadata searches should start working a little bit later on:
https://pagure.io/fedora-infra/ansible/pull-request/2057


- FChE


[Bug debuginfod/31862] New: debuginfod client should cache received x-debuginfod-* headers

2024-06-07 Thread fche at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31862

Bug ID: 31862
   Summary: debuginfod client should cache received x-debuginfod-*
 headers
   Product: elfutils
   Version: unspecified
Status: NEW
  Severity: normal
  Priority: P2
 Component: debuginfod
  Assignee: unassigned at sourceware dot org
  Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Caching alongside the payload would permit the client to repeat IMA checks
later, and would permit federated / caching servers to pass back IMA (and
other) headers to the ultimate client.  This shouldn't require an api/webapi
change.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: [PATCH] Update code of conduct

2024-06-07 Thread Aaron Merey
Pushed as commit e2a3e51ab54c4698fe09

Aaron

On Tue, May 28, 2024 at 3:34 PM Aaron Merey  wrote:
>
> Adopt a new code of conduct based on the Contributor's Covenant.
>
> See the new CONDUCT file for more information.
>
> Signed-off-by: Aaron Merey 
> ---
>  CONDUCT | 134 
>  CONTRIBUTING|   3 +-
>  Makefile.am |   2 +-
>  NEWS|   3 +
>  config/elfutils.spec.in |   2 +-
>  5 files changed, 141 insertions(+), 3 deletions(-)
>  create mode 100644 CONDUCT
>
> diff --git a/CONDUCT b/CONDUCT
> new file mode 100644
> index ..2d0b8589
> --- /dev/null
> +++ b/CONDUCT
> @@ -0,0 +1,134 @@
> +# Contributor Covenant Code of Conduct
> +
> +## Our Pledge
> +
> +We as members, contributors, and leaders pledge to make participation in
> +our community a harassment-free experience for everyone, regardless of
> +age, body size, visible or invisible disability, ethnicity, sex
> +characteristics, gender identity and expression, level of experience,
> +education, socio-economic status, nationality, personal appearance,
> +race, caste, color, religion, or sexual identity and orientation.
> +
> +We pledge to act and interact in ways that contribute to an open, welcoming,
> +diverse, inclusive, and healthy community.
> +
> +## Our Standards
> +
> +Examples of behavior that contributes to a positive environment for our
> +community include:
> +
> +* Demonstrating empathy and kindness toward other people
> +* Being respectful of differing opinions, viewpoints, and experiences
> +* Giving and gracefully accepting constructive feedback
> +* Accepting responsibility and apologizing to those affected by our mistakes,
> +  and learning from the experience
> +* Focusing on what is best not just for us as individuals, but for the
> +  overall community
> +
> +Examples of unacceptable behavior include:
> +
> +* The use of sexualized language or imagery, and sexual attention or
> +  advances of any kind
> +* Trolling, insulting or derogatory comments, and personal or political
> +  attacks
> +* Public or private harassment
> +* Publishing others' private information, such as a physical or email
> +  address, without their explicit permission
> +* Other conduct which could reasonably be considered inappropriate in a
> +  professional setting
> +
> +## Enforcement Responsibilities
> +
> +Community leaders (i.e. regular contributors and/or those with elfutils
> +git commit access) are responsible for clarifying and enforcing our standards
> +of acceptable behavior and will take appropriate and fair corrective action
> +in response to any behavior that they deem inappropriate, threatening,
> +offensive, or harmful.
> +
> +Community leaders have the right and responsibility to remove, edit, or
> +reject comments, commits, code, wiki edits, issues, and other contributions
> +that are not aligned to this Code of Conduct, and will communicate reasons
> +for moderation decisions when appropriate.
> +
> +## Scope
> +
> +This Code of Conduct applies within all community spaces, such as the
> +elfutils IRC channel, website, mailing list and bug reports. It also
> +applies when an individual is officially representing the community
> +in public spaces. Examples of representing our community include acting
> +as an appointed representative at an online or offline event.
> +
> +## Enforcement
> +
> +Instances of abusive, harassing, or otherwise unacceptable behavior may
> +be reported to the elfutils code of conduct committee at
> +elfutils-cond...@sourceware.org.
> +
> +The current members of the elfutils code of conduct committee are:
> +Mark Wielaard
> +Aaron Merey
> +
> +All complaints will be reviewed and investigated promptly and fairly.
> +
> +All community leaders are obligated to respect the privacy and security
> +of the reporter of any incident.
> +
> +## Enforcement Guidelines
> +
> +Community leaders will follow these Community Impact Guidelines in
> +determining the consequences for any action they deem in violation of
> +this Code of Conduct:
> +
> +### 1. Correction
> +
> +Community Impact: Use of inappropriate language or other behavior deemed
> +unprofessional or unwelcome in the community.
> +
> +Consequence: A private, written warning from community leaders, providing
> +clarity around the nature of the violation and an explanation of why the
> +behavior was inappropriate. A public apology may be requested.
> +
> +### 2. Warning
> +
> +Community Impact: A violation through a single incident or series of
> +actions.
> +
> +Consequence: A warning with consequences for continued behavior. No
> +interaction with the people involved, including unsolicited interaction
> +with those enforcing the Code of Conduct, for a specified period of time.
> +This includes avoiding interactions in community spaces as well as external
> +channels like social media. Violating these terms may lead to a temporary
> +or permanent ban.
> +
> +### 3. Temp