|
q36
|
 |
« on: April 08, 2010, 03:23:41 AM » |
|
I'm just curious why disabling live access for jtagged boxes isn't a part of the patching. It would be a good thing to keep idiot cheaters off of live and all this keyvault selling crap.
|
|
|
|
|
Logged
|
|
|
|
|
mataman
|
|
« Reply #1 on: April 08, 2010, 03:35:58 AM » |
|
What for? When you get on live without Jtag console you get ban almost right away.
|
|
|
|
|
Logged
|
|
|
|
|
Intruder
|
|
« Reply #2 on: April 08, 2010, 03:56:59 AM » |
|
What for? When you get on live without Jtag console you get ban almost right away.
totally agree... as for the post below yours, what a plonker first post and clearly cant read.... |
|
|
|
|
Logged
|
|
|
|
|
Arakon
|
|
« Reply #3 on: April 08, 2010, 11:42:29 AM » |
|
The "almost" is the key point. They get about an hour or so, enough time to really f*** up some online games. I agree, it would be nice to get live locked out on jtag consoles automatically, i.e. also so you can still use internet "safely" (for updates, timeserver etc).
|
|
|
|
|
Logged
|
I do NOT give support by email, PM, ICQ or whatever. Anyone annoying me that way will have his balls removed. With a rusty butterknife. Slowly. And I'll enjoy doing it.
|
|
|
|
maximilian0017
|
|
« Reply #4 on: April 08, 2010, 11:50:33 AM » |
|
Would be the next logical step, some people change the defaultgateway for the xbox to keep it off of live, but that cripples other possibilities.
|
|
|
|
|
Logged
|
|
|
|
|
m3ntal
|
|
« Reply #5 on: April 08, 2010, 01:29:25 PM » |
|
I've configured my firewall to disable only the ports used by Live. This allows my 360 to still access HTTP and other net services. Just inverse the directions supplied by Microsoft support for configured your router for Live support. Not as pure as disabling Live in XBR, and certainly doesn't stop cheaters from wrecking havoc for a short time, but works great for my needs.  |
|
|
|
|
Logged
|
|
|
|
|
neonpolaris
|
|
« Reply #6 on: April 08, 2010, 02:17:50 PM » |
|
Ports required by Live, per here: http://support.microsoft.com/kb/908874- TCP 80
- UDP 88
- UDP 3074
- TCP 3074
- UDP 53
- TCP 53
I've been blocking all access to the outside world for my 360. I assumed that all internet functionality ran through Live. Timeserver would be nice. What all functionality would work with only the Live ports blocked? Which updates, game or dashboard? |
|
|
|
|
Logged
|
|
|
|
|
routehero
|
|
« Reply #7 on: April 08, 2010, 02:22:26 PM » |
|
Blocking port 3074 should be enough to prevent you from getting in to Xbox Live.
Port 3074 is the "Live Services Platform" port. The IPs can be random -- publishers can have their own XLSP services that your titles may connect to. For the purposes of signing it, it would only ever be Microsft's IPs.
However, blocking TCP/80 from your Xbox to the internet would likely prevent any auto-update mechanism for software which attempted to take advantage of it.
|
|
|
|
« Last Edit: April 08, 2010, 02:27:27 PM by routehero »
|
Logged
|
|
|
|
|
ReverseAffect
|
|
« Reply #8 on: April 08, 2010, 02:57:46 PM » |
|
I'm just curious why disabling live access for jtagged boxes isn't a part of the patching. It would be a good thing to keep idiot cheaters off of live and all this keyvault selling crap.
i think i am going to quote this because the point is straying off key of what q36 posted this ain't about how we can block live access with our boxes. this is about kv sales and jtagged boxes going on live and cheating. which they have plenty of time to do...... can we stray back on key,because this is becoming a bigger issue... |
|
|
|
|
Logged
|
sick like a mofo..not reballing for a while...
|
|
|
|
b0rz_
|
|
« Reply #9 on: April 08, 2010, 03:02:05 PM » |
|
disabling xbox live in the dashboard itself seems to me a safer way than w/ a router that for human, or not, errors can fails, so xbox get banned for a small mistake!
i would approve xbox live disabling in xbr/freeboot.
|
|
|
|
|
Logged
|
b0rz FIRST THING to do BEFORE post: Read THIS Thread. XBOX360.FALCON_//_fbBuild.SMC.PCIe.BUG.FiX_//_DashLaunch_ PS3.SLIM.160GB_//_FW.3.41_ |
|
|
|
ReverseAffect
|
|
« Reply #10 on: April 08, 2010, 03:06:25 PM » |
|
i think that is a tad bit late, because of the code being known already
but we will see...
|
|
|
|
|
Logged
|
sick like a mofo..not reballing for a while...
|
|
|
|
b0rz_
|
|
« Reply #11 on: April 08, 2010, 03:17:52 PM » |
|
The fact that works are at the refinements stage and now is not a plausible option is not so bad, the important thing is that soon or later this proposal would become part of the patch set. I'm not in hurry, for now my router is doing its job well or at least, so it would seem.
|
|
|
|
« Last Edit: April 08, 2010, 03:20:54 PM by b0rz_ »
|
Logged
|
b0rz FIRST THING to do BEFORE post: Read THIS Thread. XBOX360.FALCON_//_fbBuild.SMC.PCIe.BUG.FiX_//_DashLaunch_ PS3.SLIM.160GB_//_FW.3.41_ |
|
|
|
neonpolaris
|
|
« Reply #12 on: April 09, 2010, 01:20:15 AM » |
|
Getting back to the main point, I don't think it would do much good to patch XBR to disable Live usage. It would only prevent it for a little while after each update at best.
|
|
|
|
|
Logged
|
|
|
|
|
maximilian0017
|
|
« Reply #13 on: April 09, 2010, 03:50:58 AM » |
|
Getting back to the main point, I don't think it would do much good to patch XBR to disable Live usage. It would only prevent it for a little while after each update at best.
Why would it only prevent Live access for a little time?, are you afraid people will hack it out of the patchset? People who are smart enough to patch it out of the patchset should be bright enough to understand that they will be banned quickly after connecting to Live. The port information is nice to know, there are ofcourse many points in the dash that you can patch to stop the dash from connecting to Live, maby the port is one way to stop it (at bootup open the port and keep it open.., change the portnumber etc) |
|
|
|
|
Logged
|
|
|
|
|
q36
|
|
« Reply #14 on: April 09, 2010, 04:21:02 AM » |
|
Well, I just think it's a win win situation if it's removed. The real problem with homebrew on consoles is the result of opening the system to that extent, piracy/cheating. Piracy has already happened anyway, but cheating on live is purely the result of exploited boxes, and not only does that ruin the service for people who pay for it and play legitimately, it puts pressure on and gives a bad name to enabling homebrew on consoles. It's not that hard to patch it out in xam.
|
|
|
|
|
Logged
|
|
|
|
|
TheFallen93
|
|
« Reply #15 on: April 09, 2010, 05:07:18 AM » |
|
Lets just patch xam to call KeBlowFuses in some of the live functions. This way no one will make this mistake.
|
|
|
|
|
Logged
|
|
|
|
|
neonpolaris
|
|
« Reply #16 on: April 09, 2010, 08:45:33 AM » |
|
Getting back to the main point, I don't think it would do much good to patch XBR to disable Live usage. It would only prevent it for a little while after each update at best.
Why would it only prevent Live access for a little time?, are you afraid people will hack it out of the patchset? That's exactly my thinking. People who are smart enough to patch it out of the patchset should be bright enough to understand that they will be banned quickly after connecting to Live.
They're going to be banned quickly already, that won't be any more of a deterent then than it is now. One person will patch it, release it, then every little glitcher will find it via google. Don't get me wrong, I'm not trying to protest it or anything. If the developers have the time, sure. But I would consider it a low priority item. |
|
|
|
|
Logged
|
|
|
|
|
ReverseAffect
|
|
« Reply #17 on: April 09, 2010, 09:06:16 AM » |
|
I don't know who said there ban quick,
(didn't want to bring this up but o'well)
I know 2 peeps that have been on live for almost 2 months
and play every day...so that banning within a day or so is a rummor....
|
|
|
|
|
Logged
|
sick like a mofo..not reballing for a while...
|
|
|
|
mataman
|
|
« Reply #18 on: April 09, 2010, 09:37:30 AM » |
|
It's not a rummor, that's a fact. I know 3 people who plugded to LIVE with Jtag and got baned within few hours. Besides I don't thing that those cheaters are big issue after all.
|
|
|
|
« Last Edit: April 09, 2010, 09:39:10 AM by mataman »
|
Logged
|
|
|
|
|
Kushan
|
|
« Reply #19 on: April 09, 2010, 10:21:51 AM » |
|
I realsie this is somewhat off-topic, but with people talking about how to disable Live I thought I'd offer this little nugget of info, since it hasn't been mentioned yet:
You can disable LIVE functionality on a JTAG WITHOUT blocking ports OR changing default gateways/DNS Servers or anything like that. Simply go into parental controls and put a lock on connecting to Live. The console doesn't make any attempts to connect to live* and you still have full HTTP access to the outside world (tested this myself using xm360 and Freestyle 1.2's NNTP functionality).
*As far as I'm aware, no information is currently sent to MS at all, but perhaps someone could confirm this?
|
|
|
|
|
Logged
|
|
|
|
|
Dilber MC Theme by HarzeM