On 08/24/2016 08:21 PM, Bradford Wetmore wrote:
Sean Mullan wrote:
> What about setting the default value to "limited"? And then this
> would only be changed to "unlimited" if the build --enable-unlimited-
> crypto option is specified?
I could, but I'm concerned that a build with --enabled-unlimited-crypto
would expect that the compiled-in version default would also be
unlimited and would be surprised with limited.
Upon Max's suggestion above, I've changed the name of the marker to
"crypto.policy=crypto.policydir-tbd." Does that work for you?
Not really.
Why not just leave the property unset (or commented out)? That seems
more intuitive to me. What if the placeholder value accidentally never
gets replaced?
Anyway, if time is of the essence, go with what you have. This is not a
significant issue.
--Sean
