There is no proof b/c there has been no mass banning of PS3 users yet…this method is all speculation…..until we have people getting banned, we don't know if this method is a joke or not
Printable View
That's the whole point. The applications that aim to wipe history just delete the files mentioned here, though I haven't noticed any of them deleting 'boot_history.dat' from user's home directories. But since they just delete the files you need to keep on wiping the history whereas if they are read-only they will always be empty.
Also, if you are unlucky your PS3 might just send the pushlist out before you've wiped it and thus your backup-manager could still show up in them.
Pushlists get sent even without signing on to PSN. PS3 tries to send them out if it has internet connection, regardless of whether or not you're signed on. That's why it's a good idea to keep them clean all the time.Quote:
oh and btw...i think you use wipe history after you mount your game and before you connect to psn EVERY time.
AFAIK it keeps sending the list on periodic intervals, not only when booted.Quote:
the ps3 sends the pushlist when you turn it on. Does it only do it then or does it as soon as it gets internet access? Just a though.
Why? If nothing gets sent it could for example be because you've accidentally left your PS3 on, or your kid has turned it on, or your cat jumped on the remote, and so on. There's plenty of reasons why it could be on without sending anything and as such Sony can't really know whether or not it is a legitimate reason.
Sure, crafting fake pushlists would be the best way, but then those would have to be changed every now and then so as to avoid always sending the same pushlist over and over as that would attract even more attention. A custom application for PS3 which carefully modifies the pushlist on random intervals would likely be the Right Way To Go (TM).
I think he means if you are actually playing a game or using an app while connected even though nothing is sent they might be able to still see what is currently running on your PS3, but it seems like they would have to catch you in the act that way. I really doubt they have some monitoring system anyway right now like that since the bans haven't been coming in large amounts.
It COULD be possible, but what I've seen so far it looks like they actually didn't think of implementing such as they believed no one would be able to access the actual pushlist files and thus they just assumed them to always return all the relevant data. From what we've seen so far Sony and their affiliates implemented everything all the way from the start with the belief that PS3 is 100% safe and thus there is no need to sanitize input or add real-time monitoring anywhere, and that's also why cheating is so rampant at the moment. If they did sanitize input then that already would cut out most of the cheaters.
Though of course they can add such capability to PSN and release a new firmware later on which implements the on-the-fly monitoring capabilities. At that point it will likely be impossible to get online with CFW anymore.
Ive been logging in with Kmeaw 3.55 with 3.56 version spoofer, f*ckpsn 0.5 (the one that hides console ID) and psNinja v3 which clears history and makes files read only. Ive had the email from sony and im still good. Might start using PSIDPatch as well.
Should maybe mention Im a UK psn user with no new TOS to speak of.
Anyone using this set up had troubles?
I tried psNinja myself and it actually fails to make the files read-only. It doesn't even report an error or anything, it just doesn't do anything to them. That's the whole reason why I wrote this tutorial on how to make them read-only manually. You should really check if they are indeed read-only just to be sure.