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

Change of FTP AES key in .1000 firmware #7

Open
jezzab opened this issue Sep 7, 2017 · 3 comments
Open

Change of FTP AES key in .1000 firmware #7

jezzab opened this issue Sep 7, 2017 · 3 comments

Comments

@jezzab
Copy link
Collaborator

jezzab commented Sep 7, 2017

New FTP AES key:
Hex: 0x59 0x50 0x31 0x4E 0x61 0x67 0x37 0x5A 0x52 0x26 0x44 0x6A 0x00 0x00 0x00 0x00
ASCII: YP1Nag7ZR&Dj

IV remains the same:
Hex: 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0x61 0x62 0x63 0x64 0x65 0x66
ASCII: 0123456789abcdef

@jezzab jezzab changed the title Change of AES key in .1000 firmware Change of FTP AES key in .1000 firmware Sep 7, 2017
@Dreamlinker77
Copy link

Hi,
how did you manage to get the new key?
I tried before but when running the busybox binary of the new firmware I always got a Segmentation fault.
The method used for previous version did not work.

Thank you

@MAVProxyUser
Copy link
Owner

MAVProxyUser commented Oct 16, 2017

@Dreamlinker77 you'd need to share strace output from the segfault for help there, at least share more info on your system. The old technique is how we got the new key as you can see from the output.

You can also get the new FTP key from the environment variables, you can root the drone and type "set" and see the net key.

You can see this in the open source code.
https://github.com/MAVProxyUser/busybox-1.25.1/blob/master/networking/ftpd.c#L583
http://www.dji.com/opensource

@Dreamlinker77
Copy link

Now it's more clear to me
Thank you

matemaciek added a commit to matemaciek/DJI_ftpd_aes_unscramble that referenced this issue Jul 7, 2021
Tested with Spark, key from MAVProxyUser#7 seem to  be working (-:
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

3 participants