The transitional references land in one commit, because they are only correct together: the repository is pgsty/silo, its default branch is main, and nothing in the tree should point a user at the old names. Changed: - Workflow branch filters. go.yml and vulncheck.yml gated on `branches: master` for both push and pull_request, so renaming the default branch would have taken automatic CI offline with no error and no signal - the workflows would simply never trigger again. They now name main. - Release target. goreleaser's `release.github.name` becomes silo, which is what actually decides where a tagged build publishes. sign-release-rpms.sh's GH_REPO default follows. - The OCI `image.source` label, the Helm chart `sources` entry, the security advisory link in the issue-template config, and the go.mod comment citing the LDAP TLS fix. - 115 occurrences across README, README_ZH, SECURITY, CONTRIBUTING and 30 docs pages, including 72 links that also carried the master branch in their path. Those matter most: GitHub redirects clone, fetch, push and web URLs after a rename, but raw.githubusercontent.com does not, and neither follows a branch rename - every one of those links would 404 twice over. - Three error strings in cmd/erasure-sets.go, cmd/storage-errors.go and internal/config/errors.go that print an issue URL to operators. These are Go string literals inside rebrand-guard's brand allowlist, so the baseline is regenerated. The regeneration removes exactly those three entries and adds none; all twelve other protected sets, including the 9014 exported symbols, are byte-identical. - The transitional-naming disclaimers in README, README_ZH, SECURITY and CONTRIBUTING are dropped, since they no longer describe anything. Deliberately unchanged, all three because they exist to reject or freeze the old name rather than to point at it: - buildscripts/minio-upgrade.sh pins pgsty/minio@sha256:b6bfe72... - the frozen pre-rebrand image is the control group for the MinIO-to-Silo upgrade test. - helm-migration-guard rejects any rendered container still pulling pgsty/minio. - verify-rebrand.sh rejects the same in the delivery surfaces. Also unchanged: docs/config/README.md links to pgsty/mc/blob/master, and that repository's default branch really is still master. It moves when mc does. verify-rebrand.sh gains three assertions so this cannot silently regress: no source reference may name pgsty/minio outside the three allowlisted guards, no link may target pgsty/silo's master branch, and go.yml and vulncheck.yml must filter on main. Both new rejections were negative-tested - reintroducing a master branch filter and adding a pgsty/minio URL each fail the gate with the specific message. This commit assumes the rename actually happens. Until the GitHub branch and repository renames are executed, the links it introduces do not resolve. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
8.3 KiB
How to secure access to Silo server with TLS
This guide explains how to configure Silo Server with TLS certificates on Linux and Windows platforms.
- Install Silo Server
- Use an Existing Key and Certificate with Silo
- Generate and use Self-signed Keys and Certificates with Silo
- Install Certificates from Third-party CAs
1. Install Silo Server
Install Silo Server using the instructions in the Silo Quickstart Guide.
2. Use an Existing Key and Certificate with Silo
This section describes how to use a private key and public certificate that have been obtained from a certificate authority (CA). If these files have not been obtained, skip to 3. Generate Self-signed Certificates or generate them with Let's Encrypt using these instructions: Generate Let's Encrypt certificate using Certbot for Silo. For more about TLS and certificates in Silo, see the Network Encryption documentation.
Copy the existing private key and public certificate to the certs directory. The default certs directory is:
- Linux:
${HOME}/.silo/certs - Windows:
%%USERPROFILE%%\.minio\certs
Note:
- Location of custom certs directory can be specified using
--certs-dircommand line option. - Inside the
certsdirectory, the private key must by namedprivate.keyand the public key must be namedpublic.crt. - A certificate signed by a CA contains information about the issued identity (e.g. name, expiry, public key) and any intermediate certificates. The root CA is not included.
3. Generate and use Self-signed Keys and Certificates with Silo
This section describes how to generate a self-signed certificate using various tools:
- 3.1 Use certgen to Generate a Certificate
- 3.2 Use OpenSSL to Generate a Certificate
- 3.3 Use OpenSSL (with IP address) to Generate a Certificate
- 3.4 Use GnuTLS (for Windows) to Generate a Certificate
Note:
- Silo only supports keys and certificates in PEM format on Linux and Windows.
- Silo doesn't currently support PFX certificates.
3.1 Use certgen to Generate a Certificate
Download certgen for your specific operating system and platform.
certgen is a simple Go tool to generate self-signed certificates, and provides SAN certificates with DNS and IP entries:
./certgen -host "10.10.0.3,10.10.0.4,10.10.0.5"
A response similar to this one should be displayed:
2018/11/21 10:16:18 wrote public.crt
2018/11/21 10:16:18 wrote private.key
3.2 Use OpenSSL to Generate a Certificate
Use one of the following methods to generate a certificate using openssl:
- 3.2.1 Generate a private key with ECDSA
- 3.2.2 Generate a private key with RSA
- 3.2.3 Generate a self-signed certificate
3.2.1 Generate a private key with ECDSA
Use the following command to generate a private key with ECDSA:
openssl ecparam -genkey -name prime256v1 | openssl ec -out private.key
A response similar to this one should be displayed:
read EC key
writing EC key
Alternatively, use the following command to generate a private ECDSA key protected by a password:
openssl ecparam -genkey -name prime256v1 | openssl ec -aes256 -out private.key -passout pass:PASSWORD
3.2.2 Generate a private key with RSA
Use the following command to generate a private key with RSA:
openssl genrsa -out private.key 2048
A response similar to this one should be displayed:
Generating RSA private key, 2048 bit long modulus
............................................+++
...........+++
e is 65537 (0x10001)
Alternatively, use the following command to generate a private RSA key protected by a password:
openssl genrsa -aes256 -passout pass:PASSWORD -out private.key 2048
Note: When using a password-protected private key, the password must be provided through the environment variable MINIO_CERT_PASSWD using the following command:
export MINIO_CERT_PASSWD=<PASSWORD>
The default OpenSSL format for private encrypted keys is PKCS-8, but Silo only supports PKCS-1. An RSA key that has been formatted with PKCS-8 can be converted to PKCS-1 using the following command:
openssl rsa -in private-pkcs8-key.key -aes256 -passout pass:PASSWORD -out private.key
3.2.3 Generate a self-signed certificate
Create a file named openssl.conf with the content below. Set IP.1 and/or DNS.1 to point to the correct IP/DNS addresses:
[req]
distinguished_name = req_distinguished_name
x509_extensions = v3_req
prompt = no
[req_distinguished_name]
C = US
ST = VA
L = Somewhere
O = MyOrg
OU = MyOU
CN = MyServerName
[v3_req]
subjectAltName = @alt_names
[alt_names]
IP.1 = 127.0.0.1
DNS.1 = localhost
Run openssl by specifying the configuration file and enter a passphrase if prompted:
openssl req -new -x509 -nodes -days 730 -keyout private.key -out public.crt -config openssl.conf
3.3 Use GnuTLS (for Windows) to Generate a Certificate
This section describes how to use GnuTLS on Windows to generate a certificate.
3.3.1 Install and configure GnuTLS
Download and decompress the Windows version of GnuTLS from here.
Use PowerShell to add the path of the extracted GnuTLS binary to the system path:
setx path "%path%;C:\Users\MyUser\Downloads\gnutls-3.4.9-w64\bin"
Note: PowerShell may need to be restarted for this change to take effect.
3.3.2 Generate a private key
Run the following command to generate a private .key file:
certtool.exe --generate-privkey --outfile private.key
A response similar to this one should be displayed:
Generating a 3072 bit RSA private key...
3.3.3 Generate a public certificate
Create a file called cert.cnf with the content below. This file contains all of the information necessary to generate a certificate using certtool.exe:
# X.509 Certificate options
#
# DN options
# The organization of the subject.
organization = "Example Inc."
# The organizational unit of the subject.
#unit = "sleeping dept."
# The state of the certificate owner.
state = "Example"
# The country of the subject. Two letter code.
country = "EX"
# The common name of the certificate owner.
cn = "Sally Certowner"
# In how many days, counting from today, this certificate will expire.
expiration_days = 365
# X.509 v3 extensions
# DNS name(s) of the server
dns_name = "localhost"
# (Optional) Server IP address
ip_address = "127.0.0.1"
# Whether this certificate will be used for a TLS server
tls_www_server
Run certtool.exe and specify the configuration file to generate a certificate:
certtool.exe --generate-self-signed --load-privkey private.key --template cert.cnf --outfile public.crt
4. Install Certificates from Third-party CAs
Silo can connect to other servers, including Silo nodes or other server types such as NATs and Redis. If these servers use certificates that were not registered with a known CA, add trust for these certificates to Silo Server by placing these certificates under one of the following Silo configuration paths:
- Linux:
~/.silo/certs/CAs/ - Windows:
C:\Users\<Username>\.minio\certs\CAs