Jump to content
  • 0

l2scripts password encryption


Question

Posted

Hi everyone, im creating a acp for l2scripts server

 

Currently i havig problems to encrypt the password, i try with the common base64_encode(pack("H*",sha1($password))), but is not working

 

(The stored password has 88 char lenght instead 28)

 

Any one working with this source know how is the password encryption?

4 answers to this question

Recommended Posts

  • 0
Posted (edited)

The base64 encoded string of the 64 bytes is 88 character long. try base32 instead.

Edited by BruT
  • 0
Posted
On 3/2/2021 at 5:48 PM, MaXUN said:

Hi everyone, im creating a acp for l2scripts server

 

Currently i havig problems to encrypt the password, i try with the common base64_encode(pack("H*",sha1($password))), but is not working

 

(The stored password has 88 char lenght instead 28)

 

Any one working with this source know how is the password encryption?

 

Do you have access to the source? If yes you can check the encryption style though java.

If not you can write here. I have access in all Scripts sources i can paste you the part where it encrypt/decrypt the password. 

  • 0
Posted
On 3/4/2021 at 9:34 PM, Kara said:

 

Do you have access to the source? If yes you can check the encryption style though java.

If not you can write here. I have access in all Scripts sources i can paste you the part where it encrypt/decrypt the password. 

public String encrypt(String password) throws Exception
    {
        AbstractChecksum checksum = JacksumAPI.getChecksumInstance(name);
        checksum.setEncoding("BASE64");
        checksum.update(password.getBytes());
        return checksum.format("#CHECKSUM");
    }

 

@Kara i mean they are using the jacksumAPI but i cannot use that on NodeJS

  • 0
Posted
15 minutes ago, MaXUN said:

public String encrypt(String password) throws Exception
    {
        AbstractChecksum checksum = JacksumAPI.getChecksumInstance(name);
        checksum.setEncoding("BASE64");
        checksum.update(password.getBytes());
        return checksum.format("#CHECKSUM");
    }

 

@Kara i mean they are using the jacksumAPI but i cannot use that on NodeJS

 

I'm not familiar with JS but if you say so. If it's your problem or your client's project why don't you simply change the encoding to something similar to L2J ? 

Guest
This topic is now closed to further replies.


  • Posts

    • https://web.archive.org/web/20260306183214/https://maxcheaters.com/topic/241828-l2j-l2damage/page/3/ https://l2topzone.com/forum/l2-server-support-problems/9/l2damage-stopped/30514 Also we will try to push longer seasons ever ! (1135-100)/9 = 115 online
    • ONE SIDE – AND EVERYTHING BREAKS ▪ Looks like a simple case: Florida DL, back side, barcode – “clean and minimal”. ▪ In reality, these are exactly the tasks that fail most often. – data provided as plain text – request only for the back side – focus on the barcode (PDF417) ▪ And here’s the key point: ▪ A barcode is not just a “picture on the back”. It’s compressed logic of the entire document. ▪ If it doesn’t match the front, format, and data structure – the system flags it instantly. ▪ Many create a “similar-looking” code. But systems don’t read “similar” – they read by specification. ▪ In cases like this, it’s not about design. It’s about correct data assembly and how it behaves inside the format. ▪ Today only – 15% off for verification cases. ▪ Want it to pass, not just look right? Describe your case – we’ll show where even clean files break. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #editing #photoshop #documents #verification #case
    • Your anonymity is a corpse. Blockchain forgets nothing. Your transactions are direct footprints in the hands of anyone who takes an interest. [✘] Still believe in "mixing"? Forget it. Classic Bitcoin mixers are an illusion of security. For Chainalysis and Elliptic algorithms, any attempt to hide tracks in the ledger is transparent. Your "mixing" is an artifact that gets filtered out in seconds. Every transaction leaves a trail that leads to frozen assets or unwanted questions from exchanges.  We don't mix. We break the link. [-] Input: Your "dirty" coins (Dirty BTC/ETH) with all their history and digital markers stay with us. [+] Output: You receive absolutely clean assets (Clean Crypto) from our reserves, which have never intersected with your past. This isn't a game of hide and seek. This is the surgical removal of your financial history from the system.   ------------------------------------------------------------------- Technical indexing: Bitcoin Mixer, Crypto Mixer, Clean BTC, Clean ETH, Anti-Chainalysis, Best Bitcoin Mixer, Anonymous Crypto Exchange, NoLog Mixing Service.
    • Here you are: https://l2crypt.com/l2-tools/l2editor-source/
  • 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..