| import cv2 | |
| import numpy as np | |
| import win32api, win32con | |
| import math | |
| webcam_x = 640 #Set webcam resolution | |
| webcam_y = 640 | |
| screen_x = 1280 #Set screen resolution | |
| screen_y = 1024 |
| server.socket = "0.0.0.0:443" | |
| server.username = "lighttpd" | |
| server.groupname = "lighttpd" | |
| server.modules = ( | |
| "mod_openssl", | |
| "mod_proxy", | |
| "mod_dirlisting", | |
| "mod_access", | |
| "mod_compress", | |
| "mod_auth" |
In order to be issued a certificate, Let's Encrypt needs to verify you have control over the domain. This process is automated through challenges, such as setting up a local webserver, or adding DNS TXT records. I don't like the DNS-TXT challenge, as it requires giving every host a DNS service account.
I came up with my own solution. The .well-known/acme-challenge can be hosted using S3, allowing Let's Encrypt to perform an HTTP-01 challenge.
This method requires the least amount of privileges on the host (no ports need to be open)
The primary reason I want internal hosts to have valid certs is quite simple - invalid/untrusted certificates break things! A secondary reason is that constant browser warning are annoying and false alarms are detrimental to security.
| #################################### | |
| # Generates ~/.ssh/config entries # | |
| # using hostname+mac (/etc/ethers) # | |
| #################################### | |
| #!/bin/bash | |
| dev=${1:-'eth0'} # use eth0 if no device specified | |
| domain=.${2:-'local'} # use .local if no domain specified | |
| while read line; do | |
| mac=$(echo $line|awk '{print $1}'); | |
| host=$(echo $line|awk '{print $2}'); |
| admins = {} | |
| modules_enabled = { | |
| "roster"; "saslauth"; "tls"; "private"; "vcard"; "uptime"; "time"; "ping"; "pep"; "admin_adhoc";"posix"; "mod_log_auth"; "disco"; | |
| }; | |
| modules_disabled = { | |
| "offline"; "s2s"; | |
| }; |
| Ability | |
| Able | |
| About | |
| Above | |
| Accept | |
| According | |
| Account | |
| Across | |
| Act | |
| Action |