164w ago - A few months back it was first reported that a Sony ban wave was imminent, and today DJLO over at PSX-Scene reiterated the fact that it's only a matter of time until Sony begins banning PS3 JailBroken consoles.
To quote: Folks, Sniffynose pointed me to this. Since we are all updating now, you ALL need to read this and pay attention
On boot the system contacts the server and uploads the play list etc. this list alone is enought to get anyone that goes online banned as it shows the bootmanger etc. has been running. Here is the list and what they do, I port sniffed this a while ago before I went online with a retail unit >.> because I am not stupid hehe.
All these need to be blocked, web access will still work, updates will still work, but psn and any system messages/ads/communication will be blocked completely. For other areas someone would have to sniff the addresses again to compare. North American Servers are listed.
fus01.ps3.update.playstation.net > Update Server (sys updates)
mercury.dl.playstation.net > What's new ads
nsx.np.dl.playstation.net > playstation store preview
nsx-e.np.dl.playstation.net > ads
(main file exchange connections)
us.np.stun.playstation.net > on boot initiates connection
ena.net.playstation.net > SSLv3 connection after above connection
dus01.ps3.update.playstation.net > secondary update attempt (could force updates)
auth.np.ac.playstation.net > SSLv3 authentication server
service.playstation.net (has multiple IPs if only the ip address is blocked)
creepo.ww.hl.playstation.net (uploads crash reports etc.)
Almost all connections cannot just be port blocked, the port will continue to increment until it connects, you have to block the entire domains. Also a big point is that ALL computers on your network need to have these blocked not just the PS3's MAC because if you are running a proxy for example to get patches, the computer you proxy to will just allow the connections right out to the open unless all local IPs are blocked from these sites as well."
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
At this point I don't think anyone can absolutely say what it being sent back to Sony (or what info Sony actually keeps) because there are various encrypted connections (SSL) which according to my logs often vary in size each time they are sent. These connections could contain something (or nothing) incriminating.
If we could intercept this data before it is encrypted (ie: before it hits the SSL library) then we might get some answers.
Lately, I change all homebrew title ID's to those of a known game so my pushlists no longer contain ABCD12345, etc. but like many people in the beginning I didn't do this and my logs probably did get sent with homebrew ID's.. But I guess we'll see..
While I realise this is possible the problem is if Sony is going to issue a banhammer for consoles that have sent information to their servers while jailbroken with backup manager then I'm in trouble. While trying to network my console to my computer i accidently had it online and bam, my info has been sent.
If I update to 3.50 even with a clean drive they will still have my PSID having used backup manager and could place me in a ban wave. Then i'm stuck with a console that can't be jailbroken and can't go online. At this stage it looks like i have to spend $500USD for a new console.. yes that is the price for one here in Australia... ridiculous! I'm holding off to see what happens but I do miss playing online.
The question I would like to see answered is what exactly is being sent. Is it just a game list and other annonymous information or is our PSID being sent with it, clearly identifying the console. If there is no PSID being sent then it should be safe to update.
When no one fully understands the nature of the info sent when our ps3's "phone home" I for one don't care to find out the hard way. It took me all of 2 min to copy/paste these URL's into my router.
Wanna be one of the first victims when/if someone figures out a way to get us online again? Bury your head in the sand and let your hardware keep telling on you. Problem solved. No offense to anyone who is skeptical but enough time on the 360 scene and you learn to be precautionary.
PPL there found out the hard way about your offline unit logging backups in NAND and then phoning it all in the second you connected. If it takes very little of my time to do why not do it even if it never does any good? Being permabanned is a high price to pay and I'd never stop kicking myself if it turned out preventing it was something that was simple. IMHO it pays to err on the side of caution.