So close to self awareness

But he did and got the penalty.

Despite the clusterfuck, the fastest man won the race

FIA shitshow

Dafok is dis

Madness

^

This season written by M. Night Shyamalan

E coin

That was uploaded as a test by someone and was deleted straight away, the list still showed it but the map was no longer no the servers.

Uploaded by a troll, and has been deleted.

If you see these fake maps, please let me know on the serveme discord or on steam.

tl;dr Trialing SDR-based servers (Valve's "VPN"), available now in EU and NA, give them a go

Over the past 6 months there has been a large increase in the amount, size and complexity of DDoS attacks. Some of the DDoS protection offered by our providers proved to be ineffective, with no fix in sight.
In EU, only the servers hosted by OVH proved resilient, while in NA, only the servers hosted by NFO proved sufficiently protected against most attacks.

For EU we were able to add a second location (Germany, PetraBrigade) with OVH DDoS protection, since not everyone has great routing to France. In NA we would have liked to have NFO Dallas as a reliable DDoS-protected location in addition to NFO Chicago. Unfortunately their anti-DDoS capabilities in Dallas proved insufficient.
Thanks to community member and server hoster Rob (Rob#9019), we were able to add two very powerful Dallas-based servers with anti-DDoS (DAL3+DAL4).

In addition to these new DDoS protected servers we're also trialing a new kind of server. A couple of weeks ago, Valve added SDR support to TF2. SDR is kind of like a VPN for gaming traffic, already used to keep DOTA and CS:GO servers safe from DDoS.
Both the server and players get private IPs, which is good for your privacy and good for keeping the real IP of the server a secret. Apart from privacy and DDoS protection, SDR can also help with routing, especially over longer distances, so it can even improve your ping in some cases.

Starting today we're trialing SDR in EU and NA. In EU, we've added a Dutch machine in a new location, and the servers on that machine are only reachable through SDR.
In NA, we've added a machine located in Dallas, also at a new datacenter, again only reachable through SDR.

What this means for you:
You make a reservation for these servers just like normal, SDR servers are clearly named. After making the reservation you get a preliminary IP and port. These can still change if the server has to receive a full reboot before your reservation starts (e.g. a TF2 update), so if you can't connect, check back once your reservation has fully launched for the final IP and port. This can take about a minute longer than you're used to.

The IP and port for an SDR is in the 169.254.xxx.xxx range. Normally this is a private IP range, but your TF2 takes care of connecting to this "fake" ip properly. In addition to the server having this fake IP, you as a player also get a fake IP in this same range. So as a server hoster, we never get to see your real IP, which is a nice privacy bonus.

Sssst.... don't let sigafoo know

The merc engine goes up to 11.

In the hands of their no1. driver at least.

L 10/27/2021 - 22:48:19: "built like ps1 hagrid<42><[U:1:156752614]><Blue>" disconnected (reason "Client Disconnect")

L 10/26/2021 - 21:39:49: "built like a minecraft creeper<18><[U:1:156752614]><Spectator>" disconnected (reason "Client Disconnect") 

Nothing useful in the server logs unfortunately.

All this code shows is that all the passwords are stored with bcrypt now. Before using bcrypt they used SHA1 hashes with a salt pepper :(. Those are relatively easy to crack because SHA1 hashing is very very fast.

Sadly, they seemed to have used a single salt (so actually a pepper) for all passwords:

// SHA1Salt is the single salt used for all pre-BCrypt passwords
SHA1Salt = "theleakedcodecontainsthepepper"
// PasswordCutoffTime is the last time we reset passwords. Passwords older than this timestamp must be reset
PasswordCutoffTime = 1427025600 // March 22, 2015, never forget

If you logged in since March 2015, you'll have reset your password and it should no longer be stored as salted SHA1.

If a database ever leaks with the salted SHA1s still in them, it would be trivial to crack all those old passwords.