| ||
| .: STRAYA 🇦🇺 Here's a bit older mashup. Happy Australia Day! | ||
| 05:43 | Music | Permalink | ||
| ||
| .: ACME-CAA Let's Encrypt recently introduced support for ACME-CAA. I've now extended my existing CAA DNS entries with the ACME-CAA properties: % dig +short -t CAA x-way.org 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/68891730; validationmethods=http-01" 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/605777876; validationmethods=http-01" The effect of this is that Let's Encrypt will only grant a signed TLS certificate if the request comes from one of my two accounts (authenticated with the corresponding private key). Addendum: % cat /etc/letsencrypt/accounts/acme-v02.api.letsencrypt.org/directory/*/regr.json
{"body": {}, "uri": "https://acme-v02.api.letsencrypt.org/acme/acct/605777876"}
| ||
| 23:06 | Networking | Permalink | ||
| ||
| .: JSON Feed Added a JSON Feed to this blog (in additon to the existing RSS and Atom feeds): https://blog.x-way.org/feed.json To build the proper JSON file, I used this Jekyll template and the JSON Feed validator. | ||
| 21:51 | Webdesign | Permalink | ||
| ||
| .: Get last 24h of logs with AWK For a temporary log analysis task, I wanted to get the last 24h of logs from a Postfix logfile.
awk -F '[ :]+' 'BEGIN{m=split("Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec",d,"|"); for(o=1;o<=m;o++){months[d[o]]=sprintf("%02d",o)}} mktime(strftime("%Y")" "months[$1]" "sprintf("%02d",$2+1)" "$3" "$4" "$5) > systime()'
This is then used in a cronjob to get a pflogsumm summary of the last 24h:
cat /var/log/mail.log | awk -F '[ :]+' 'BEGIN{m=split("Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec",d,"|"); for(o=1;o<=m;o++){months[d[o]]=sprintf("%02d",o)}} mktime(strftime("%Y")" "months[$1]" "sprintf("%02d",$2+1)" "$3" "$4" "$5) > systime()' | pflogsumm
| ||
| 14:40 | Linux | Permalink | ||
| ||
| .: Happy New Year 2023 As usual, Sydney is a bit ahead of us. Great memories, long time ago :-) | ||
| 13:59 | Misc | Permalink | ||
| ||
| .: Alpha Bravo Charlie While closing an old account I had to communicate using the infamous NATO/ICAO phonetic alphabet (US banks like to exchange the 20+ character long IBANs via poor-quality call-center phonelines). As it has been a while since I last used it, I created a handy table to quickly lookup the code words: nato.sigint.ch Special feature: when queried by curl (eg. without a text/html Accept header) it returns the table as plaintext :-) # curl nato.sigint.ch A Alpha S Sierra B Bravo T Tango C Charlie U Uniform D Delta V Victor E Echo W Whiskey F Foxtrot X X-ray G Golf Y Yankee H Hotel Z Zulu I India 0 Zero J Juliett 1 One K Kilo 2 Two L Lima 3 Three M Mike 4 Four N November 5 Five O Oscar 6 Six P Papa 7 Seven Q Quebec 8 Eight R Romeo 9 Niner | ||
| 22:11 | Misc | Permalink | ||
| ||
| .: How to Exit Vim
(via) | ||
| 22:19 | Linux | Permalink | ||
| ||
| .: Add node to MongoDB cluster To add a new node to an existing MongoDB cluster, login to the mongo shell on the primary node and run the following command: rs.add({host:"mongodb3.example.net:27017"})
Similar to remove a node from the cluster, use: rs.remove("mongodb3.example.net:27017")
| ||
| 22:14 | Linux | Permalink | ||
| ||
| .: Custom nginx error pages For quite some time I've been using custom nginx error pages on this site.
error_page 429 @custom_error_429;
location @custom_error_429 {
internal;
more_set_headers 'Content-Type: text/html';
echo '<html>...</html>';
}
Now while implementing custom error pages for a different project, I tried to see if there is an easier way to do this. Instead of generating and defining a specific error page for each error, a single error page is used for all errors.
error_page 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414
415 416 417 418 421 422 423 424 425 426 428 429 431 451 500
501 502 503 504 505 506 507 508 510 511 /error.html;
location = /error.html {
ssi on;
internal;
root /var/www/default;
}
nginx provides the status code as variable to our error page, but we also need the error message to make it more userfriendly.
map $status $status_text {
400 'Bad Request';
401 'Unauthorized';
402 'Payment Required';
403 'Forbidden';
404 'Not Found';
405 'Method Not Allowed';
406 'Not Acceptable';
407 'Proxy Authentication Required';
408 'Request Timeout';
409 'Conflict';
410 'Gone';
411 'Length Required';
412 'Precondition Failed';
413 'Payload Too Large';
414 'URI Too Long';
415 'Unsupported Media Type';
416 'Range Not Satisfiable';
417 'Expectation Failed';
418 'I\'m a teapot';
421 'Misdirected Request';
422 'Unprocessable Entity';
423 'Locked';
424 'Failed Dependency';
425 'Too Early';
426 'Upgrade Required';
428 'Precondition Required';
429 'Too Many Requests';
431 'Request Header Fields Too Large';
451 'Unavailable For Legal Reasons';
500 'Internal Server Error';
501 'Not Implemented';
502 'Bad Gateway';
503 'Service Unavailable';
504 'Gateway Timeout';
505 'HTTP Version Not Supported';
506 'Variant Also Negotiates';
507 'Insufficient Storage';
508 'Loop Detected';
510 'Not Extended';
511 'Network Authentication Required';
default 'Something went wrong';
}
Now we have the status and the status_text variables available in our error.html page. <html><body> <h1><!--# echo var="status" default="" --> <!--# echo var="status_text" default="Something went wrong" --></h1> </body></html> | ||
| 09:48 | Webdesign | Permalink | ||
| ||
| .: nitter nitter provides a free and open source alternative front-end to Twitter. It talks with the API and does not show any JavaScript or ads (thus no 'forced-login' overlay after reading 5 tweets or similar nastiness). It does a direct mapping of the profile URLs, thus | ||
| 21:08 | Misc | Permalink | ||
