It counts as console access, but that does not mean physical access. If you don't understand this, think about how you would install a $5 hardware keylogger over a network-accessible system console. If you do understand this, then WTF is your point?
No, that's actually more difficult, since you'll have to pull the server out of the rack, open it, potentially power it down. More visible, too. If you can't program yourself out of a wet paper bag, maybe. That said, I'd like to see you pulling that off over the network, too.
Or you could mount the filesystem that contains the program to unlock the disk and replace it with one that leaks the typed passphrase somewhere. But yes, the same can be had using a bootable usb drive. Then again, there are network-accessible consoles...
He is old enough to know that "facebook and twitter" are mere placeholders for $latest_trendy_social_platform. Like it mattered in the slightest which particular platform that actually is. Now get off our lawn, PFY.
They claim to be continuously "improving security", yes. So "$latest_windows is the most secure windows ever" isn't news. That said, last time I checked, "writing new code" was the opposite of "improving security", and that's what seems to happen for the most part. Would be difficult to keep selling new stuff otherwise, too.
But you use "shady sites", or maybe even totally un-shady sides, which cause foreign data to be processed by local processes. Takes one drive-by attack to break your amazing security scheme.
What protocol do you suggest to inform the router or firewall what program it is that produced the packets in question? How do you secure it? How to you cope with spoofing? Ohhh, you're talking about the software "firewall" that is built right into the OS you're trying to tame. Yeah, that sounds useful.
Generally speaking, if someone is able to abandon Windows, there's a good chance they may be able to abandon PCs altogether and simply use a tablet with a keyboard attached or even a smartphone for day to day computing and communications tasks.
There's an equally good chance that they are able to abandon Windows because they have reached a level of basic computer literacy that makes them realize they don't need $product to do $simple_task, for most simple tasks. And how to break down $large_task into those.
Oh, damn, I never knew. I pretty viably used it exclusively between 2006 and 2011, after which i switched to BSD, but not because Linux wasn't viable. What do I do now, purchase Windows?
What does God need a transgender for, and where does he keep it?
Spare us your bizarre phantasies, please.
Yawn.
Actually, "Lunix" means "Linux Torvaldes's Unix."
Actually, "Lunix" stands for "Losers' unix".
Love from BSDland
The irony.
As if Germany wouldn't be in trouble if a French nuke plant shat itself...
It counts as console access, but that does not mean physical access. If you don't understand this, think about how you would install a $5 hardware keylogger over a network-accessible system console. If you do understand this, then WTF is your point?
Does too, if the console is accessible over the network....
No, that's actually more difficult, since you'll have to pull the server out of the rack, open it, potentially power it down. More visible, too. If you can't program yourself out of a wet paper bag, maybe.
That said, I'd like to see you pulling that off over the network, too.
I used to like sonic boom. Haven't heard one in years though.
Have you even read the comment you're replying to? If not:
you could mount the filesystem that contains the program to unlock the disk and replace it with one that leaks the typed passphrase somewhere.
If you think you could get around that issue by simply having the unlocking-program on the encrypted disk, then I might have a bridge to sell to you.
Or you could mount the filesystem that contains the program to unlock the disk and replace it with one that leaks the typed passphrase somewhere.
But yes, the same can be had using a bootable usb drive. Then again, there are network-accessible consoles...
He is old enough to know that "facebook and twitter" are mere placeholders for $latest_trendy_social_platform. Like it mattered in the slightest which particular platform that actually is. Now get off our lawn, PFY.
They claim to be continuously "improving security", yes. So "$latest_windows is the most secure windows ever" isn't news.
That said, last time I checked, "writing new code" was the opposite of "improving security", and that's what seems to happen for the most part. Would be difficult to keep selling new stuff otherwise, too.
That said, MS has labeled every version of Windows as 'the most secure windows' ever since computers are regularly networked. Geez.
Why, isn't it systemd-mp3d that enables this newfangled mp3 support in the first place?
The web is. The Internet is fine.
Pretty sure you replied to the wrong post there
That was my point.
No. You cannot expect your "firewall" to effectively control the OS when it is the OS that controls the "firewall".
1) I don't run random programs from shady sites
But you use "shady sites", or maybe even totally un-shady sides, which cause foreign data to be processed by local processes. Takes one drive-by attack to break your amazing security scheme.
Block telemetry at the edge firewall.
How do you identify what is telemetry and what isn't?
What protocol do you suggest to inform the router or firewall what program it is that produced the packets in question? How do you secure it? How to you cope with spoofing?
Ohhh, you're talking about the software "firewall" that is built right into the OS you're trying to tame. Yeah, that sounds useful.
Generally speaking, if someone is able to abandon Windows, there's a good chance they may be able to abandon PCs altogether and simply use a tablet with a keyboard attached or even a smartphone for day to day computing and communications tasks.
There's an equally good chance that they are able to abandon Windows because they have reached a level of basic computer literacy that makes them realize they don't need $product to do $simple_task, for most simple tasks. And how to break down $large_task into those.
Oh, damn, I never knew. I pretty viably used it exclusively between 2006 and 2011, after which i switched to BSD, but not because Linux wasn't viable. What do I do now, purchase Windows?