troypulk1 Posted May 16, 2025 Report Posted May 16, 2025 (edited) Hello, how do I fix this? Thanks /etc/apt/sources.list.d/enpass.sources Types: deb URIs: https://apt.enpass.io/ Suites: stable Components: main Signed-By: /etc/apt/trusted.gpg.d/enpass.gpg Warning: https://apt.enpass.io/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details Audit: https://apt.enpass.io/dists/stable/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on B6DA722E2E65721AF54B93966F7565879798C2FC is not bound: No binding signature at time 2025-01-06T06:23:46Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Edited May 16, 2025 by troypulk1
Tarun Singh Rawat Posted May 20, 2025 Report Posted May 20, 2025 We are looking into the issue with the technical team and will follow up with an update soon. #SI-4367 1
NikosBzh Posted August 14, 2025 Report Posted August 14, 2025 On 5/20/2025 at 7:27 AM, Tarun Singh Rawat said: We are looking into the issue with the technical team and will follow up with an update soon. #SI-4367 Hi, Any news about it ? Thanks
Amandeep Kumar Posted August 18, 2025 Report Posted August 18, 2025 Our technical team has alredy acknowledged the issue and is actively working on a solution. Fixing this bug may take some time, and the resolution will be included in the upcoming updates of the application. We appreciate your patience and understanding.
Amandeep Kumar Posted August 22, 2025 Report Posted August 22, 2025 That’s right, this isn’t a bug in the traditional sense. What’s happening is expected: our signing key is nearing the end of its validity window under the updated policy requirements (specifically, stricter hashing rules around SHA-1). We’re fully aware that this needs updating. Rest assured, our technical team is already working on rotating the signing key. Once that’s ready, it will be rolled out in an upcoming update. Thanks for your patience and for helping us improve the Linux install experience
JeffB Posted September 2, 2025 Report Posted September 2, 2025 Is there any update on this issue? It is still objecting and an updated signing key would remove the error. Thanks
Tarun Singh Rawat Posted September 4, 2025 Report Posted September 4, 2025 We appreciate you following up, and thank you for your patience. Our technical team is actively working on this, and we’ll keep you updated as soon as we have more to share.
michibaby Posted December 22, 2025 Report Posted December 22, 2025 Is there any update on this issue? The first report in this thread is from May 16th!
Tarun Singh Rawat Posted 10 hours ago Report Posted 10 hours ago The feature request is under review by our technical team and awaiting prioritization. We aim to incorporate it into our roadmap in the near future.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now