Docker's Remote API can be secured via TLS and client certificate verification.
First of all you need a few certificates and keys:
- CA certificate
- Server certificate
- Server key
- Client certificate
- Client key
description "Suspend dmcache for SSD cache" | |
author "Kyle Manna <[email protected]>" | |
# Start monitoring with inotifywait (will block) after the filesystem is | |
# mounted, when the filesystem is unmounted, teardown the dm devices. | |
start on mounted MOUNTPOINT=/media/usb1 | |
script | |
inotifywait -e unmount $MOUNTPOINT |
# to generate your dhparam.pem file, run in the terminal | |
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
auth_mechanisms = plain login digest-md5 cram-md5 ntlm apop | |
!include auth-sql.conf.ext |
#!/bin/bash | |
# Ubuntu Developer Script for pdf2htmlEx | |
# Created by Rajeev Kannav Sharma | |
# http://rajeevkannav.github.io/ | |
# | |
# | |
# Downloads and configures the following: | |
# | |
# CMake, pkg-config | |
# GNU Getopt |
import requests | |
import hashlib | |
import time | |
import uuid | |
import os | |
import copy | |
import json | |
# This is based on my personal implementation but stripped down to only what is | |
# needed to verify it. |
import requests | |
import hashlib | |
import time | |
import uuid | |
import os | |
import copy | |
import json | |
# Fixed up version of my previous code to work with the Cloud endpoints. | |
# Hopefully this works. |
# I had a bit of trouble getting my unifi controller (hosted offsite) to use a proxy/letsencrypt. So here are the fruits of my labor. | |
# The unifi default port is 8443 running on localhost. | |
# License: CC0 (Public Domain) | |
server { | |
# SSL configuration | |
# | |
listen 443 ssl default_server; | |
listen [::]:443 ssl default_server; |
<domain log-root="${com.sun.aas.instanceRoot}/logs" application-root="${com.sun.aas.instanceRoot}/applications" version="89"> | |
<security-configurations> | |
<authentication-service default="true" name="adminAuth" use-password-credential="true"> | |
<security-provider name="spcrealm" type="LoginModule" provider-name="adminSpc"> | |
<login-module-config name="adminSpecialLM" control-flag="sufficient" module-class="com.sun.enterprise.admin.util.AdminLoginModule"> | |
<property name="config" value="server-config"></property> | |
<property name="auth-realm" value="admin-realm"></property> | |
</login-module-config> | |
</security-provider> | |
<security-provider name="filerealm" type="LoginModule" provider-name="adminFile"> |
No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.
Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.
A Russian translation of this article can be found here, contributed by Timur Demin. There's also this article about VPN services, which is honestly better written (and has more cat pictures!) than my article.