I'd imagine it's hashed and not encrypted. The iDevice would also need to be jailbroken first, although you probably knew that.

-CLK- wrote I'd imagine it's hashed and not encrypted. The iDevice would also need to be jailbroken first, although you probably knew that.

I was thinking of when you plug the ipod into the computer it shows up as a usb device. Then you would specify the drive that is is (for example E). Then the program would navigate to the area containing the security pin. And then it would decode it and reveal the pin. I am not sure if you would have to have it jailbroken for this. If it was on the ipod then you would have to have it jailbroken.

The PIN would most definitely not be stored in user-readable memory.

-CLK- wrote The PIN would most definitely not be stored in user-readable memory.

That could be true, but if I define a specific path, even if the user cannot access it themselves, the path could most likely still link to the file

So are you trying to hack ipod users?

Hiimmanly wrote So are you trying to hack ipod users?

I am only trying to figure out the pin. It is more of unlocking rather then hacking.

99rock99 wrote

-CLK- wrote The PIN would most definitely not be stored in user-readable memory.

That could be true, but if I define a specific path, even if the user cannot access it themselves, the path could most likely still link to the file

Whether or not you find where the password is stored is irrelevant. A golden rule in development is that passwords should almost never be stored in plain text or a decrypt-able format. Instead they should be stored as a hash like CLK already said.

-Jordan- wrote

99rock99 wrote

-CLK- wrote The PIN would most definitely not be stored in user-readable memory.

That could be true, but if I define a specific path, even if the user cannot access it themselves, the path could most likely still link to the file

Whether or not you find where the password is stored is irrelevant. A golden rule in development is that passwords should almost never be stored in plain text or a decrypt-able format. Instead they should be stored as a hash like CLK already said.

This. And like I said... You can't define a specific path because the OS will not let you access it while using it as removable storage. Trust me. There's separate regions of memory.

-CLK- wrote

-Jordan- wrote

99rock99 wrote

-CLK- wrote The PIN would most definitely not be stored in user-readable memory.

That could be true, but if I define a specific path, even if the user cannot access it themselves, the path could most likely still link to the file

Whether or not you find where the password is stored is irrelevant. A golden rule in development is that passwords should almost never be stored in plain text or a decrypt-able format. Instead they should be stored as a hash like CLK already said.

This. And like I said... You can't define a specific path because the OS will not let you access it while using it as removable storage. Trust me. There's separate regions of memory.

But the program will lose it's purpose if it is not connected to the computer, because if you don't know the code then you cannot go into the ipod to run the program that figures out the pin. Would there be a way to run a program on the ipod from a computer, that brings up a notice, like the low battery one, except it will show the code over the pin area?