Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[jansson] Don't use WinCryptoApi for UWP builds #2244

Merged
merged 1 commit into from
Nov 25, 2017

Conversation

janisozaur
Copy link
Contributor

Jansson tries to use Windows' CryptoApi to seed its hash table. This API
is not exposed in UWP, but there is still a fallback to use current time
and PID.

This change makes Jansson use less-secure fallback, but fixes
compilation for UWP target.

See https://jansson.readthedocs.io/en/2.10/apiref.html#c.json_object_seed

Jansson tries to use Windows' CryptoApi to seed its hash table. This API
is not exposed in UWP, but there is still a fallback to use current time
and PID.

This change makes Jansson use less-secure fallback, but fixes
compilation for UWP target.

See
https://jansson.readthedocs.io/en/2.10/apiref.html#c.json_object_seed
@janisozaur janisozaur mentioned this pull request Nov 24, 2017
10 tasks
@ras0219-msft ras0219-msft merged commit 90e520a into microsoft:master Nov 25, 2017
@ras0219-msft
Copy link
Contributor

LGTM, thanks for the PR!

@janisozaur janisozaur deleted the patch-1 branch April 19, 2023 10:00
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.

None yet

2 participants