Re: Strict Clean JAPH

Replies are listed 'Best First'.
Re^2: Strict Clean JAPH by Anonymous Monk on Aug 08, 2014 at 19:03 UTC
Not worth running. ... unrecognizable slang here ... Why?	[reply]
Re^3: Strict Clean JAPH by marto (Cardinal) on Aug 08, 2014 at 19:34 UTC
I'd hope that this is obvious to most. It's not a good idea to send an "unknown" payload to a system which you do not own. The link I gave shows what the tool this script is based on (well, essentially is) does. It's downright dishonest to post this here under the guise of an obfuscated JAPH Update: Fixed typo, additional text.	[reply]
Re^4: Strict Clean JAPH (reap socket obfuscation) by Anonymous Monk on Aug 10, 2014 at 07:19 UTC
Hi marto I'd hope that this is obvious to most. It's not a good idea to send an "unknown" payload to a system which you do not own. The link I gave shows what the tool this script is based on (well, essentially is) does. It's downright dishonest to post this here under the guise of an obfuscated JAPH Yeah, it was obvious without running the "obfuscation" that it opens a Socket and talks on it What is not obvious is why that should be reaped You offered a link as a reason to reap, but the link is also obfuscated :) it doesn't explain the reasoning The posting qualifies under ?node_id=237057#obfu The current guidelines say To reap a highly offensive posting Reap -- Please only do this for true troll posts and true duplicate posts. reapage is not for useless, stupid, off-topic, and annoying nodes: ignore them Obscure quite graphic material or material inviting legal action So , where does sending unknown payloads to systems you don't own fall? I think it falls under stupid/annoying... Consider simple eval Considered by idsfa: "Delete: Network based system exploit"! Final vote: (keep/edit/delete) = 6/4/21. Unconsidered by davido: Keep and Edit votes were sufficient to block reaping. Caveat Emptor. Consider Re: perl Tk help and Re^2: How should Perlmonks deal with Plagiarism? (legalese) Hi marto	[reply]
Re^5: Strict Clean JAPH (reap socket obfuscation) by marto (Cardinal) on Aug 10, 2014 at 08:25 UTC
Re^6: Strict Clean JAPH (vector) by tye (Sage) on Aug 10, 2014 at 17:06 UTC
Some notes below your chosen depth have not been shown here
Re^5: Strict Clean JAPH (reap socket obfuscation) by Anonymous Monk on Aug 10, 2014 at 14:06 UTC
Re^6: Strict Clean JAPH (reap socket obfuscation) by Anonymous Monk on Aug 10, 2014 at 18:28 UTC
Some notes below your chosen depth have not been shown here
Re^4: Strict Clean JAPH by hookbot (Acolyte) on Aug 09, 2014 at 19:39 UTC
Well, I actually thought it would be a fun exercise to de-obfuscate. There was no malicious intent. It actually works just fine and doesn't do anything wrong. But yeah, that does make sense about the "unknown" payload. Sorry if that offended anyone. I'll be more careful in the future.	[reply]
Re^5: Strict Clean JAPH by jdporter (Paladin) on Aug 10, 2014 at 13:15 UTC