1,084
edits
Technician (talk | contribs) |
|||
(47 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
== Hosts == | == Hosts == | ||
The following table documents the DNS configuration, and can be used as part of the <code>/etc/hosts</code> file on each server to obviate the need for DNS lookups when connecting to one another. | The following table documents the basic DNS configuration, and can be used as part of the <code>/etc/hosts</code> file on each server to obviate the need for DNS lookups when connecting to one another. | ||
{| class="wikitable" | {| class="wikitable" | ||
!IP !! FQDN !! Host !! Purpose | !IP !! FQDN !! Host !! Purpose !! Ports | ||
|- | |- | ||
|85.214.101.34 || feministwiki.org || || Wiki | |85.214.101.34 || feministwiki.org || || Wiki || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || www.feministwiki.org || www || Wiki | |85.214.101.34 || www.feministwiki.org || www || Wiki || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || ldap.feministwiki.org || ldap || LDAP | |85.214.101.34 || ldap.feministwiki.org || ldap || LDAP || - | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || blogs.feministwiki.org || blogs || Blogging || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || chat.feministwiki.org || chat || Web-client for XMPP || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || forum.feministwiki.org || forum || BBS Forum || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || mail.feministwiki.org || mail || Web-client for Mail || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || files.feministwiki.org || files || File storage || 80, 443 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || imap.feministwiki.org || imap || IMAP || 993 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || pop3.feministwiki.org || pop3 || POP3 || 995 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || smtp.feministwiki.org || smtp || SMTP || 25, 465, 587 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || xmpp.feministwiki.org || xmpp || XMPP || 5222, 5269, 5280 | ||
|- | |- | ||
|85.214.101.34 || | |85.214.101.34 || irc.feministwiki.org || irc || IRC || 6697 | ||
|- | |||
|85.214.101.34 || account.feministwiki.org || account || Account operations || 80, 443 | |||
|} | |||
As you can see, all services are on the same server for now. However, it should be kept as an open possibility that the hosts are split across different IPs. When done so, the <code>ldap</code> host should listen on 636 for LDAPS connections. | |||
== Firewall == | |||
The simple <code>ufw</code> firewall-frontend is used to trivially limit all network I/O to the ports you can see in the host table above, plus port 22 for ssh and scp. | |||
== Special DNS entries == | |||
For CAA: | |||
{| class="wikitable" | |||
!Type !! Name !! Flag !! Tag !! Value | |||
|- | |||
|CAA || @ || 0 || issue || letsencrypt.org | |||
|- | |||
|CAA || @ || 0 || iodef || admin@feministwiki.org | |||
|} | |||
For email: | |||
{| class="wikitable" | |||
!Type !! Host !! Data !! Purpose | |||
|- | |||
|MX || @ || smtp.feministwiki.org || Mail server | |||
|- | |||
|TXT || @ || v=spf1 mx -all || SPF | |||
|- | |||
|TXT || mail._domainkey || v=DKIM1; k=rsa; p=<pubkey> || DKIM | |||
|- | |||
|TXT || _dmarc || v=DMARC1; p=reject; rua=<nowiki>mailto:admin</nowiki>@feministwiki.org || DMARC | |||
|} | |||
'''Note:''' There must be a direct A or AAAA record (not a CNAME record) for the domain name specified in the MX record. | |||
For XMPP: | |||
{| class="wikitable" | |||
!Type !! Service !! Protocol !! Name !! Destination !! Port | |||
|- | |||
|SRV || _xmpp-client || _tcp || @ || xmpp.feministwiki.org || 5222 | |||
|- | |||
|SRV || _xmpp-server || _tcp || @ || xmpp.feministwiki.org || 5269 | |||
|} | |} | ||
Google Site Verification: | |||
{| class="wikitable" | |||
!Type !! Host !! Data | |||
|- | |||
|TXT || @ || google-site-verification=<key> | |||
|} | |||
== SSH access == | == SSH access == | ||
Line 51: | Line 103: | ||
The FeministWiki uses LetsEncrypt to acquire digital certificates for encrypted communication. | The FeministWiki uses LetsEncrypt to acquire digital certificates for encrypted communication. | ||
To ease use of the letsencrypt command, the file <code>/root/etc/domains</code> contains all the FQDNs used by the FeministWiki, one per line. Given that, the preferred way to populate the <code>/etc/letsencrypt/live/feministwiki.org</code> directory with fresh certs is to run the following | To ease use of the letsencrypt command, the file <code>/root/etc/domains</code> contains all the FQDNs used by the FeministWiki, one per line. Given that, the preferred way to populate the <code>/etc/letsencrypt/live/feministwiki.org</code> directory with fresh certs is to run the following commands while TCP port 80 is free (e.g. stop Apache first): | ||
# Use $() to eliminate the terminating newline, if any. | |||
domains=$(cat /root/etc/domains) | |||
domains=$(printf '%s' "$domains" | tr '\n' ',') | |||
letsencrypt certonly --authenticator standalone --keep --expand -d "$domains" | |||
Additionally, for programs that require a cert file and its private key in a single combined <code>.pem</code> file, run the following commands to generate such a file: | Additionally, for programs that require a cert file and its private key in a single combined <code>.pem</code> file, run the following commands to generate such a file: | ||
Line 60: | Line 117: | ||
cat fullchain.pem privkey.pem > certbundle.pem | cat fullchain.pem privkey.pem > certbundle.pem | ||
The script <code>/root/bin/letsencrypt-refresh</code> '''does all of the above''', | The script <code>/root/bin/letsencrypt-refresh</code> '''does all of the above''' automatically. It stops Apache, runs the commands described above, and starts Apache again. This can be used not only to refresh a cert that's running out, but also to add a new domain to the cert. Just add the domain to <code>/root/etc/domains</code> and run the commands. Note that the letsencrypt command may not work well on a "dumb" terminal such as an Emacs shell buffer. If in doubt, run it from within a proper terminal emulator. | ||
=== Readability of the key files === | |||
To ensure that processes running under unprivileged users can read key files, ensure that the users they run under are members of the <code>ssl-cert</code> group, which should have read access to the files in <code>/etc/letsencrypt/live/feministwiki.org</code>. | |||
== Ubuntu package repositories == | |||
Currently, FeministWiki runs on Ubuntu 16.04 LTS (Xenial), which has rather old Apache and PHP packages. We use the Ubuntu PPAs <code>ondrej/apache2</code> and <code>ondrej/php</code> to get newer versions. | |||
For F-Droid packages, we use the <code>fdroid/fdroidserver</code> Ubuntu PPA. | |||
== Services == | == Services == | ||
Line 79: | Line 138: | ||
Software: OpenLDAP | Software: OpenLDAP | ||
The LDAP service contains the central database of FeministWiki members. | The LDAP service contains the central database of FeministWiki members. For details on the LDAP schema, see [[FeministWiki:LDAP Schema]]. | ||
=== Wiki === | === Wiki === | ||
Line 122: | Line 145: | ||
Software: MediaWiki | Software: MediaWiki | ||
The wiki uses a [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] installation located at <code>/var/www/wiki/w</code> | The wiki uses a [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] installation located at <code>/var/www/wiki/w</code>. It uses the [https://www.mediawiki.org/wiki/LDAP_Stack LDAP Stack] for login management, and the "Short URL" feature enabled with help of Apache's vhost configuration. | ||
The wiki uses the SQL database called "feministwiki" and the SQL user of the same name. | The wiki uses the SQL database called "feministwiki" and the SQL user of the same name. | ||
=== | === Blogs === | ||
Host: blogs.feministwiki.org <br/> | |||
Software: WordPress (multisite) | |||
This is an installation of WordPress in <code>/var/www/blogs</code>, with the "multisite network" feature enabled on a path-basis, so users can have their own blogs on URLs like <code>blogs.feministwiki.org/janedoe</code>. LDAP authentication is enabled via the AD/LDAP plugin from miniOrange. | |||
Users from LDAP who log in for the first time are automatically registered as "Subscriber" accounts, and the admin can change their WordPress role "Author" to allow publishing. | |||
This WordPress installation uses the SQL database called "blogs" and an SQL user of the same name. | |||
=== Chat (web interface) === | === Chat (web interface) === | ||
Line 141: | Line 166: | ||
The web-interface for the FeministChat uses the full-screen "Impress" variant of the [https://conversejs.org/ Converse.js] XMPP client. The hosted HTML and JS files are located at <code>/var/www/chat</code>, although they load Converse.js as an external script from upstream, which is why the self-hosted HTML and JS are very minimal. | The web-interface for the FeministChat uses the full-screen "Impress" variant of the [https://conversejs.org/ Converse.js] XMPP client. The hosted HTML and JS files are located at <code>/var/www/chat</code>, although they load Converse.js as an external script from upstream, which is why the self-hosted HTML and JS are very minimal. | ||
=== Forum === | |||
Host: forum.feministwiki.org <br/> | |||
Software: phpBB | |||
The forum uses a [https://www.phpbb.com/ phpBB] installation located at <code>/var/www/forum</code>. Most configuration of phpBB, including LDAP authentication, is done through its administration panel. The style used by the forum is essentially Basic Orange, though the logo is changed via an inheriting style called FeministWiki. | |||
The forum uses the SQL database called "feministforum" and the SQL user of the same name. | |||
=== Mail (web interface) === | === Mail (web interface) === | ||
Line 148: | Line 182: | ||
The web-interface for the FeministMail uses the [https://roundcube.net/ Roundcube] mail client, installed at <code>/var/www/mail</code>. It uses the standard "larry" style, but with some tweaks to logos and images. | The web-interface for the FeministMail uses the [https://roundcube.net/ Roundcube] mail client, installed at <code>/var/www/mail</code>. It uses the standard "larry" style, but with some tweaks to logos and images. | ||
=== Files === | |||
Host: files.feministwiki.org <br/> | |||
Software: Nextcloud | |||
FeministFiles is a [https://nextcloud.com/ Nextcloud] installation with some branding, and LDAP authentication, installed at <code>/var/www/files</code>. | |||
=== IMAP === | |||
Host: imap.feministwiki.org <br/> | |||
Software: Dovecot | |||
FeministMail uses the [https://www.dovecot.org/ Dovecot] IMAP server, configured for LDAP authentication and using virtual mail boxes under <code>/home/vmail</code>. | |||
=== POP3 === | |||
Host: pop3.feministwiki.org <br/> | |||
Software: Dovecot | |||
While Dovecot is primarily an IMAP server, it also offers POP3 support, which the FeministWiki installation has enabled. | |||
=== SMTP === | |||
Host: smtp.feministwiki.org <br/> | |||
Software: Postfix, OpenDKIM | |||
FeministMail uses the [http://www.postfix.org/ Postfix] SMTP server, using SASL authentication through Dovecot, LDAP-based virtual mail boxes under <code>/home/vmail</code>, and DKIM signing via OpenDKIM. Send a mail to a Gmail account and use the "Show original" feature of Gmail to see if the mail passes SPF, DKIM, and DMARC tests. | |||
There are also various tools on the web to automatically test the DNS settings for correctness, to check if the domain/IP is on blacklists, etc., which you can find via Google. All in all, FeministMail is probably the most complicated service of the FeministWiki, as far as technical background goes. | |||
=== Mailing lists === | |||
Email domain: lists.feministwiki.org <br/> | |||
Software: GNU Mailman, Postfix | |||
Postfix is configured to recognize <code>lists.feministwiki.org</code> as a "local" domain. This means it uses the file specified in the <code>alias_maps</code> configuration directive (typically <code>/etc/aliases</code>) to decide the final recipient of an e-mail sent to this domain. Correspondingly, we populate <code>/etc/aliases</code> with the aliases needed by Mailman to operate each mailing list it controls. | |||
Note that there is no DNS entry for <code>lists.feministwiki.org</code> because e-mail software just checks the MX record for <code>feministwiki.org</code> when the recipient is from the domain <code><em>anything</em>.feministwiki.org</code>. | |||
=== XMPP === | |||
Host: xmpp.feministwiki.org <br/> | |||
Software: ejabberd | |||
FeministChat uses the [https://www.ejabberd.im/ ejabberd] XMPP server, configured to use LDAP authentication and an LDAP-based shared roster group for all members. | |||
=== IRC === | |||
Host: irc.feministwiki.org <br/> | |||
Software: InspIRCd | |||
FeministIRC uses the [http://www.inspircd.org/ InspIRCd] IRC server with the <code>ldapauth</code> module for LDAP authentication. | |||
=== Account operations === | |||
Host: account.feministwiki.org <br/> | |||
Software: custom | |||
This custom web interface hosted at <code>/var/www/account</code> lets you complete several tasks related to FeministWiki membership, such as changing your account settings, resetting your password, or adding a new member. It also contains a form to request membership. The interface is written in HTML, CSS, PHP, and C. |