Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrupted object failure due to username/password length? #69

Open
Invictaz opened this issue Jun 3, 2024 · 1 comment
Open

Corrupted object failure due to username/password length? #69

Invictaz opened this issue Jun 3, 2024 · 1 comment

Comments

@Invictaz
Copy link

Invictaz commented Jun 3, 2024

Normally we use ppp / ppp as username and password for scanning a corrupted object.

If I read this correctly the username / password length matters in the scanning for corrupted object phase.

https://www.psx-place.com/threads/11-00-my-method-of-increasing-the-success-rate-of-pppwn-to-50.43828/

Is this correct or do we have to alter the Corrupt_num = 0x1 to 0x5 ?

@kfp000
Copy link

kfp000 commented Jul 5, 2024

That was the solution for me! It always took me around 20 to 30 attempts with the Raspberry Pi until the hack worked. I have now extended the user name and password for pppoe to both "ppp12345" and now it works every time on the first or second attempt. Thanks you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants