Neil Horman
Neil Horman
I understand what your saying, but what you are suggesting is that making the file location a built in policy of openssl. I also understand what you are saying in...
I do think it has downsides. If we fall back to a specific location (in this case the ShGetSpecialFolderPath location for CSIDL_COOMMON_APPDATA, say), Then we have created a canonical location...
your proposal replaces one problem with another. Currently, yes, I agree a hard coded build time path for OPENSSLDIR and friends creates a constraint in which engines/providers have to be...
Let me try summarize the problem as I see it here **The issue** We currently have an issue in that, since many windows users don't build binaries, but install them...
@t8m no fallback is now the path that #22450 is taking
We're not going to break users configurations in a minor release like that. Warts and all, what they have currently works, and they understand (or should understand) the current risks....
Its possible, yes, but why not just use command substitution here: openssl mac -digest "$digest" -macopt key:$(cat key.txt) "$mac_name"
I'm having a hard time seeing the outcome of this issue. From reading it it sounds like the resolution was the observation that the aarch64 target has no hardware offload...
no response marking as inactive, to be closed at the end of 3.4 dev, barring further input
@jvdsn thank you for your query. Asking questions like the above is in large part how we identify issues that are still of concern to the community. This issue clearly...