1 Attachment(s)
l2 411 encode/decode tool
dunno who wrote this program
BETA ! <-- and I mean it. Tested well, but who knows.
--------------
L2encdec
--------------
Algorithms supported in both directions:
111, 121, 211, 212
411 (using new private/public pair)
Decoding only:
411 (using L2's original key)
USAGE: l2encdec.exe <command> <source file> [destination file]
-e - will encode plain file with already present header (first 28 bytes)
-h - will encode plain file, header must be given on the command line - 111, 121, 211, 212, 411
-d - will decode file and leave header (useful for later -e)
-s - will decode and strip header
-l - will decode "legacy" 411 files, using original public key. Header will be left intact.
Source file is mandatory (duh!).
Destination file, if not given, will be automatically generated (with enc- or dec- prefix). Those prefixes
are not taken into account, when 121 key is being generated.
-------------
patcher
-------------
1) Copy patcher and l2encdec into lineage2's system subdir
2) Make sure backup dir doesn't exist
3) Preferably make sure no other crap is in system subdir (wth exception of original files :) )
4) Start command line prompt, or use something that will keep it (like far, etc.)
5) Start patcher
Patcher will:
1) make backup subdir (or abort if it's impossible or subdir already exists).
2) scan every file in L2's system subdir. If file with 411 header is found,
it will be decrypted/decompressed with -l option, original will be backed up,
then decoded file will be reencoded with new 411 private key.
3) patch l2.exe and core.dll files with new rsa public key.
The whole thing unfortunately won't work on PTS - exe and dll files are compressed there. Desipte that core.dll has
key naked, doing it will make L2 or GG think it's corrupt. If it's because of GG or because of L2, reamins to be
seen atm :P
Of course, original private 411 exponent would be the best :)
