Can a SentinelPro be overwritten? (Cloned)

[Psycho]

Is it possible (easy, etc) to clone a SentinelPro dongle? (The purple one)

I have two of these, one of them is a spare (came with a demo program, and they never asked for it back, but it's expired now), and I'd like to 're-write' the spare with the dump of the good one. Essentially creating a 'physical backup' of the dongle.

That kind of goes against the purpose of these things, so I'm assuming it's not a simple process, but I was just curious if it's even possible (i.e., are these 'write once' devices when they are made, or can they be 'erased'?).

[Git]

I believe it is possible, but if the knowledge has ever been reverse engineered, it has certainly never been made public.

You demo dongle may be much easier to change though. If you can reverse engineer the application, you may get lucky and find WP, OWP1 and OWP2. With these, and some studying of a dump of your two dongles, they can probably be made identical. Finding the overwrite passwords really is down to luck though.

Git

[maximus]

Hi Psycho,

iam working on this project at the moment and wnat to know did you have the Sentinel Super Pro Kit?? or is anybody here to share it with us??
Thanks

[yogi_saw]

even though u have wp, still I don't think it is possible to change readonly cells like developer id unless until u use some hardware to modify its bit patterns in dongle memory, but that too is very difficult u have to play with its internal, sentinel & hasp both are coted in epoxy very difficult to get access to EEPROM

[Git]

Correct, it isn't. But that is exactly what I said a few messages back.

Git

[maximus]

Iam not a pro but i have read, you have readonly cells and writeable cells.Maybe it is enough to have the writeable cellcs.:)

[foffa]

WP OPW1 , OWP2 must be avilable to write to dongle , what he will write on a cell must be as the working other cell from the other dongle

[yogi_saw]

@git I didn't see same thing written by u in this post:confused:
check ur PM, for another way around to achieve this:) :) :)

[scorpie_511]

Are we talking SentinelPro or Sentinel SuperPro.

There is no way to write or reprogram SentinelPro, and it contains no memory. The chip Rainbow used is one time program IC (integrated circuit).

Sentinel SuperPro can be reprogram, provided we have access to the programmer, and it is always, so a certain revision can only program certained group of dongles. There is no need of OP1 and OP1 if we intend to write to memory cells of type 0. They are only required to re-write to memory cells of type 1 (locked data), type 2 (counter cells) and type 3 (algo cells).

Have fun with your experiments.

[Git]

scorpie - the author is talking about reprogramming the whole thing, DevID, C6, WP, the lot. Those values are NOT stored in normal cells with accesscodes in the dongle, only in emulator files. There is no direct API call to write to those registers.

Git

[yogi_saw]

@git what is c6 in this case
@scropio good info man thanks i would like to know something more abt it any more info u have

[benito]

c6=cell06, clear? :)

[scorpie_511]

I know that the author would like to store the content of one of the sentinelpro to the other (not a register), and I also know exactly that sentinelpro has no memory and they use IC of not reprogrammable.

On the other hand, in case of superpro, we can reprogram them provided we have the program to program it (SafeNet/Rainbow give it to their distributors with certain dongle id's/database) and the data base containing the information you mentioned (dongle id's, WP, OP1, OP2 and cell 06). Kindly refer to my previous post.

[Git]

They do not give the database. There is only one copy of the database which distributors access over the net. At least, that is how it used to work. Access to it is secured by iKey. And they do not access all of WP, OWP1, OWP2, C6 as some are algorithmically derived from the others. It doesn't work like that any more because they do not sell SSP or ULP to new customers.

Git