Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
letsencrypt.sh
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
letsencrypt.sh
Commits
00a0937c
Commit
00a0937c
authored
Dec 05, 2015
by
Simon Ruderich
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
make license agreement configurable as LICENSE
parent
f11bb1db
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
1 deletion
+2
-1
letsencrypt.sh
letsencrypt.sh
+2
-1
No files found.
letsencrypt.sh
View file @
00a0937c
...
...
@@ -6,6 +6,7 @@ set -o pipefail
# default config values
CA
=
"https://acme-v01.api.letsencrypt.org"
LICENSE
=
"https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf"
.
./config.sh
...
...
@@ -168,7 +169,7 @@ thumbprint="$(printf '%s' "$(printf '%s' '{"e":"'"${pubExponent64}"'","kty":"RSA
# If we generated a new private key in the step above we have to register it with the acme-server
if
[
"
${
register
}
"
=
"1"
]
;
then
echo
"+ Registering account key with letsencrypt..."
signed_request
"
${
CA
}
/acme/new-reg"
'{"resource": "new-reg", "agreement": "
https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf
"}'
>
/dev/null
signed_request
"
${
CA
}
/acme/new-reg"
'{"resource": "new-reg", "agreement": "
'
"
$LICENSE
"
'
"}'
>
/dev/null
fi
# Generate certificates for all domains found in domain.txt (TODO: check if certificate already exists and is about to expire)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment