-
Notifications
You must be signed in to change notification settings - Fork 26
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
Does this still work? #2
Comments
The subsequent releases of the firmware by DblTek did not exactly "fix" this issue. Merely, they made the math problem harder to reverse engineer. I haven't had the time to reverse engineer these later firmwares, but a good rule of thumb is that if the device gives a challenge starting with the letter "n", then it is vulnerable to this tool. Hope this helped with your 'research'! ;) |
I'm simply trying to explore my own device with the hopes that I'll be able to fix it's flakiness.
My challenges for
If you do RE them, be sure to let us know! My device is a rather flakey and I'm trying to get it working. |
Ah I see. Well, currently I do not believe there are any public tools out there for breaking into those newer firmwares. So your device is safe from skids. However, if an APT such as a nationstate wanted to get into your box, they totally could. A good solution is to put your device behind NAT (like a router) and disable the telnet service by blocking the port with iptables. |
My box is behind nat and is not accessible. What I need is access (for myself)! |
It seems the algo was updated in later firmware. Does this still work? There also seems to be another user,
secid
, that uses the device's serial number as past of the challengeThe text was updated successfully, but these errors were encountered: