Live data from Hacker News

Knock Knock Who's There? – An NSA VM

reverse.put.as

11–20 of 46 posts

Re: Knock Knock Who's There? – An NSA VM

#11
post #7
post #2

It seems most vulnerabilities published by shadow brokers are on Windows. What percentage of vulnerabilities are focused on Linux or macOS? What can ordinary users do to protect themselves other than patching?

Most ordinary users will connect to the internet using a router provided by their ISP so port knocking does not work. Unless they plant the malicious code on the router - that would be even harder to detect.

[deleted]

Re: Knock Knock Who's There? – An NSA VM

#12
post #10

> I made local presentations at 0xOpoSec and BSidesLisbon but those slides were never published for obvious reasons (aka live implants all over the Internet). I don't understand. Or does this mean because the malware was being used you refused to publish documentation about it? Because you think people targeted by nation states are evil? Intelligence services are the worst terrorist organizations, and most people tar…

Live implants, means if they published you or I can access the implants and therefore the victims' systems.

If you've got root RCE can't you use it to "close" the implant and make sure noone gets hurt like some have been doing to counteract IoT botnets? How is leaving a gaping hole better?

EDIT: To those saying it would be a legal liability risk, isn't it a criminal offense in your jurisdiction if you know about a danger to someone else, not to do something about it if only warn them? (non-assistance à personne en danger, in french law) Or couldn't you partner with a security research lab with better legal counsel?

Re: Knock Knock Who's There? – An NSA VM

#13
post #10

Earlier quoted context omitted.

Live implants, means if they published you or I can access the implants and therefore the victims' systems.

If you've got root RCE can't you use it to "close" the implant and make sure noone gets hurt like some have been doing to counteract IoT botnets? How is leaving a gaping hole better? EDIT: To those saying it would be a legal liability risk, isn't it a criminal offense in your jurisdiction if you know about a danger to someone else, not to do something about it if only warn them? (non-assistance à personne en danger,…

depends if you want to take the risk of being prosecuted for illegitimately accessing multiple computer resources

Re: Knock Knock Who's There? – An NSA VM

#14
post #10

Earlier quoted context omitted.

Live implants, means if they published you or I can access the implants and therefore the victims' systems.

If you've got root RCE can't you use it to "close" the implant and make sure noone gets hurt like some have been doing to counteract IoT botnets? How is leaving a gaping hole better? EDIT: To those saying it would be a legal liability risk, isn't it a criminal offense in your jurisdiction if you know about a danger to someone else, not to do something about it if only warn them? (non-assistance à personne en danger,…

That's illegal. You can't break into someones house to kick out a burglar. The people that have counteracted and kicked out bots from botnets broke laws in several countries (fed crime in US), which is why they don't publicize their identity (even if they did, prosecutors may not come after them). You need the consent of the system owner to help them with the intrusion, otherwise anyone can hack into someone else's computer and say they were there to get rid of some malware.

Re: Knock Knock Who's There? – An NSA VM

#15

> I made local presentations at 0xOpoSec and BSidesLisbon but those slides were never published for obvious reasons (aka live implants all over the Internet). I don't understand. Or does this mean because the malware was being used you refused to publish documentation about it? Because you think people targeted by nation states are evil? Intelligence services are the worst terrorist organizations, and most people tar…

I sure wouldnt want you to have access to these :p

Re: Knock Knock Who's There? – An NSA VM

#16
post #10

Earlier quoted context omitted.

Live implants, means if they published you or I can access the implants and therefore the victims' systems.

If you've got root RCE can't you use it to "close" the implant and make sure noone gets hurt like some have been doing to counteract IoT botnets? How is leaving a gaping hole better? EDIT: To those saying it would be a legal liability risk, isn't it a criminal offense in your jurisdiction if you know about a danger to someone else, not to do something about it if only warn them? (non-assistance à personne en danger,…

You would be taking on a lot liability and responsibility if you did that.

Re: Knock Knock Who's There? – An NSA VM

#17
post #3

Earlier quoted context omitted.

Rootkits/exploits appear on any operating system. Wipe and reinstall often, rotate passwords at same time, also teaches good backups. ad blocker by default and always up to date system. Use VMs or other machines for dubious websites and wipe those often (like a raspberry?) Careful what you execute on your machine Then if you're really paranoid: Some external firewall running suricata for alerting Logging to an extern…

In this spirit I've been playing with spun up Firefox instances in a Google Cloud Run. The container is stateless and goes away after I close the page that connects to video stream of the other container in my browser.

Do you find the performance satisfactory enough for daily browsing?

Re: Knock Knock Who's There? – An NSA VM

#18
post #15

> I made local presentations at 0xOpoSec and BSidesLisbon but those slides were never published for obvious reasons (aka live implants all over the Internet). I don't understand. Or does this mean because the malware was being used you refused to publish documentation about it? Because you think people targeted by nation states are evil? Intelligence services are the worst terrorist organizations, and most people tar…

I sure wouldnt want you to have access to these :p

Not interested anyway, but thanks! :P

I just want holes to be fixed.

Re: Knock Knock Who's There? – An NSA VM

#19
post #3

Earlier quoted context omitted.

Rootkits/exploits appear on any operating system. Wipe and reinstall often, rotate passwords at same time, also teaches good backups. ad blocker by default and always up to date system. Use VMs or other machines for dubious websites and wipe those often (like a raspberry?) Careful what you execute on your machine Then if you're really paranoid: Some external firewall running suricata for alerting Logging to an extern…

In this spirit I've been playing with spun up Firefox instances in a Google Cloud Run. The container is stateless and goes away after I close the page that connects to video stream of the other container in my browser.

For all intents and purposes Google is the civilian NSA, I'm not sure you're gaining anything by creating VM in their cloud!

Re: Knock Knock Who's There? – An NSA VM

#20

Earlier quoted context omitted.

In this spirit I've been playing with spun up Firefox instances in a Google Cloud Run. The container is stateless and goes away after I close the page that connects to video stream of the other container in my browser.

For all intents and purposes Google is the civilian NSA, I'm not sure you're gaining anything by creating VM in their cloud!

I'm assuming they want some protection against adtech companies or the local coffee shop sysadmin. Running Firefox in the cloud "to avoid detection by the NSA" would indeed be quite foolish.
Post reply on HN