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
Minor TLS documentation improvements #7592
Conversation
Added the explicit name for private.key and public.crt
Codecov Report
@@ Coverage Diff @@
## master #7592 +/- ##
==========================================
+ Coverage 47.35% 47.35% +<.01%
==========================================
Files 295 295
Lines 46785 46785
==========================================
+ Hits 22153 22156 +3
+ Misses 22581 22579 -2
+ Partials 2051 2050 -1
Continue to review full report at Codecov.
|
Mint Automation
7592-4638977/mint-dist-xl.sh.log:
7592-4638977/mint-compression-xl.sh.log:
7592-4638977/mint-large-bucket.sh.log:
7592-4638977/mint-fs.sh.log:
7592-4638977/mint-compression-dist-xl.sh.log:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
From my limited understanding of the code, the server key/certificate file names are hardcoded here and cannot be changed. The user can only supply the path to the
certs
directory containing these two files.But the TLS documentation isn't really clear on this:
and:
For clarity I've included in the second phrase to include the names
public.crt
andprivate.key
. (I've lost way to much time trying to understand why minio wasn't picking up my<hostname>.crt
andhostname.key
files :D ).Types of changes
Checklist:
mint
PR # here: )