0xFFFFFFFF*

[devnul]

I have a strategy I am going to try to work around this, however it would be very helpful if anyone had any idea why this occurs.

What's confusing is that it occurs intermittently.

Rezoning is a hassle.

Anyone can shed any light on this issue?

dn

[fryfrog]

did you click "new thread" instead of "post reply"? is that the issue you are talking about? ;p

[devnul]

The issue is the key that is sniffed is occasionally 0xFFFFFFFF[0-f]+.

I assumed it would be clear to anyone that had a useful answer.

And yes I did search, and have seen it noted that this is an issue, and do have a simple idea of what to do to fix it, but have seen no one else delve into the problem other than to mention it exists.

dn

[mvern]

No, the key occasionaly is 0xffffffff........ - this is not somehow a problem with the methods used to read the key - its just that the keys actualy do start with that roughly half the time...

[devnul]

Thank you very much mvern.

I assumed this was an glitch and thus was afraid to load that key.

I'll roll back my 'fix' then which was to try shifting a few either way if I got ff's.

I also want to thank you for posting your excellent code. I borrowed heavily and am in your debt.

It does seem very odd the key would be half ff's sometimes tho, is that significant?

dn

[jonnyboy]

I did also notice the key is sometimes sniffed as 0xFFFFFFFF*, I didn't think it was a problem, as entering this key does decode the zone. knowing this, would it be possible to brute force only the last 4 bytes of the key and assume the first 4 bytes is 0xFFFFFFFF ??, so that at least some of the time the zone is passively decoded? would brute forcing a 4 byte key be feasible on a desktop pc?

[SEQLurker]

Hmm... I haven't played around with the key pullers, and thus haven't seen any sample keys, but out of curiosity, if it doesn't start with 0xffffffff, does it start with 0x00000000? If so, it'd seem that sony is using a signed 32bit number in a 64bit space, and that could at least narrow down the search quite a bit.

[high_jeeves]

It is simply a bug in their keygen algorithm. They can (and probably will) fix it quickly.. For now, they are valid keys. They happen roughly 30-40% of the time, from what I have seen. They are not mathmatically significant. The key still takes all 64 bits of space, they are not just sign extending, as many people have suggested (that would make it a 32 bit key, NOT a 64 bit key..)

--Jeeves

[devnul]

"It is simply a bug in their keygen algorithm"

Sorry you're wrong.

Working As Intended (tm)

hehe

dn