Dev/About Infrastructure

From Kicksecure
< Dev
Jump to navigation Jump to search

Development Notes / Design Documentation about Kicksecure Infrastructure

Current Situation[edit]

Introduction[edit]

Kicksecure.org Site Security

This page talks about Kicksecure online hosting and (non-existing) testing infrastructure.

File Hosting[edit]

Hosted by mirror, downloadable using TLS.

Testing infrastructure[edit]

  • CI build environment required.
  • Automated Test Suite [1] required.
  • systemcheck

backend[edit]

MediaWiki[edit]

MediaWiki advantages[edit]

  • 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
  • footnotes
  • expand buttons
  • footer
  • mobile view
  • mediawiki markup text file backups (but are not easily importable)
  • short and detailed buttonsarchive.org (probably not unique to mediawiki)

MediaWiki disadvantages[edit]

goals for new website[edit]

  • flat file
  • git based?
  • prose.io (examplearchive.org) compatible?
  • breadcrumbs navigation?
  • javascript free?
  • CMS free?
  • bootstrap based?
  • mobile friendly
  • illustrative images
  • quick page load times
  • footer links (legal, imprint)!
  • seo

discourse forums[edit]

TODO: archival using httrack?

Security[edit]

See Trust#Trusting_the_Kicksecure_Website.

OCSP[edit]

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]

resources:

nginx bugs:

postfix:

OCSP must-staple is "dead", long life CRLite.

Info:

  • OCSP - CA feature
  • OCSP stapling - server feature
  • OCSP must-staple - certificate feature
  • checking OCSP (ask CA) or checking stapled OCSP - browser feature

Conclusion:

Due to,

  • 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.

DANE TLSA[edit]

quote https://mytechiethoughts.com/linux/implementing-dane-with-certbot-using-lets-encrypt/archive.org

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.

-> https://github.com/letsencrypt/boulder/issues/1882archive.org

-> https://www.internetsociety.org/blog/2016/01/lets-encrypt-certificates-for-mail-servers-and-dane-part-1-of-2/archive.org

-> https://www.internetsociety.org/blog/2016/03/lets-encrypt-certificates-for-mail-servers-and-dane-part-2-of-2/archive.org

drop-www vs yes-www[edit]

cookies[edit]

cookie isolation[edit]

Quote https://www.bjornjohansen.com/www-or-notarchive.org

Cookies are passed down to subdomains

This might be a security issue.

Quote https://www.rfc-editor.org/rfc/rfc6265archive.org (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.txtarchive.org (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.

Quote https://stackoverflow.com/questions/12387338/what-is-a-host-only-cookiearchive.org

Host-only only protects example.com cookies from being read by bar.example.com.

cookie performance[edit]

Quote https://www.bjornjohansen.com/www-or-notarchive.org

Unnecessary cookies hurts performance

caching[edit]

https://www.section.io/blog/bare-domain-cookies/archive.org 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.

scaling[edit]

Quote https://docs.gandi.net/en/domain_names/faq/record_types/alias_record.htmlarchive.org

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.htmlarchive.org (bold added)

A, AAAA, ALIAS (not yet supported with dnssec-enabled domains), CNAME, MX, NS, TXT, WKS, SRV, LOC, SPF, CAA, SSHFP, PTR, DNAME

Quote https://help.heroku.com/NH44MODG/my-root-domain-isn-t-working-what-s-wrongarchive.org

Cloudflare - Note: Cloudflare use CNAME Flattening. This is the same thing as an ALIAS or ANAME record

https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/archive.org

popular survey[edit]

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 

Location: https://www.google.com/

SEO[edit]

https://seranking.com/blog/www-vs-non-www/archive.org

Hide Server IP[edit]

Separate server/IP for e-mail required since it cannot be hidden by CDN.

Quote https://support.cloudflare.com/hc/en-us/articles/115003687931-Warning-about-exposing-your-origin-IP-address-via-DNS-recordsarchive.org 

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

Quote https://support.cloudflare.com/hc/en-us/articles/200168876-Email-undeliverable-when-using-Cloudflarearchive.org 

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?

https://www.secjuice.com/finding-real-ips-of-origin-servers-behind-cloudflare-or-tor/archive.org

https://blog.0day.rocks/securing-a-web-hidden-service-89d935ba1c1darchive.org

pricing when sending through third party server:

Others[edit]

Qubes[edit]

Qubes Documentation using jekyll and markdown

pros:

  • hosted inside git
  • editable through git

cons:

  • without javascript there is no table of contents
  • without javascript, anchors are broken
  • 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

See Also[edit]

Footnotes[edit]

  1. ↑ Port Tails Test Suitearchive.org or create a new one from scratch.

Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

Your support makes
all the difference!

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!

Retrieved from "https://www.kicksecure.com/w/index.php?title=Dev/About_Infrastructure&oldid=77727"