Development Notes / Design Documentation about Kicksecure Infrastructure
This page talks about Kicksecure online hosting and (non-existing) testing infrastructure.
Hosted by mirror, downloadable using TLS.
- community contribution friendly - flagged revisions - usable way to allow anonymous users to edit and to let admins review changes before these go live
- sufficient protection from spam
- seo - plugins provide good OpenGraph meta tags and meta settings (description, images)
- wiki templates
- expand buttons
- mobile view
- mediawiki markup text file backups (but are not easily importable)
- short and detailed buttons (probably not unique to mediawiki)
- offline documentation
- translations not solved
- data base is binary (mysql) (requires mysql data base)
- in other words: not flat file
- not easy "transparent" backups
- cannot rebuild from clean human readable source files
goals for new website
- flat file
- git based?
- prose.io (example) compatible?
- breadcrumbs navigation?
- CMS free?
- bootstrap based?
- mobile friendly
- illustrative images
- quick page load times
- footer links (legal, imprint)!
TODO: archival using httrack?
- cannot make complete backup - https://meta.discourse.org/t/how-to-backup-and-restore-a-whole-var-discourse-app-folder/152598
- backup restoration failing - https://meta.discourse.org/t/restore-problem-relation-theme-fields-does-not-exist/95500/7
- postgres database bugs - https://meta.discourse.org/t/restore-fails-could-not-create-unique-index/151380/20
- difficult to repair database - https://meta.discourse.org/t/a-basic-discourse-archival-tool/62614
- no archival - https://meta.discourse.org/t/a-basic-discourse-archival-tool/62614
- archival feature request #1 https://web.archive.org/web/20200805132135/https://meta.discourse.org/t/print-long-topic-to-pdf-redux-again/44639/62
- archival feature request #2 https://meta.discourse.org/t/a-basic-discourse-archival-tool/62614/51
- feature request: Option to use flat/text backing files instead of SQL(Postgres) backend
OCSP is only relevant in case if a TLS certificate is ever revoked.
must staple needs to be activated:
- on web server [safe] [done]
- inside TLS certificate [can break connectivity] [will not be implemented]
The OCSP "must staple", however, is a completely different thing, and getting OCSP "must staple" to work with nginx might be tricky: you have to either ensure that OCSP responses are preloaded somehow, or have to use ssl_stapling_file and provide responses yourself. Avoid using OCSP "must staple" flag in certificates unless you are going to deal with this. Closing this as a duplicate of #812, which is about improving compatibility with "must staple" without using ssl_stapling_file.
Avoid using "must staple" in certificates unless you are going to provide OCSP responses yourself using the ssl_stapling_file directive.
- at Mozilla also pointing out that nginx bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1366100
- OCSP won't be implemented in postfix: https://marc.info/?l=postfix-users&m=151119229905817
OCSP must-staple is "dead", long life CRLite.
- CRLite is a browser and CA (certificate authority) feature. Not a server feature.
- OCSP - CA feature
- OCSP stapling - server feature
- OCSP must-staple - certificate feature
- checking OCSP (ask CA) or checking stapled OCSP - browser feature
- OCSP only relevant after a TLS certificate or CA has been compromised,
- many multiple years unfixed nginx bugs,
- high risk of broken connectivity,
- OCSP must-staple being unpopular,
- browsers ignoring OCSP / must-staple with softfail,
the following actions have been taken:
- OCSP stapling has been enabled server-side.
- OCSP must-staple has not been set in the TLS certificate.
- test websites:
- another website working example: https://dane.sys4.de/smtp/go6.si
- what happen to these screenshots?
- Firefox saying: Verified by: Let's Encrypt
- not yet supported by SSL Labs https://github.com/ssllabs/ssllabs-scan/issues/118
- letsencrypt vs DANE TLSA?
- DANE TLSA standalone?
- DANE TLSA update required, useful when?
The problem with regular Let’s Encrypt certificates
As you know, Let’s Encrypt certificates renew every 90 days. This is not a problem in itself, however, the standard procedure is to generate a new private key with each renewal and, thus, an entirely new public key also. This will necessarily change the hashed key value that would appear in our TLSA record meaning that we would have to remember to update our DNS records on each renewal otherwise the wrong key will be specified and no one will trust our site/server/application! We need to tell Let’s Encrypt to re-use our private key so that the public key hash value does NOT change – that way our DNS record remains valid across certificate renewals.
- Moxie-SSL And The Future Of Authenticity
- todo reading:
drop-www vs yes-www
Cookies are passed down to subdomains
This might be a security issue.
- If you login on github.com, you are also automatically login to gist.github.com.
Quote https://www.rfc-editor.org/rfc/rfc6265 (April 2011):
The user agent will reject cookies unless the Domain attribute specifies a scope for the cookie that would include the origin server. For example, the user agent will accept a cookie with a Domain attribute of "example.com" or of "foo.example.com" from foo.example.com, but the user agent will not accept a cookie with a Domain attribute of "bar.example.com" or of "baz.foo.example.com".
Quote https://www.ietf.org/rfc/rfc2109.txt (February 1997):
A is a FQDN string and has the form NB, where N is a non-empty name string, B has the form .B', and B' is a FQDN string. (So, x.y.com domain-matches .y.com but not y.com.)
Maybe fixable by hostonly cookies.
Host-only only protects example.com cookies from being read by bar.example.com.
Unnecessary cookies hurts performance
https://www.section.io/blog/bare-domain-cookies/ paraphrased and summarized: If unrelated cookies for the apex domain name (example.com) are sent for subdomains (such as forums.example.com) then this is bad for caching.
An ALIAS record will break DNSSEC on the bare domain (@), because @ A and @ AAAA responses will be missing the RRSIG records, which will break resolution on all resolvers.
Quote https://docs.gandi.net/en/domain_names/faq/dns_records.html (bold added)
A, AAAA, ALIAS (not yet supported with dnssec-enabled domains), CNAME, MX, NS, TXT, WKS, SRV, LOC, SPF, CAA, SSHFP, PTR, DNAME
Cloudflare - Note: Cloudflare use
CNAME Flattening. This is the same thing as an
Some of the highest traffic, most popular webstes such as google.com are still using the www subdomain.
scurl --silent --head https://google.com | grep -i location
Hide Server IP
Separate server/IP for e-mail required since it cannot be hidden by CDN.
To take advantage of Cloudflare’s performance and security benefits, we recommend you orange-cloud DNS records that handle HTTP traffic, including A, AAAA, and CNAME. However, do not orange-cloud A, AAAA, or CNAME records used to resolve MX records. For instance, if you have an MX record that points to mail.example.com as your mail server, orange-clouding the A record for mail.example.com will break your mail traffic.
However, there are times when some of your DNS records need to remain grey-clouded. For example: A, AAAA, or CNAME records used for mail traffic must not be orange-clouded because email routing won’t pass through Cloudflare's proxy. When you have to host multiple services (for example, a website and email) on the same physical server To mitigate this risk, we recommend that you: Host your email service in a server (in-house or external) that is different from your site’s origin server Analyze the impact of hosting multiple services on the same origin server in cases when having grey-clouded DNS records can’t be avoided Orange-cloud all records that share the same origin IP address as your root domain and can be safely proxied through Cloudflare
Use separate IP addresses for mail traffic and HTTP/HTTPS traffic. Cloudflare recommends using non-contiguous IPs from different IP ranges.
Compatible with SPF, DKIM and DANE?
pricing when sending through third party server:
Qubes Documentation using jekyll and markdown
- hosted inside git
- editable through git
- unstable table of contents anchors(?)
- no wiki templates support?
- no footnote support?
- web based editing is cumbersome
- previews so not match actual result
- links cannot be tested if those actually work as expected from github editor
- can only edit whole page, not chapter wise
- github editor does not let one use the browsers internal search function and github editor's one is cumbersome
- mediawiki, codeselect, select code, short / long / recommended / detailed buttons
- Web Backend, CMS vs non-CMS, vs github-pages, etc.
- Port Tails Test Suite or create a new one from scratch.