I’ve went through this in order to secure access to Camlistore and delegate authorization to nginx. This doesn’t help, as I don’t yet have a securely stored password set up to protect it, but the first steps are there. Moving to something like LDAP-backed authorization for authentication on my machine and authentication of Camlistore is probably the way to go.
Without further ado, here is my partial nginx configuration, which should be useful if you already have a domain set up and you’d just like to direct toward Camlistore. I didn’t want to set up a subdomain, as I would have to get a new SSL certificate.
I’m bound to have made a mistake in configuration, so comments are welcome.
server {
server_name ivan.vucica.net;
access_log /var/log/nginx/ivan.vucica.net_access.log;
error_log /var/log/nginx/ivan.vucica.net_error.log;
root /somewhere/on/my/disk;
listen 80;
# skipped...
location /camli {
return 302 https://ivan.vucica.net:3180$request_uri;
}
}
server {
server_name ivan.vucica.net;
access_log /var/log/nginx/ivan.vucica.net_access.log;
error_log /var/log/nginx/ivan.vucica.net_error.log;
root /somewhere/on/my/disk;
listen 443 ssl;
# skipped...
location /camli {
return 302 $scheme://ivan.vucica.net:3180$request_uri;
}
ssl_certificate /ssl/directory/on/my/disk/startssl-vucica.net.chained.crt;
ssl_certificate_key /ssl/directory/on/my/disk/startssl-vucica.net.key;
# ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
# ssl_ciphers HIGH:!aNULL:!MD5;
# from: https://community.qualys.com/blogs/securitylabs/2013/08/05/configuring-apache-nginx-and-openssl-for-forward-secrecy#comment-3794
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS";
# for ssl cache - see http://nginx.org/en/docs/http/configuring_https_servers.html
keepalive_timeout 70;
}
server {
server_name ivan.vucica.net;
access_log /var/log/nginx/ivan.vucica.net_camli_access.log;
error_log /var/log/nginx/ivan.vucica.net_camli_error.log;
root /somewhere/on/my/disk;
listen 3180 ssl;
location /camli {
rewrite ^/camli/(.*) /$1 redirect;
rewrite ^/camli$ / redirect;
}
location / {
proxy_pass http://127.0.0.1:3179;
proxy_connect_timeout 5;
# not using after all, as it would need access to /etc/shadow.
# see http://web.iti.upv.es/~sto/nginx/ngx_http_auth_pam_module-1.3/README.html
# auth_pam "Secured Camli";
# auth_pam_service_name "nginx";
auth_basic "Secured Camli";
auth_basic_user_file /path/to/ivucica-camli-user_file;
}
ssl_certificate /ssl/directory/on/my/disk/startssl-vucica.net.chained.crt;
ssl_certificate_key /ssl/directory/on/my/disk/startssl-vucica.net.key;
# ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
# ssl_ciphers HIGH:!aNULL:!MD5;
# from: https://community.qualys.com/blogs/securitylabs/2013/08/05/configuring-apache-nginx-and-openssl-for-forward-secrecy#comment-3794
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS";
# for ssl cache - see http://nginx.org/en/docs/http/configuring_https_servers.html
keepalive_timeout 70;
}
Camlistore itself is configured to listen only on 127.0.0.1. It doesn’t handle authentication, as using localhost authentication would require running nginx and camlistored under the same user. Adding a username+password authentication and using internal SSL would limit my long-term options for configuring authentication.
{
"auth": "none",
"listen": "localhost:3179",
"identity": "AC5742DD",
"identitySecretRing": "/path/to/camlistore/identity-secring.gpg",
"blobPath": "/path/to/camlistore/blobs",
"sqlite": "/path/to/camlistore/camli-index.db",
"baseURL": "https://ivan.vucica.net:3180/",
"shareHandler": true
}
To generate the .htpasswd file, refer to nginx documentation. Here follows an example; consider hard whether this is secure enough and appropriate for you.
printf "John:$(openssl passwd -crypt V3Ry)\n" >> .htpasswd # this example uses crypt encryption
Don’t forget that this will store the line in your .bash_history. (One way to avoid this specific issue is to prefix the command line with a space. Think hard whether this is enough for you.)