crypt/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-01-24 19:22:07 +03:00
Code Activity

Fixed several typos

Browse Source
This commit is contained in:
Alex Gaynor
2014-11-18 07:55:39 -08:00
parent ec92f6d935
commit 00aae545ac
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
letsencrypt/client/client.py
View File

@@ -308,7 +308,7 @@ class Client(object):
self.config.restart(quiet=self.curses)
#if self.ocsp_stapling is None:
# q = "Would you like to protect the privacy of of your users " +
# q = "Would you like to protect the privacy of your users " +
# "by enabling OCSP stapling? If so, your users will not have to " +
# "query the Let's Encrypt CA separately about the current " +
# "revocation status of your certificate."
@@ -378,7 +378,7 @@ class Client(object):
path = self.gen_challenge_path(
c["challenges"], c.get("combinations", None))
logger.info("Peforming the following challenges:")
logger.info("Performing the following challenges:")
# Every indicies element is a list of integers referring to which
# challenges in the master list the challenge object satisfies
@@ -545,7 +545,7 @@ class Client(object):
def challenge_factory(self, name, challenges, path):
sni_todo = []
# Since a single invocation of SNI challenge can satsify multiple
# Since a single invocation of SNI challenge can satisfy multiple
# challenges. We must keep track of all the challenges it satisfies
sni_satisfies = []

4
letsencrypt/client/configurator.py
View File

@@ -801,7 +801,7 @@ LogLevel warn \n\
def __general_vhost(self, ssl_vhost):
"""
Function needs to be throughly tested and perhaps improved
Function needs to be thoroughly tested and perhaps improved
Will not do well with malformed configurations
Consider changing this into a dict check
"""
@@ -961,7 +961,7 @@ LogLevel warn \n\
TEMP_CHECKPOINT_DIR are removed, then IN_PROGRESS changes are removed
The order is important. IN_PROGRESS is unable to add files that are
already added by a TEMP change. Thus TEMP must be rolled back first
because that will be the 'latest' occurance of the file.
because that will be the 'latest' occurrence of the file.
"""
self.revert_challenge_config()
if os.path.isdir(IN_PROGRESS_DIR):