Jump to content

Recommended Posts

Posted

What does the bake ice protection?

Well people say that it's  a loader/launcher but frienzl2 in the launcher don't say anything about bakeice but when i proxifilter the connection ALL the packets are encrypted (init too) i read this

 

Interlude changed the way tokens work completely.

 

There are now two tokens used in connection.

 

There's a static one, default 6B60CB5B82CE90B1CC2B6C556C6C6C6C

The static key is used to encrypt the init packet from server(the very first packet)

 

All subsequent packets are encrypted using a dynamic key the init packet contained(I believe it's the last field)

 

i proxifilter the connection using Proxifier and WPC sauron with this script:

 

begin

gSys.tLA2BFToken:=Hstr('6B 60 CB 5B 82 CE 90 B1 CC 2B 6C 55 6C 6C 6C 6C 00');

end.

 

to see the init packet and nothing encrypted...

any idea or knowledge?

Posted

Saurons WP suports Interlude and RSA. In the last version:

A quote from the user guide:

gSys.tPDecode : int;  - тип де/кодировки пакетов (PDecode),

'-1' стоит автоопределение, но еще не определен.

'0' - нет де/кодировки, выключено,

'2' - LA2, LS: BF;

'2' - LA2, GS: GSDecode/GSDecodej/GSDecodeI (см. gSys.tKeyType)

'2' - RFO: ...

'3'..'14' - резерв.

 

gSys.tKeyType : int; - тип ключа для де/кодировки (зависит от PDecode и типа трафика)

(при включенной системе Auto Detect устанавливается автоматически)

значениния tKeyType:

LA2:

1 - GS: GSDecodeJ (C4/C5 ключ 8 байт, инкрементация половины ключа , L2J сервера)

2 - GS: GSDecode (C4/C5 ключ 8 байт, инкрементация всего ключа , official сервер LA2)

3 - GS: GSDecodeI (Interlude ключ 16 байт, инкрементация второй половины)

1 - LS: BF decode

2 - LS: BF decode, RSA present

 

 

Posted

I know it was you, I was just informing the people in these forums :P

Okey then xD

any new you know, pm me^^

but a question then the token changes for every connection (init packet) or the server puts a static token that is forever?

ah and in this

gSys.tKeyType: int-type key for de / encoding (depends on the type of traffic and PDecode)

with that u can make a script to decode the packages like in C4???

Thanks

Posted

ok but u say that is the lasted 16 bytes and i don't think that in this init packet the last 16 bytes will be the token:

here's the packet:

[1]            S>c            0ms.            20:25:25

-------------------------------------------------------------------------------

TType: LA2    Server: LS1    ParseType: 2 (auto)    EnCode: T2 K2 (auto)

------- 0  1  2  3  4  5  6  7 -  8  9  A  B  C  D  E  F    -------------------

000000 AB 00 00 35 2D D1 41 5A | 78 00 00 8A 61 1B 8A 5D    «..5-ÑAZx..Ša.Š]

000010 E4 A2 2E 87 46 FA 41 F8 | 45 4E 96 A2 BB 35 23 82    ä¢.‡FúAøEN–¢»5#‚

000020 60 C2 1C 89 77 75 5F 6E | CA 89 CA EF 2F BE 46 7F    `Â.‰wu_nʉÊï/¾F

000030 2B 01 84 2C 99 11 94 EF | EB 48 ED B3 48 B3 4C 42    +.„,™.”ïëHí³H³LB

000040 8F D2 48 AC 3B DA 13 36 | 40 18 41 B6 55 97 1D DA    ÒH¬;Ú.6@.A¶U—.Ú

000050 2F 5D E3 7F 39 B1 DA 13 | 80 6C F1 37 1B 22 41 31    /]ã9±Ú.€lñ7."A1

000060 67 06 B4 0B 89 63 C3 A2 | 9A 6B 25 92 59 57 59 9D    g.´.‰câšk%’YWY

000070 49 61 C3 AA C0 F0 59 39 | 0C 1B AA F6 73 83 8B F8    IaêÀðY9..ªösƒ‹ø

000080 5A F6 B5 D9 36 6B 52 BB | 92 78 32 00 00 00 00 00    ZöµÙ6kR»’x2.....

000090 00 00 00 00 00 00 00 00 | 00 00 00 30 30 30 30 30    ...........00000

0000A0 30 30 30 30 30 30 30 30 | 30 30 30                    00000000000

-------------------------------------------------------------------------------

LA2:      "Init"                            size: 171    prot: 30810  $785A

Addr:  Size:    Type:        Description:    Value:

0000    2  word          psize            171        | $00AB                           

0002    1  byte          ID                0          | $00                             

0003    4  integer      LoginSessionID    1104227637 | $41D12D35                       

0007    4  integer      LoginProtocolRev  30810      | $0000785A                       

000B  128  array[const]  RSApubKey        (Ša.Š]ä¢.‡FúAøEN–¢»5#‚`Â.‰wu_nʉÊï/¾F

