I agree with this despite the fact that any and every device should function even under such an attack. The medical industry is actually LESS competent than the median of industries in regard to computer and network security. They are being pushed by things like HIPAA, but that push is not necessarily resulting in things done the right way, since it's coming from lawyers instead of engineers.
First check to see if the medical practice relationship contract with the hospital provides for authorized pentesting in some way. It may well be completely legal. Proper pentesting would let you know that it will be done, though typically without informing you of the time or source IPs (not knowing makes it a more valid test). They should then provide you with a report so you can make corrective action.
Under the theory that multiple layers of protection are a good idea, actual pentesting might need to be done in ways that can test all layers. If you have a smart firewall that detects attempts and blocks the attacking IP address in whole, then that pentesting is actually incomplete. The should be an (arranged in advance) unblocked pentest to test actual hosts. An alternative to that is to run this phase of pentesting directly on your LAN. You need to have protection from in-LAN attacks, too, such as my infected computers or compromised employees (disgruntled or selling info).
So far, though, it sounds like the hospital is doing some rather lame pentesting. You and they need to contact some professionals.
If the content industry does not want to market their (usually crappy, but sometimes there are exceptions) content to me and people like me (Linux and BSD users), then so be it. But then they would be liars if they claimed that they were losing any money by me and people like me (Linux and BSD users) viewing, listening to, or reading their content. If they made the decision to not seek business revenues from me and people like me (Linux and BSD users), then they need to sleep in that bed.
People still need to know if THEIR URL is subject to a search engine entry takedown. The only case where the search engine would not need to provide it is if the party doing the takedown ALSO sends the info to the owner of the URL.
... with a bootable SD card that will wipe the hard drive and re-image it with the OS. It takes a while to write the whole hard drive, so this is a per-day thing, rather than a per-user thing. Eventually I plan to move to a virtualized system where I can "fake wipe" the hard drive more instantly, and even give each user their own VM.
Hell, I've been doing it in Firefox since I can't remember. It's called the -no-remote option. With a little scripting around it, every Firefox window is its own process in its own home directory. I can make permanent ones (I have one for Slashdot, for example) or temporary ones.
I'd rather use HTTP PUT to store the files. I'd rather it just delete from the upload directory as soon as encryption is done. I'd rather use a file system with a security erase feature. I'd rather then further upload the encrypted directory to my server instance which allows some otner server instances elsewhere to pull the files, without any logging.
Slashdot Mirror
I agree with this despite the fact that any and every device should function even under such an attack. The medical industry is actually LESS competent than the median of industries in regard to computer and network security. They are being pushed by things like HIPAA, but that push is not necessarily resulting in things done the right way, since it's coming from lawyers instead of engineers.
First check to see if the medical practice relationship contract with the hospital provides for authorized pentesting in some way. It may well be completely legal. Proper pentesting would let you know that it will be done, though typically without informing you of the time or source IPs (not knowing makes it a more valid test). They should then provide you with a report so you can make corrective action.
Under the theory that multiple layers of protection are a good idea, actual pentesting might need to be done in ways that can test all layers. If you have a smart firewall that detects attempts and blocks the attacking IP address in whole, then that pentesting is actually incomplete. The should be an (arranged in advance) unblocked pentest to test actual hosts. An alternative to that is to run this phase of pentesting directly on your LAN. You need to have protection from in-LAN attacks, too, such as my infected computers or compromised employees (disgruntled or selling info).
So far, though, it sounds like the hospital is doing some rather lame pentesting. You and they need to contact some professionals.
If the content industry does not want to market their (usually crappy, but sometimes there are exceptions) content to me and people like me (Linux and BSD users), then so be it. But then they would be liars if they claimed that they were losing any money by me and people like me (Linux and BSD users) viewing, listening to, or reading their content. If they made the decision to not seek business revenues from me and people like me (Linux and BSD users), then they need to sleep in that bed.
How do I say "contradiction of terms" in French?
People still need to know if THEIR URL is subject to a search engine entry takedown. The only case where the search engine would not need to provide it is if the party doing the takedown ALSO sends the info to the owner of the URL.
... a use for my Wicked Laser. Oh wait, which one should I use? Teh green one? Teh blue one?
... with a bootable SD card that will wipe the hard drive and re-image it with the OS. It takes a while to write the whole hard drive, so this is a per-day thing, rather than a per-user thing. Eventually I plan to move to a virtualized system where I can "fake wipe" the hard drive more instantly, and even give each user their own VM.
Time to close all your browser windows.
Has anyone downloaded Firefox 24 yet? I want to know if Firefox 25 is any good.
Next week!
Hell, I've been doing it in Firefox since I can't remember. It's called the -no-remote option. With a little scripting around it, every Firefox window is its own process in its own home directory. I can make permanent ones (I have one for Slashdot, for example) or temporary ones.
Triple-rot13 FTW!
I hate Anonymous Coward on Slashdot...
What used to be some witty humor and unusual perspectives has become noise and spamming and just posting too fast everywhere.
Jul jnf fhpu n cbbe rapelcgvba nytbevguz pubfra? Rirelbar xabjf gevcyr-ebg13 vf orggre.
... when the watcher does more than just watch.
... so why limit people to browsers?
Put some photos on the SD card, so they will see what they expect. If you are British, you may want to avoid that big blob of random bits.
Are you sure there is no back door in it?
I'd rather use HTTP PUT to store the files. I'd rather it just delete from the upload directory as soon as encryption is done. I'd rather use a file system with a security erase feature. I'd rather then further upload the encrypted directory to my server instance which allows some otner server instances elsewhere to pull the files, without any logging.
I don't use passwords, you insensitive clod.
That and an accidental DMCA takedown.
New Hampshire?
Sucking a quarter billion dollars from the economic recovery.
Your database-using commercial application should "just work" on any database.
Modifying things in CentOS, Debian, Fedora, and Ubuntu isn't a simple task to get it all right. In Slackware it is definitely simpler.
Oh, the topic? I use Postgres.
Yeah, I'm sure they want to extradite you, Anonymous Coward.