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.

Sign up for GitHub

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

Jump to bottom

Enable strong cryptography when running .NET 2.0 and 4.0 binaries on .NET Framework 4.6 #498

Merged
merged 1 commit into from
Apr 9, 2020
Merged

Enable strong cryptography when running .NET 2.0 and 4.0 binaries on .NET Framework 4.6 #498

merged 1 commit into from
Apr 9, 2020

Conversation

nxtn
Copy link
Contributor

@nxtn nxtn commented Apr 9, 2020 •
edited

@nxtn nxtn added this to the 2.Next milestone Apr 9, 2020
@nxtn nxtn requested a review from oleg-nenashev as a code owner April 9, 2020 08:47
oleg-nenashev
oleg-nenashev approved these changes Apr 9, 2020
View reviewed changes
Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SetSwitch and System.AppContext are both introduced in .NET Framework 4.6, so the checks are right here. Thanks!

@oleg-nenashev oleg-nenashev changed the title Enable strong cryptography when running on .NET Framework 4.6 Enable strong cryptography when running .NET 2.0 and 4.0 binaries on .NET Framework 4.6 Apr 9, 2020
@nxtn nxtn merged commit b0c09e1 into winsw:master Apr 9, 2020
@nxtn nxtn deleted the strongcrypto branch April 9, 2020 10:07
@nxtn nxtn modified the milestones: 2.Next, 2.8.0 Apr 19, 2020
@nxtn nxtn mentioned this pull request Apr 19, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@oleg-nenashev oleg-nenashev oleg-nenashev approved these changes

Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
2.8.0
Development

Successfully merging this pull request may close these issues.

Enable strong cryptography in WinSW by default
2 participants
@nxtn @oleg-nenashev