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

keepass: Change from mono40 to mono50 #34358

Closed
wants to merge 1 commit into from

Conversation

joncojonathan
Copy link
Member

Motivation for this change

Issue #31859 (#31859) highlighted TLSv1.1 / TLSv1.2
support isn't available with older versions of Mono 4. This change moves to use Mono 5.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

Motivation for change:
Issue NixOS#31859 (NixOS#31859) highlighted TLSv1.1 / TLSv1.2
support
isn't available with older versions of Mono 4.  This change moves to use Mono 5.
@fpletz
Copy link
Member

fpletz commented Jan 28, 2018

Any reason why we shouldn't compile with with mono54 right away? Builds for me.

The other question is why is mono40 the default anyway. No support for newer TLS versions is a security issue.

cc @orivej @copumpkin because they have done mono stuff in the last few weeks.

@copumpkin
Copy link
Member

I don't know enough about mono to know about changing the default, but it seems reasonable to bump the default to a much higher version.

@joncojonathan
Copy link
Member Author

@fpletz @copumpkin The only reason I didn't switch to Mono54 was because I forgot it existed. Was a month or so ago I started looking into this and I forgot what version I was aiming for! I'm happy to look at moving to mono54.

I'll close this PR and start again with the change.

@joncojonathan
Copy link
Member Author

Please see #34398

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants