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

Update the release documentation #85369

Closed
wants to merge 1 commit into from
Closed

Conversation

immae
Copy link
Contributor

@immae immae commented Apr 16, 2020

Motivation for this change

See this comment on the issue: #84633 (comment)

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • 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 nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@immae immae mentioned this pull request Apr 16, 2020
10 tasks
@immae
Copy link
Contributor Author

immae commented Apr 16, 2020

Certificates will be regenerated anew on the next renewal date. The credentials for simp-le are
preserved and thus it is possible to roll back to previous versions without breaking certificate
generation.
Certificates will be regenerated on activation, no account or certificate will be migrated from simp-le.
Copy link
Member

Choose a reason for hiding this comment

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

simp_le state and lego state are stored in different directories no? or at different places? So rollback should work? if that isn't the case anymore than that's a new bug.

Copy link
Member

Choose a reason for hiding this comment

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

We dont say it's backwards compatible. We just say that rollback is an option. Those are different things

Copy link
Contributor Author

@immae immae Apr 16, 2020

Choose a reason for hiding this comment

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

Ah yes, if that’s what you mean for "rollback". However:

  • a new account will be recreated by lego anwyay, he won’t be able to use the one created by simp_le
  • lego will generate new certificates when switching from simp-le to lego the first time, because it doesn’t use the content of /var/lib/acme/your_cert to make its decision. Switching back I don’t know (that will depend on how simp-le computes if a certificate is too old)

Copy link
Member

Choose a reason for hiding this comment

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

We mean rollback in the sense of nixos-rebuild switch --rollback. i.e. the switch to lego doesn't destroy any simp_le state so if something goes bad with upgrade, you can go back to 19.09 and figure out what went wrong

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, I’ll put back the last line then

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed

@arianvp
Copy link
Member

arianvp commented Apr 16, 2020

@GrahamcOfBorg test acme

Copy link
Contributor

@m1cr0man m1cr0man left a comment

Choose a reason for hiding this comment

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

LGTM :) I'm a fan of well worded options, in hope that if the agent changes we can reuse/maintain them.

@flokli
Copy link
Contributor

flokli commented Apr 18, 2020

Thanks! Maybe future work, but can we test this feature in a VM test?

@immae
Copy link
Contributor Author

immae commented Apr 18, 2020

Thanks! Maybe future work, but can we test this feature in a VM test?

I agree. I already tried to understand how tests worked, but I’m not fully at ease with the language yet, it’s still new to me. If you think it’s necessary for this PR it may take me a bit longer to manage to write it (or someone else to write it)

@flokli
Copy link
Contributor

flokli commented Apr 18, 2020

@immae what do you think about forward-porting the release notes from #85370 into master, and picking this up once the test refactorings took place?

cc @emilazy

It currently says that everything will be backward compatible between lego and simp-le certificates, but it’s not.
@immae immae changed the title Add an option to re-use private keys for lego certificates Update the release documentation Apr 19, 2020
@immae
Copy link
Contributor Author

immae commented Apr 19, 2020

@flokli : done

@flokli
Copy link
Contributor

flokli commented Apr 21, 2020

forward-ported from #85370 into master as 3dbd3f2, closing here.

@flokli flokli closed this Apr 21, 2020
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