008B    16  -            null              (................)               

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • Added the protection module to the demo.   DDoS Guard Pro v2.0 is a system protection module for PlayMMO CMS designed to reduce the load on the website during HTTP floods, bot activity, suspicious frequent requests, and attacks on individual pages or API methods. Unlike simple global limiters, DDoS Guard Pro v2.0 supports flexible rules based on routes and HTTP methods. This allows you to block the entire site in a targeted manner, rather than blocking the entire site equally. You can set up protection for specific areas of the site, such as login, registration, APIs, administration, forms, and other sensitive areas. What is the purpose of the module? DDoS Guard Pro v2.0 helps protect your site from basic L7 attacks at the HTTP request level. The module is useful when your site receives: frequent requests from a single IP address; HTTP page floods; login or registration form flooding; automatic requests from bots; URL scanning; frequent API requests; suspicious activity spikes; load on individual CMS methods or pages. The module helps to reduce the load on PHP and CMS by limiting suspicious activity before it starts to create a serious load on the site. Main features Per-route and per-method Rate Limit In the new version, protection is configured not only globally, but also according to specific rules. You can set limits separately for: GET; POST; PUT; PATCH; DELETE; ALL. This allows you to flexibly protect different parts of your website. For example: for the login page, you can set a strict limit; for registration, you can set a separate limit; for the API, you can set a limit for reading and a limit for changing data; for regular website pages, you can set a soft limit or not set a limit at all. This approach reduces the risk of accidentally blocking regular users and makes the protection more accurate. Flexible rule system The module supports setting rules in the following format: METHODS|PATTERN|LIMIT|WINDOW|BURST_LIMIT|BURST_WINDOW|BLOCK_SECONDS|IDENTITY|NAME Example of rules: POST|*login*|10|60|5|10|600|ip|login_post POST|*register*|8|60|4|10|600|ip|register_post GET|*api*|300|60|80|10|120|ip|api_get PUT,PATCH,DELETE|*api*|80|60|20|10|300|ip|api_write This allows you to specify exactly: which HTTP methods to protect; which URLs or URL patterns to consider; how many requests are allowed; over what time period; what burst limit to use;  how many seconds to block the offender;  by which ID to count the limit;  what the rule is called. Burst protection against sharp spikes  In addition to the regular request limit, the module monitors sharp spikes of activity.  This is useful when a bot makes many requests in a few seconds. In this case, the protection can be activated faster, without waiting for the overall limit per minute.  Burst protection is especially useful for: authorization pages; registration; API; search; data submission forms; administrative sections. Support for different types of requests DDoS Guard Pro v2.0 works not only with POST requests. The module can control: GET — regular pages, API requests, search; POST — forms, login, registration, data submission; PUT — updating data via API; PATCH — partial data update; DELETE — data deletion; ALL — all methods at once. This makes the module suitable not only for regular sites, but also for CMS with API, personal accounts, game panels and administrative actions. Limit storage: Redis, APCu and file fallback In the new version, the module supports several options for storing temporary data. Available modes: Redis; APCu; file fallback. The auto mode tries to use the most suitable option: Redis; APCu; file storage as a fallback. Redis or APCu are suitable for more efficient operation, while the file storage is left as a fallback option for simple hosting environments that do not have additional extensions. JSONL logging The module records protection events in JSON Lines format. Logs are saved in the following file: storage/logs/ddos_guard.jsonl This format is more convenient than a regular text log, because each event is stored as a separate JSON record. The logs can record the following information: event time; IP address; HTTP method; URL; name of the triggered rule; reason for blocking; number of requests; action status; user-agent; protection mode. The JSONL format is convenient for analysis by external tools, log agents, and monitoring systems. Prometheus metrics DDoS Guard Pro v2.0 adds an endpoint for receiving metrics in Prometheus format. Endpoint: /?ddos_guard_metrics=TOKEN The token is set in the module settings. Metrics allow you to track: the number of processed requests; the number of rule activations; the number of blocks; activity by limits; protection events; module status. This allows you to connect monitoring and configure alerts so that the administrator can see when suspicious activity starts on the site. LOG ONLY mode The module has a LOG ONLY mode. In this mode, DDoS Guard Pro does not block users, but only records events and potential triggers in the log. This mode is recommended to be used after installation, in order to first see which rules are triggered, and only then to enable the real blocking.  This helps to avoid too strict limits and random blocking of regular users.  Support for Cloudflare and proxy  The module supports working behind Cloudflare or another reverse proxy.  With proper configuration, it is possible to take into account the real IP of the user, and not the IP of the proxy server.  This is important for sites that use:  Cloudflare; nginx reverse proxy; load balancers; CDN; hosting proxy protection. Nginx-recommendations DDoS Guard Pro v2.0 contains an example nginx-config: modules/ddos_guard/nginx-ddos-guard-example.conf This allows you to use the module as an additional application layer of protection, and to move the main coarse limits to the nginx level. Recommended protection scheme: Cloudflare / nginx / firewall → DDoS Guard Pro → PlayMMO CMS This approach is more correct than trying to solve all problems only at the PHP level.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..