René Meusel

This will need to be revisited once #4318 has converged and landed. I converted it to a draft PR.

That's just how it has always been. You can run `./configure.py` from another location (much like you would typically do with `cmake`), to build out-of-source: ```bash mkdir my_build cd my_build...

With #4245 `./configure.py --with-build-dir=` (which is the equivalent of `cmake -B`) should work as expected now. It should not drop any generated files into the repository root, when running ....

> It does create a build/build folder, but other than that, the install is inside the build folder as expected so for now this works for me, thanks! Yeah, the...

Currently Botan supports TPM 1.2 only, and that support is deprecated. TPM 2.0 is a completely new specification that offers _much_ more flexibility and functionality than what we currently have...

There's some discussion in the ML-KEM PR: https://github.com/randombit/botan/pull/3893#issuecomment-2302404165 Generally, I'm fine with adding the seed expansion to the public API as well as not exposing the reading of expanded keys,...

For the record: I changed the ML-KEM pull request [to use the seeds exclusively](https://github.com/randombit/botan/pull/3893#issuecomment-2349229966).

For the record: I changed the ML-DSA pull request [to use the seed exclusively](https://github.com/randombit/botan/pull/4270#issuecomment-2356039856).

With #3893 and #4270 merged we're now supporting the seed-based encoding for the private keys exclusively. I wouldn't rule out that we introduce support for the expanded format in case...

> Define some naming convention for prehashing. Say "SHA-256/Raw" or whatever. As a side-note: We're currently working on signing support for TPM 2.0 (#3877). For that, such an agreed-upon naming...