Certain proxy servers can be configured to intercept HTTPS traffic, and emulate a legitimate security certificate. This allows corporations to MITM their own employees and spy on their own HTTPS connections.
Blah, there's nothing being "emulated" (and nothing legitimate about it). It's just another predeployed trusted CA cert on the employee's computer, if the employee cares to check, they can easily tell they're being MITM'd
Will HTTPS stop the email? No. Will HTTPS stop a network email scanner from detecting malicious links in the email? Yes. Will HTTPS stop a malware scanner from analyzing a malicious payload in the email? Yes.
Uh, none of that will or will not stop any email because emails are transmitted via SMTP or SMTPS, geez. Your uid is low enough that you ought to know this.
Now, are you arguing for using SMTP instead of SMTPS? Yeah didn't think so.
While I'm not a fan of Zero__Kelvin, he is right. Client authentication is extremely rare in https connections. (And the average technological understanding on/. is absolutely shit)
In case you don't understand what that means: The client neither has nor supplies any cert in the TLS handshake, therefore there is no cert that can act as a cookie of whatever kind.
"Open-source software" is computer software with its source code made available with a license in which the copyright holder provides the rights to study, change, and distribute the software to anyone and for any purpose
I'm torn between making a snarky remark about how I, thanks to slashdot, finally learned what open source software is, or whether I should point out that in no way "open source" implies the right to "distribute the software to anyone and for any purpose" because that is clear and utter bullshit that only applies to free software (as in e.g. BSD-licensed stuff).
Technically if you have your kernel offer PCI bus access to userspace you could drive the USB host controller completely from there. Not that it would necessary be a good idea, but it would reduce the attack surface to the PCI driver/bus logic (as well as introducing a new potential security problem from userspace)
A stack of hard disks sitting next to my computer and containing a total of around 8 TB actual pseudorandom data beg to differ. Also every hard drive that was bought used and sold by someone with a little knowledge.
One solution to that problem is to completely (first to last sector) overwrite the disk with random data, then create a partition table and a legitimate filesystem on top of that, add some legitimate files, map the sectors that constitute free space of that filesystem to a logical contiguous block device, create crypto container on top of that, create filesystem on top of that, mount, enjoy.
I think you're on to something! If you use a graphene drone to find out where the golf ball ends up, with some AI and blockchain -- damn that's gonna be huge!
Slashdot Mirror
I'm not entirely sure what "hiding who accesses the endpoint from the endpoint itself." means, but please explain how HTTPS doesn't do that.
(Spoiler: you're full of yourself)
Certain proxy servers can be configured to intercept HTTPS traffic, and emulate a legitimate security certificate. This allows corporations to MITM their own employees and spy on their own HTTPS connections.
Blah, there's nothing being "emulated" (and nothing legitimate about it). It's just another predeployed trusted CA cert on the employee's computer, if the employee cares to check, they can easily tell they're being MITM'd
Web proxies that MITM TLS connections are way worse than proxies that outright refuse to do HTTPS.
(That said, this is about mail.)
Will HTTPS stop the email? No. Will HTTPS stop a network email scanner from detecting malicious links in the email? Yes. Will HTTPS stop a malware scanner from analyzing a malicious payload in the email? Yes.
Uh, none of that will or will not stop any email because emails are transmitted via SMTP or SMTPS, geez. Your uid is low enough that you ought to know this.
Now, are you arguing for using SMTP instead of SMTPS? Yeah didn't think so.
While I'm not a fan of Zero__Kelvin, he is right. Client authentication is extremely rare in https connections. (And the average technological understanding on /. is absolutely shit)
In case you don't understand what that means: The client neither has nor supplies any cert in the TLS handshake, therefore there is no cert that can act as a cookie of whatever kind.
You're sadly mistaken, or time traveling.
Can we please avoid cryptocurrencies being shortened to just "crypto" in the mainstream? Pretty please?
Or they just resisted the urge to brag about their hack on the Internet. Wonder why that is.
Is an altitude of one mile even enough to visually confirm earth is or is not flat?
"Open-source software" is computer software with its source code made available with a license in which the copyright holder provides the rights to study, change, and distribute the software to anyone and for any purpose
I'm torn between making a snarky remark about how I, thanks to slashdot, finally learned what open source software is, or whether I should point out that in no way "open source" implies the right to "distribute the software to anyone and for any purpose" because that is clear and utter bullshit that only applies to free software (as in e.g. BSD-licensed stuff).
s/issue/usage/ too
I only get around 600% CPU issue (3 HT cores fully busy) for the framerate of around 20 fps in that tanks demo. WAY TO GO!
Technically if you have your kernel offer PCI bus access to userspace you could drive the USB host controller completely from there. Not that it would necessary be a good idea, but it would reduce the attack surface to the PCI driver/bus logic (as well as introducing a new potential security problem from userspace)
It's 4.11 for Workgroups.
I'm pretty sure that those people know the concept "I", since that's what they're usually all about
A stack of hard disks sitting next to my computer and containing a total of around 8 TB actual pseudorandom data beg to differ. Also every hard drive that was bought used and sold by someone with a little knowledge.
One solution to that problem is to completely (first to last sector) overwrite the disk with random data, then create a partition table and a legitimate filesystem on top of that, add some legitimate files, map the sectors that constitute free space of that filesystem to a logical contiguous block device, create crypto container on top of that, create filesystem on top of that, mount, enjoy.
Many humans are not self-aware
Excuse me?
Come to think about it, the one thing I'd want even less than an Intel-run ME is a Google-run ME...
Nope, he isn't.
I think you're on to something! If you use a graphene drone to find out where the golf ball ends up, with some AI and blockchain -- damn that's gonna be huge!
If you built it from source, fair enough (modulo compiler backdoors /tips tinfoil hat).
If you didn't, my point still stands.
Now how would you do /that/ in turn?
Can you even point to the source code that your phone's firmware was built from?
If you look up,
Don't do
you might just be able to see
Don't see
the point of the article
Don't read
flying over your head.
Don't head
It's called PEBCAK