Search results

Update documentation about fips compliance

important

Status: Open.

#483 In shieldworks/aegis;

· v0lkan opened on Jul 19, 2023

a command line utility to do replacements on any file talking to Aegis Safe

enhancementNew feature or requestNew feature or request

Status: Open.

#482 In shieldworks/aegis;

· v0lkan opened on Jul 18, 2023

 ·  

v0.19.0

Test aegis on a kind cluster

Status: Open.

#480 In shieldworks/aegis;

· v0lkan opened on Jul 14, 2023

add some badges to the readme

Status: Open.

#475 In shieldworks/aegis;

· v0lkan opened on Jul 6, 2023

Sentinel is getting too crowded with flags; maybe it’s time to introduce subcommands:

Status: Open.

#474 In shieldworks/aegis;

· v0lkan opened on Jul 6, 2023

Add sentinel the ability to randomly generate key for the "manual insertion" mode. — Sentinel shall require a public key, and encrypt the response with that public key before delivering it (for added security) — the owner of the private key then can decrypt the result — we can also write a helper binary for that

Status: Open.

#473 In shieldworks/aegis;

· v0lkan opened on Jul 6, 2023

All medium and higher severity exploitable vulnerabilities discovered with dynamic code analysis MUST be fixed in a timely way after they are confirmed.

openssf

Status: Open.

#472 In shieldworks/aegis;

· v0lkan opened on Jul 5, 2023

It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases these assertions should not be enabled in production builds.

openssf

Status: Open.

#471 In shieldworks/aegis;

· v0lkan opened on Jul 5, 2023

It is SUGGESTED that at least one dynamic analysis tool be applied to any proposed major production release of the software before its release.

openssf

Status: Open.

#470 In shieldworks/aegis;

· v0lkan opened on Jul 5, 2023

It is SUGGESTED that static source code analysis occur on every commit or at least daily. \

openssf

Status: Open.

#469 In shieldworks/aegis;

· v0lkan opened on Jul 5, 2023

All medium and higher severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed.

openssf

Status: Open.

#468 In shieldworks/aegis;

· v0lkan opened on Jul 5, 2023

The public repositories MUST NOT leak a valid private credential (e.g., a working password or private key) that is intended to limit public access.

openssf

Status: Open.

#467 In shieldworks/aegis;

· v0lkan opened on Jul 5, 2023