Juped - Revision history

Pbug: /* Juping todays Internet */ wording jovial

2008-01-31T19:43:46Z

Juping todays Internet: wording jovial

← Older revision		Revision as of 12:43, 31 January 2008
Line 9:		Line 9:
	I did a bit of research to this and came to two conclusions which I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute, which gave me a new IP every time I reconnected. What I intended		I did a bit of research to this and came to two conclusions which I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute, which gave me a new IP every time I reconnected. What I intended
	to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is		to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is
	a sitting duck in networking. [[IRC]] requires you be connected for longer periods of time on the same [[IP]]. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over [[TCP]] sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not ~~sequential~~ IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections. The software I wrote for this is not available, but it		a sitting duck in networking. [[IRC]] requires you be connected for longer periods of time on the same [[IP]]. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over [[TCP]] sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not sequentially picked IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections. The software I wrote for this is not available, but it
	needs a [[firewall]] to catch non-connected states and writes into		needs a [[firewall]] to catch non-connected states and writes into
	those sessions.		those sessions.

Pbug: Opa Rader the jupe from Germany

2008-01-31T18:38:42Z

Opa Rader the jupe from Germany

← Older revision		Revision as of 11:38, 31 January 2008
Line 3:		Line 3:
	clear text session is simple, usually the job ends when it's an encrypted session (SSL or similar).		clear text session is simple, usually the job ends when it's an encrypted session (SSL or similar).

			[[Image:opa-the-jupe.jpg]]

	== Juping todays Internet ==		== Juping todays Internet ==

Pbug: /* Juping todays Internet */ which witch

2008-01-31T18:31:06Z

Juping todays Internet: which witch

← Older revision		Revision as of 11:31, 31 January 2008
Line 6:		Line 6:
	== Juping todays Internet ==		== Juping todays Internet ==

	I did a bit of research to this and came to two conclusions (which) I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute. What I intended		I did a bit of research to this and came to two conclusions which I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute, which gave me a new IP every time I reconnected. What I intended
	to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is		to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is
	a sitting duck in networking. [[IRC]] requires you be connected for longer periods of time on the same [[IP]]. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over [[TCP]] sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not sequential IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections. The software I wrote for this is not available, but it		a sitting duck in networking. [[IRC]] requires you be connected for longer periods of time on the same [[IP]]. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over [[TCP]] sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not sequential IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections. The software I wrote for this is not available, but it
	needs a [[firewall]] to catch non-connected states and writes into		needs a [[firewall]] to catch non-connected states and writes into
	those sessions.		those sessions.

Pbug: encrypted session jupe

2008-01-31T18:28:13Z

encrypted session jupe

← Older revision		Revision as of 11:28, 31 January 2008
Line 1:		Line 1:
	Juped in IRC talk means hijacked TCP connections. Back in a time when TCP connections used a lesser random value to set up their [[3 way handshake]] people "juped" others peoples IRC sessions. Someone on IRC with the nick Jupiter did it first and		Juped in IRC talk means hijacked TCP connections. Back in a time when TCP connections used a lesser random value to set up their [[3 way handshake]] people "juped" others peoples IRC sessions. Someone on IRC with the nick Jupiter did it first and
	people called it juping from then on.		people called it juping from then on. Juping and Hijacking a
			clear text session is simple, usually the job ends when it's an encrypted session (SSL or similar).

Pbug: /* Juping todays Internet */ <-- jovial

2008-01-31T16:36:50Z

Juping todays Internet: <-- jovial

← Older revision		Revision as of 09:36, 31 January 2008
Line 7:		Line 7:
	I did a bit of research to this and came to two conclusions (which) I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute. What I intended		I did a bit of research to this and came to two conclusions (which) I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute. What I intended
	to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is		to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is
	a sitting duck in networking. IRC requires you be connected for longer periods of time on the same IP. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over TCP sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not sequential IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections.		a sitting duck in networking. [[IRC]] requires you be connected for longer periods of time on the same [[IP]]. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over [[TCP]] sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not sequential IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections. The software I wrote for this is not available, but it
			needs a [[firewall]] to catch non-connected states and writes into
			those sessions.

Pbug: juping todays internet

2008-01-31T16:29:20Z

juping todays internet

← Older revision		Revision as of 09:29, 31 January 2008
Line 1:		Line 1:
	Juped in IRC talk means hijacked TCP connections. Back in a time when TCP connections used a lesser random value to set up their [[3 way handshake]] people "juped" others peoples IRC sessions. Someone on IRC with the nick Jupiter did it first and		Juped in IRC talk means hijacked TCP connections. Back in a time when TCP connections used a lesser random value to set up their [[3 way handshake]] people "juped" others peoples IRC sessions. Someone on IRC with the nick Jupiter did it first and
	people called it juping from then on.		people called it juping from then on.


			== Juping todays Internet ==

			I did a bit of research to this and came to two conclusions (which) I mentioned later. I used the ISP freenet to connect/disconnect a [[pppoe]] session every minute. What I intended
			to see was how someone could possibly hide from active scanners who look for a person to abuse them. This broke several concepts, such as keeping connected to IRC which is
			a sitting duck in networking. IRC requires you be connected for longer periods of time on the same IP. I also noticed that I received the latest connections from people on the IP before me. Apparently Deutsche Telekom forces a reset on pppoe connections every 24 hours. Anyhow I wrote a small program to take over TCP sessions that had states established and one victim was IRC connections. You then give a few commands on the juped connection to find out who had your IP before that. You can be sure that they weren't gone for more than 4 minutes the TCP default timeout. The conclusion I came to in this all is that an ISP pppoe pool should be as large as possible to allow someone to "hide". It should also give out truely random IP's not sequential IP's because a gang of Internauts can find out when you first connected and for how long you were on the link. And then of course it should quaranteen the IP's to reset any left over connections.

Pbug: jovial!

2008-01-31T16:20:34Z

jovial!

New page

Juped in IRC talk means hijacked TCP connections. Back in a time when TCP connections used a lesser random value to set up their [[3 way handshake]] people "juped" others peoples IRC sessions. Someone on IRC with the nick Jupiter did it first and
people called it juping from then on.