Private info Vs. Public info

[tommyoz]

So what is the latest? Are the days of public info history or will be? Should we be sticking to private?

[Crazy1_79]

go private, it is definately safer.

[tommyoz]

Thanks for the response. My reason for the question is because I have a few IRDS that I changed to pubic for testing purposes (in other words just to play around). I needed the practice.

I guess I should return them to it's normal state of Private. Thanks for the heads up Crazy1_79

[Ohms]

It's like this.. Anything that sets you apart from a subbed users is a potential target.. The more public that thing is, the more likely they will target it. I have no idea why the public numbers have been allowed to go ECM Free for so long, but they are not any longer. It's time to stop using them NOW.

Try to use the most obscure methods. The more private your "fix", the better the odds are that you won't be targeted directly..

[skinerd]

Since most blockers in use are also public, even Romcode, and others, in reality public, (if you think about it, all they have to do is subscribe to the service and get the info) they can and have been targeted too........not saying Romcode has been targeted, but could be. Blocker hits have, so far, been on true, free public blockers.

[skinerd]

DVD makes a good point......

What I did for private info is:
Couple days ago I was successful in transferring the private numbers from the 510 flash into 2 different receivers, a 301-013 dual tsop, a 301-013 single tsop. This included SKs. I now have 3 receivers setup for private numbers, all use the same card file, all work 100%.

I did not use GenDT08 or anything else to generate any numbers, I simply transferred the receiver number, boxkeys and Sks from the 510 to the other 2.


See my other thread for more info...........

[JT]

Seems to me that the most likely targets are, in this order:

1- public blockers
2- public receiver info
3- private blockers like romcode
4- tier expiry dates beyond 90 days
5- open tiers that code for porn and ppv events
6- anything else that is in use by high numbers of people other than subs

Just how bad using public numbers on your receiver is going to turn out to be remains to be seen. So far, public numbers and emu are running fine. For how long, we'll see. So far, the only sure thing to avoid, IMO, is public blockers. So far public blockers are the only thing that has resulted in looping. They hit a penga blocker back in December, and last week hit the evilrom blocker. This is the easiest thing for them to hit and in use by the largest number of people. That's the criteria I based my rankings on. I doubt Charlie will make it past number 4 on my list. He'll probably keep hitting the easy targets in use by the most number of folks.

[JT]

DVD makes a good point......

What I did for private info is:
Couple days ago I was successful in transferring the private numbers from the 510 flash into 2 different receivers, a 301-013 dual tsop, a 301-013 single tsop. This included SKs. I now have 3 receivers setup for private numbers, all use the same card file, all work 100%.

I did not use GenDT08 or anything else to generate any numbers, I simply transferred the receiver number, boxkeys and Sks from the 510 to the other 2.


See my other thread for more info...........

How about posting a refresher or a link to where to find the receiver number, bk's, and sk's (or dt08) from an unlocked rom skinerd? I couldn't find the old thread to sticky it. It's a lot more pertinant now days. Also, I hadn't realized the dual chip .13 was still dto8. That must be the cut off eh? The single chip .13 and later models are sk and dual chip .13 and earlier are dt08. Did I get that right?

[1one]

How about posting a refresher or a link to where to find the receiver number, bk's, and sk's (or dt08) from an unlocked rom skinerd? I couldn't find the old thread to sticky it. It's a lot more pertinant now days. Also, I hadn't realized the dual chip .13 was still dto8. That must be the cut off eh? The single chip .13 and later models are sk and dual chip .13 and earlier are dt08. Did I get that right?


IRD info = DT01 = ird number forward and reverse
Sessesion key = DT 06/0D
Boxkeys = DT 06/0F

Earlier models such as DT receivers used at DT 0A instead of SK. 301-13 was the cutoff.
DT receivers = Data slice/Time slice

[skinerd]

How about posting a refresher or a link to where to find the receiver number, bk's, and sk's (or dt08) from an unlocked rom skinerd? I couldn't find the old thread to sticky it. It's a lot more pertinant now days. Also, I hadn't realized the dual chip .13 was still dto8. That must be the cut off eh? The single chip .13 and later models are sk and dual chip .13 and earlier are dt08. Did I get that right?

Well, I used the info from the 510 receiver, not from the card, but i believe GetDT08-SK will pull that from the card. Now that I look, I don;t think SKs are on card, the card reads them from the flash for decoding purposes.

I could not find SKs in any of the dozen or so dual tsop -013 files that I have. I put them in flash 2 exactly same address as a single -013, removing(FFing out) old receiver number and BKs. The flash won't read in flashedit, and looks funny in jkeys, but works fine.

[JT]

Thanks for the responses. As you can probably tell, I havn't worried about going private numbers yet. I do have a pair of dual chip .13's with unlocked ex sub rom102's though. Was going to use them to come up with some private numbers when and if Cemu with public numbers starts having issues. I might even go that route sooner just in case. Problem is, some of the IRD's I'm running are single chip .13's. I have four or five 301.10's I can convert too though.

[skinerd]

I am far from a card expert, most I get done by trial and error.

What I fail to understand tho, is how the public numbers work. To use them all you do is write the receiver number and BKs to the flash, removing SKs when present.

I treid to also use a -010 as a base, i have an ex-sub -010 and tried to get the numbers over to a single -013 and a 510, neither worked. I am missing something and not sure what. Is not a problem tho, I have several 510 ex-sub flashes and card files, and I can get those transferred w/o problem. Have not tried to get them going on a -010 yet, but after getting the dual -013 working with 510 numbers and SKs, I think I may be able to with a -010, just need to give it a shot.

[skinerd]

I could not find SKs in any of the dozen or so dual tsop -013 files that I have. I put them in flash 2 exactly same address as a single -013, removing(FFing out) old receiver number and BKs. The flash won't read in flashedit, and looks funny in jkeys, but works fine.

Further checking, DACA dual tsop is non SK tsop, DAJA however is SK.

I could have save myself some headaches if I would have checked that to begin with....as I added them to a DACA tsop, not knowing about them being in a DAJA.

[JT]

Further checking, DACA dual tsop is non SK tsop, DAJA however is SK.

I could have save myself some headaches if I would have checked that to begin with....as I added them to a DACA tsop, not knowing about them being in a DAJA.

Both my dual chip .13's are build DACA. :o Oh well. I have pleanty of .10's on the shelf to work with.

[skinerd]

Both my dual chip .13's are build DACA. :o Oh well. I have pleanty of .10's on the shelf to work with.

Just means married cards are DT08....not a problem at all.

[JT]

Just means married cards are DT08....not a problem at all.

Nope, not really. Like I said, it just means I'll have to run the .10's instead. I'll be more than happy to shoot you one or both of my tsop with matching rom images if you want skinerd. Please don't anyone else other than mods ask. I won't do it for just anyone. What's the use of having private info if it doesn't stay private. :cool:

[skinerd]

Nope, not really. Like I said, it just means I'll have to run the .10's instead. I'll be more than happy to shoot you one or both of my tsop with matching rom images if you want skinerd. Please don't anyone else other than mods ask. I won't do it for just anyone. What's the use of having private info if it doesn't stay private. :cool:


Thanks for the offer, but I have a few of my own. Just keep them in reserve, never know when they may come in handy.