Hello community, here is the log from the commit of package certbot for openSUSE:Factory checked in at 2017-08-29 11:45:44 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/certbot (Old) and /work/SRC/openSUSE:Factory/.certbot.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "certbot" Tue Aug 29 11:45:44 2017 rev:12 rq:519138 version:0.17.0 Changes: -------- --- /work/SRC/openSUSE:Factory/certbot/certbot.changes 2017-08-12 20:28:44.063146506 +0200 +++ /work/SRC/openSUSE:Factory/.certbot.new/certbot.changes 2017-08-29 11:46:56.596112284 +0200 @@ -1,0 +2,7 @@ +Fri Aug 25 06:07:01 UTC 2017 - ecsos@opensuse.org + +- On request from upstream switch server parameter in cli.ini from + staging to production server. +- Change description in README.SUSE. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ README.SUSE ++++++ --- /var/tmp/diff_new_pack.mkZDaS/_old 2017-08-29 11:46:57.288014758 +0200 +++ /var/tmp/diff_new_pack.mkZDaS/_new 2017-08-29 11:46:57.292014194 +0200 @@ -1,13 +1,31 @@ -Things you must change to use the production server -=================================================== +Explanatory notes +================= +When you don't know a lot about certbot, you sould use first the staging server. +With staging server you can make tests without lock out you from letsencrypt servers. +You can sitch to it in /etc/certbot/cli.ini. +After switch to staging server, you can generate a test certificate. + +And after tests and everything is in order you must change back to production server +After switch back to production server, you must also generate your production certificate. + + +Things you must change to use the staging or producation server +=============================================================== First you must change settings (domains, email, challenges) in /etc/certbot/cli.ini. -In /etc/certbot/cli.ini the staging (testing) server is enabled. + +Things you must change to use the staging server +================================================ +You must change the server in /etc/certbot/cli.ini to staging server. You can make tests without lock out you from letsencrypt servers. -After that when all go right, you _must_ change the server in -/etc/certbot/cli.ini to production server. + +Things you must change to use the production server +=================================================== +At beginning in /etc/certbot/cli.ini the production server is enabled. +After switch to staging after test, you must switch back to production server +in /etc/certbot/cli.ini. You _must_ change /etc/cron.d/certbot with your settings, so the certificate is renewed. ++++++ certbot-cli.ini.patch ++++++ --- /var/tmp/diff_new_pack.mkZDaS/_old 2017-08-29 11:46:57.308011939 +0200 +++ /var/tmp/diff_new_pack.mkZDaS/_new 2017-08-29 11:46:57.312011375 +0200 @@ -2,14 +2,16 @@ =================================================================== --- certbot-0.17.0.orig/examples/cli.ini +++ certbot-0.17.0/examples/cli.ini -@@ -10,14 +10,34 @@ +@@ -10,14 +10,36 @@ # Use a 4096 bit RSA key instead of 2048 rsa-key-size = 4096 ++# To test you should use first the staging server. ++# If everything is in order you must change back to production server. +# The staging/testing server -+server = https://acme-staging.api.letsencrypt.org/directory ++# server = https://acme-staging.api.letsencrypt.org/directory +# The production server. -+# server = https://acme-v01.api.letsencrypt.org/directory ++server = https://acme-v01.api.letsencrypt.org/directory + # Uncomment and update to register with the specified e-mail address # email = foo@example.com