- Download intermediate certs as
.pemfrom Lets Encrypt - Add records based on:
- type (R is RSA, E is ECDSA)
- just the current keys, backup key, and future keys
- Use a "2 1 1" record:
- 2 is Trust Anchor (TA)
- 1 is the public key (0 is the full cert)
- 1 is SHA-256 (2 is SHA-512)
| [Event "Die Schachspieler Exhibition"] | |
| [Site "Richmond, VA USA"] | |
| [Date "1861.??.??"] | |
| [Round "1"] | |
| [White "Morphy, Paul"] | |
| [Black "Mephistopheles"] | |
| [Result "*"] | |
| [SetUp "1"] | |
| [FEN "3k4/2r5/1p3n2/n5r1/3q4/p2P2b1/P2K4/Q2B3R w - - 0 1"] | |
| [PlyCount "19"] |
Nginx can be used to proxy several mail protocols. This can be useful in a variety of scenarios: load balancing, providing up-to-date TLS for servers that don’t support it, graceful server migration, or enabling user-specific storage policies.
Unfortunately, what’s not clear from the documentation is that nginx (at least at 1.18) can’t proxy over encrypted connections - which makes this unworkable except in the case of servers on the local network.
| """ | |
| In scene 07 of the game Vampire: The Masquerade - Swansong, you need to turn three valves | |
| on three pipes, in order to set all three gauges to 12. | |
| Each valve has a different effect across all three gagues. | |
| If the gagues go over 12 they wrap around to zero. | |
| Online guides suggest a specific sequence of turns, but this isn't a solution as it assumes | |
| a known starting position. |
| { | |
| "Name": "BingbotSearch", | |
| "Priority": 13, | |
| "Statement": { | |
| "AndStatement": { | |
| "Statements": [ | |
| { | |
| "ByteMatchStatement": { | |
| "SearchString": "bingbot", | |
| "FieldToMatch": { |
IMAP4 Keywords are small bits of metadata that can be attached to stored email messages.
They're free-form text, but the convention is that
\indicates a system keyword$indicates a keyword with a common meaning
See the IMAP4 spec and the IANA registry
| { | |
| "@context": "https://schema.org", | |
| "@type": "ClaimReview", | |
| "claimReviewed": "The Thames is considered one of the cleanest rivers in the world.", | |
| "reviewBody": "This sounds like bollocks, mate", | |
| "itemReviewed": { | |
| "@type": "Claim", | |
| "author": { | |
| "@type": "Person", | |
| "name": "Lucy Williamson" |
| require["mime","fileinto"]; | |
| ## IANA registered type is "text/calendar", but some sources use "application/ics" | |
| if header :mime :anychild :subtype "Content-Type" ["calendar","ics"] { | |
| fileinto "calendar"; | |
| } |
I have a site where there is no legitmate use of the HTTP POST method (or anything other than GET/HEAD).
limit_except is usually used for method restriction, but only produces 403 responses, not 405.
There's a Stack Overflow
question that notes this.
There's a 2015 blog post
that suggests something like the following (which I needed to modify to get the Allow: header to appear):
server {
I have a process that outputs a list of .in-addr.arpa values. These consist of names with 3 to 6 labels.
161.187.42.143.in-addr.arpa
18.139.243.162.in-addr.arpa
38.51.19.58.in-addr.arpa
136.67.34.in-addr.arpa
16.134.243.162.in-addr.arpa
18.240.203.159.in-addr.arpa
240.54.in-addr.arpa