Re^5: Strict Clean JAPH (reap socket obfuscation)

Point taken, it won't happen again. In my defence I felt pressured to do this quickly. A senior monk had mentioned in the CB that some investigation should be done to determine what this code does, in addition to this I couldn't be as verbose as I should have due to parenting issues. I did manage to discuss the issue in some detail in the CB a short while after raising the consideration.

Comment on Re^5: Strict Clean JAPH (reap socket obfuscation)

Replies are listed 'Best First'.
Re^6: Strict Clean JAPH (vector) by tye (Sage) on Aug 10, 2014 at 17:06 UTC
There is no way to know what the code does... other than it being a vector for whatever code the author chooses to offer up at that IP address/port. When I saw this code I tried to download from the address but the service at that port had already been taken down. But it wouldn't have mattered if the code I had gotten was completely innocent. Because there is nothing to stop the author from changing what code is offered. The service can offer the same innocent code 99% of the time but add a malicious part 1% of the time. This type of code is simply unsafe to run. It is good that the node was reaped. - tye	[reply]
Re^7: Strict Clean JAPH (reap malicious code) by Anonymous Monk on Aug 11, 2014 at 08:35 UTC
This type of code is simply unsafe to run. It is good that the node was reaped. Hmm, its not the first unsafe code posted ... most aren't reaped ... PerlMonks FAQ doesn't mention evil or malicious or unsafe code, code that phones homes or downloads other code ... Giant block JAPH will be happy to read the explanation rm -rf / Malicious Code Re^3: Regex matching after ASCII characters	[reply]