List of open source tools for AWS security: defensive, offensive, auditing, DFIR, etc.
This is, for what I’v read about, the two main things that we need to have updated…
Check them trought uname -r and dmesg | grep microcode
[[email protected]d-56969 www]# systemctl status microcode -l ● microcode.service - Load CPU microcode update Loaded: loaded (/usr/lib/systemd/system/microcode.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2018-01-05 17:43:08 CET; 1 weeks 6 days ago Process: 692 ExecStart=/usr/bin/bash -c grep -l GenuineIntel /proc/cpuinfo | xargs grep -l -E "model[[:space:]]*: 79$" > /dev/null || echo 1 > /sys/devices/system/cpu/microcode/reload (code=exited, status=0/SUCCESS) Main PID: 692 (code=exited, status=0/SUCCESS) Jan 05 17:43:08 sd-56969 systemd: Starting Load CPU microcode update... Jan 05 17:43:08 sd-56969 systemd: Started Load CPU microcode update.
Most of my servers and my client’s servers are hosted @ online.net.
Online.net has posted a nice blog post about their infrastructure….
For a Discourse instance to function properly Email must be set up. Use the
SMTP_URLenv var to set your SMTP address, see sample templates for an example. The Docker image does not contain postfix, exim or another MTA, it was omitted because it is very tricky to set up correctly.
Yah! Discourse doesn’t came with any MTA (mail transfer agent).
I had to install Postfix so that Discourse could send out emails.
My emails weren’t getting delivered…
I was getting the following error on discourse logs(/var/discourse/shared/standalone/log/rails/production.log)….
Job exception: Net::ReadTimeout
After a few tweaks… I got it working…
This is my /var/discourse/containers/app.yml excerpt….
## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example '[email protected],[email protected]' DISCOURSE_DEVELOPER_EMAILS: '[email protected]' ## TODO: The SMTP mail server used to validate new accounts and send notifications DISCOURSE_SMTP_ADDRESS: mail.domain.com DISCOURSE_SMTP_PORT: 25 DISCOURSE_SMTP_USER_NAME: [email protected] DISCOURSE_SMTP_PASSWORD: XXXXXXX DISCOURSE_SMTP_ENABLE_START_TLS: false
Rebuild the APP
cd /var/discourse/ ./launcher rebuild app
While I was unzipping a 72Gb file I got the following errors…
bad zipfile offset (local header sig):
I had to install default-jdk and then use jar.
jar -xf filename.zip
Manufacturer Dell Dell PowerEdge R210
Processor Xeon E3 1x Intel® Xeon® E3 1220 4 C / 4T @3.1 Ghz cache L3 8MB, x64, VT
Memory 32 GB DDR3 ECC
Storage 2 × 4 TB SATA
RAID RAID 0/1 Software
Internet bandwidth guaranteed Premium 500 Mbit/s
So what’s changed in the last 2 years? Besides replacing some servers and network gear, not much. Here’s a top-level list of hardware that runs the sites today (noting what’s different since 2013):
4 Microsoft SQL Servers (new hardware for 2 of them)
11 IIS Web Servers (new hardware)
2 Redis Servers (new hardware)
3 Tag Engine servers (new hardware for 2 of the 3)
3 Elasticsearch servers (same)
4 HAProxy Load Balancers (added 2 to support CloudFlare)
2 Fortinet 800C Firewalls (replaced Cisco 5525-X ASAs)
2 Cisco ASR-1001 Routers (replaced Cisco 3945 Routers)
2 Cisco ASR-1001-x Routers (new!)