Skip to content

Conversation

@Spindel
Copy link
Member

@Spindel Spindel commented Apr 18, 2024

Just the bare minimum maintainance to make it work with the current gen python libraries.

@Spindel Spindel self-assigned this Apr 18, 2024
Spindel added 5 commits April 18, 2024 17:41
The _lib is not accessible in more modern PyOpenSSL and thus won't need
to be batched, better to not fail then.
This uses the most basic update to the model code to work in SqlAlchemy
2.0. The declarative attribuetes may need an overhaul anyhow.
This makes it explicit that we use UTC sans tzinfo, and thus avoid an
warning from python 3.11+ datetime library.

As the DB schema has no tzinfo, this makes it consistent.
because requests should have version=0
Spindel added 16 commits April 18, 2024 17:42
As of now, due to transient dependencies we cannot avoid deprecation
warnings, and thus we should not make those be errors
This re-generates the test fixtures ( with an very ugly script) in order
to set them up as-was but with valid certs that have the versions and
such loadable.
This adds a two way generate & compare operation for the parts that
generate our CA keys for the fixtures, in order to verify that we get
bit-identical output where we want them.
Turns out that global variables can make things work that should not work
This sets it up to work without OpenSSL and moves the code that was duplicated from test fixture generation back home
This gets rid of the OpenSSL code and uses the recommended cryptography module instead.  Some quirks of behaviour are still there, but I think ti mostly works out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants