Pnet Whitelisting

Our homebrewers need to make a Hpnet, one that works with Dev360 and maybe also devxbox1 ... Than leave the real dev alone and buy more M$ stuff. (Im not sure if its possible and if my idea can be serious) but my idea of playing with devkits is to research and make more fun for xbox, and in the end maybe help real gameprogrammers get ideas or even hire us somehow or someway. (Dont kill the real scene and the homebrew scene)

 

I like XDK's I want to keep that part going it's just the pnet part. If everyone used it properly then this wouldn't have been a problem. But I do agree with you, we should have some Hnet HomeBrew Network.

 

pnet hasnt been good since the jtag hack...

also xlink kai works great on devkits...

 

You know what? I ask everyone how knows his/her xbox will be blocked by this record all network traffic browsing and downloading stuff on pnet. just do it, and try to get keys from the network traffic. so maybe we can recreate such a save network with alsmost equel tech. maybe reversengineeer stuff for the xbox1... but maybe its all encrypted forever and unusable for ever.

Next Pnet Enabled XDK will be sold with an WAN Ip to "proxy" with

 

The only thing xlink is good for is for halo. We need a new complete system that we can patch directly into the xbox dashboard. We need our own xbox live server, finding exploits isn't going to do anything besides last less than a week and then get us banned.

 

What if we just made a VPN server?

 

all this is illogical... only way your getting on is to have someone whitelist your ip...i remember trying something similar with another console... most companies have wayyyyy more than 1 ip...so in order for people to sell vpns or anything they would need to hack a dev studio,find the right ip range thats white listed, setup a vpn tunnel on one of those computers (if there are any on that specific ISP IP addie) then would have to give people access... too much effort to get pwned in no time. if someone figures all that out i doubt they would actually share access. just my 2 cents.

 

So that's why Metro-era recoveries want to trace your IP address and info when you first sign in! Haha, I honestly think they're a bit late to the punch with this considering Xbox 360 is almost 7 years old now, but it is definitely a smart move.

I think it was a good run until everything started getting leaked. Accessing a private developer's network was definitely an interesting experience, it just sucks that the potential to do so wasn't respected as it should have been by some.

Unless Microsoft forces a mandatory network shutdown for maintenance, someone might be able to fly under the radar and sign into PNET right before the changes take effect (Halo 2 style). I wouldn't be surprised if a few show-offs and 133kers tried that approach to be like "key-holders" among unauthorized XDK owners (at least among owners who don't have enough in-house contacts).

 

whenever pnet maint is done it always has downtime...

 

So it seems all that needs to be leaked is the "IP Address Whitelisting Tool". I bet it's all automated. Use that tool to send your WANside IP to some MSFT server that stores it in the whitelist database. Access granted.

 

your kidding right? you think ms is stupid to make a tool work without adding 1 initial ip first? >_>

 

I just think trying to exploit or reverse-engineer that tool would be a more plausible solution than trying to VPN through random studios.

 

... i quit.

 

MS will just ask your IP, then lock it to your deal and maybe Kit-Serial. Goodluck with hacking that app.. the database shows no Devkit with that Serial or Serial already locked to an IP please contact your MS Support or die.

Lets think about how YOU woald fix the problem, and maybe cheap ass to... Sad MS dint think abou that sooner (In Developers eyes, me as Homebrewer I think its better for dev and MS, a bit less fun times for us..)

Also, Yeah, FIx that local Free Live for X1 and pnet for us.... hack that livedash to frag. 2cent + some spam

 

If they had a log of all the console ID's (serial numbers?) - it would have been more effective to just ban all of those in the first place. As they have not, its not a stretch to conclude that they do not have that information.

Also, people are generating keyvaults - so again, ID's not so helpful. Id imagine thats why they have had to resort to a IP whitelist.

 

totally agree.

also as far as logging consoleid etc... devs can have anywhere up to hundreds of kits in 1 studio... MS doesnt actually have a security team monitoring pnet... thats the whoe point of whitelisting. the best way to look at this is to think of it like sp-int and prod-qa on ps3...