Actions

Dev/About Infrastructure

From Whonix

< Dev(Redirected from Dev/Web Backend)


Current Situation[edit]

Introduction[edit]

Whonix ™.org Site Security

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

File Hosting[edit]

Hosted by mirror, downloadable using TLS.

Bug / Feature Request Tracker[edit]

https://phabricator.whonix.org [archive].

(Works much better than github for a project at this scale.)

Testing infrastructure[edit]

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

mailman3[edit]

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 buttons [archive] (probably not unique to mediawiki)

mediawiki disadvantages[edit]

goals for new website[edit]

  • flat file
  • git based?
  • prose.io (example [archive]) 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_Whonix_.E2.84.A2_Website.

DANE TLSA[edit]

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

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/1882 [archive]

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

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

drop-www vs yes-www[edit]

Quote https://docs.gandi.net/en/domain_names/faq/record_types/alias_record.html [archive]

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 [archive] (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-wrong [archive]

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]

SEO:

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

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-records [archive] 

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-Cloudflare [archive] 

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]

https://blog.0day.rocks/securing-a-web-hidden-service-89d935ba1c1d [archive]

pricing when sending through third party server:

See Also[edit]

Footnotes[edit]

  1. ↑ Port Tails Test Suite [archive] to Whonix ™ or create a new one from scratch.

text=Jobs in USA
Jobs in USA

Search engines: YaCy | Qwant | ecosia | MetaGer | peekier | Whonix ™ Wiki

Follow: Twitter.png Facebook.png Rss.png Matrix logo.svg.png 1024px-Telegram 2019 Logo.svg.png Discourse logo.png Reddit.jpg 200px-Mastodon Logotype (Simple).svg.png

Donate: Donate Bank Wire Paypal Bitcoin accepted here Monero accepted here Contriute

Whonix donate bitcoin.png Monero donate Whonix.png United Federation of Planets 1000px.png

Share: Twitter | Facebook

We are looking for help in managing our social media accounts. Are you interested?

https link onion link

This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation. Policy of Whonix Website and Whonix Chat and Policy On Nonfreedom Software applies.

Copyright (C) 2012 - 2020 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee [archive] of the Open Invention Network [archive]. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)

Whonix ™ is a derivative of and not affiliated with Debian [archive]. Debian is a registered trademark [archive] owned by Software in the Public Interest, Inc [archive].

Whonix ™ is produced independently from the Tor® [archive] anonymity software and carries no guarantee from The Tor Project [archive] about quality, suitability or anything else.

By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent. Whonix ™ is provided by ENCRYPTED SUPPORT LP. See Imprint, Contact.

Retrieved from "https://www.whonix.org/w/index.php?title=Dev/About_Infrastructure&oldid=60627#backend"