Hardware Upgrade Update

[Fatbear]

Still no updates?

You are literally posting in a thread that is an update.

Tell me friend, how much glue did you sniff today?

[Fatbear]

How about an update. too long between updates in my opinion. I would hate to have to go back to Warmane......Fix this please!

Please go back to Warmane and stop whinging here. Thanks!

[Posercorpse]

Wahhhhhhhhhh wahhhhhhhhhhhhhhhhhhhhhhhhhhh

[Ghiter]

how to play offline ?

[Cortez]

RIP OcotoWow, it was fun while it lasted

[Kodotochka]

As an additional layer of DDoS protection, OctoWoW could consider authenticating game connections through the launcher and dynamically adding authenticated players' IP addresses to an allowlist.

The idea would work as follows. On the first launcher startup, the player authenticates with their OctoWoW account and verifies the device, for example by entering a code sent by email. After successful authentication, the launcher contacts an authorization gateway and the player's current public IP address is temporarily added to the allowlist for the game servers.

Email verification would not necessarily be required every time the player's IP address changes. During the initial verification, the launcher could receive a unique cryptographic device token or key. If the network or public IP changes later, the launcher could automatically authenticate again using a challenge-response mechanism and update the allowed IP address. Email verification would only be required when connecting from a new device or after resetting a trusted device.

A possible architecture could look like this:

Internet → DDoS protection / scrubbing → authorization gateway → game servers

Launcher → account authentication → device token → temporary IP allowlist

This would obviously not replace upstream DDoS protection, and it would not stop an attack that completely saturates the server's network connection before traffic reaches the firewall. However, after volumetric attacks are filtered by the hosting or DDoS protection provider, this mechanism could significantly reduce unwanted TCP connections, connection floods, and direct access attempts against the game services.

Additional controls could also be implemented at the gateway, such as connection rate limiting, limits per account or IP address, automatic blocking of abnormal behavior, and other filtering mechanisms.

The main advantage is that the game servers would effectively become unreachable to sources that have not first authenticated through OctoWoW infrastructure. For legitimate players, the process could remain almost completely transparent: launch the launcher, authenticate automatically, and then start WoW as usual.

This could potentially work well as an additional protection layer on top of the new infrastructure and upstream DDoS filtering currently being deployed.

[Bit]

-snip of ai text

The attacks are on much lower layer and only the provider itself can intervene on network level.

Do you really think that no one though of asking chatgpt 'solve me ddos', lol.

[Foregone]

As an additional layer of DDoS protection, OctoWoW could consider authenticating game connections through the launcher and dynamically adding authenticated players' IP addresses to an allowlist.

The idea would work as follows. On the first launcher startup, the player authenticates with their OctoWoW account and verifies the device, for example by entering a code sent by email. After successful authentication, the launcher contacts an authorization gateway and the player's current public IP address is temporarily added to the allowlist for the game servers.

Email verification would not necessarily be required every time the player's IP address changes. During the initial verification, the launcher could receive a unique cryptographic device token or key. If the network or public IP changes later, the launcher could automatically authenticate again using a challenge-response mechanism and update the allowed IP address. Email verification would only be required when connecting from a new device or after resetting a trusted device.

A possible architecture could look like this:

Internet → DDoS protection / scrubbing → authorization gateway → game servers

Launcher → account authentication → device token → temporary IP allowlist

This would obviously not replace upstream DDoS protection, and it would not stop an attack that completely saturates the server's network connection before traffic reaches the firewall. However, after volumetric attacks are filtered by the hosting or DDoS protection provider, this mechanism could significantly reduce unwanted TCP connections, connection floods, and direct access attempts against the game services.

Additional controls could also be implemented at the gateway, such as connection rate limiting, limits per account or IP address, automatic blocking of abnormal behavior, and other filtering mechanisms.

The main advantage is that the game servers would effectively become unreachable to sources that have not first authenticated through OctoWoW infrastructure. For legitimate players, the process could remain almost completely transparent: launch the launcher, authenticate automatically, and then start WoW as usual.

This could potentially work well as an additional protection layer on top of the new infrastructure and upstream DDoS filtering currently being deployed.

https://meatproxy.me/