77
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Nov 2024
77 points (98.7% liked)
No Stupid Questions
36044 readers
3549 users here now
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
founded 2 years ago
MODERATORS
There are a lot of answers here but I feel they mostly miss OP’s point so I’ll try my own:
What stops a scammer from HTTPS certifying foobar.reputable.com is the trust system.
Anybody can create a certificate on their machine for anything within seconds, even you could create a certificate for www.google.com. The problem is that you, as an issuer, are not trusted by anybody.
Browsers and operating systems are released with a list of issuers that are considered trustworthy, so if you want your certificate to be recognised it has to come from one of these, not from you.
All of these issuers are in the list because they have been individually vetted, and are known to do their due diligence before issuing certificates, so they would not give you that cert unless they know that the bank domain or subdomain belongs to you, and the technical means to achieve this have been explained in other answers.
But if one of these issuers went rogue, or if you hypothetically hacked into their certification authority, then indeed nothing would stop you from obtaining a valid and recognised certificate for foobar.bank.com.
This is why for example Trustcor was removed from this list in 2022: from that position it would be trivial for a certificate authority to allow third parties to spy on people.
And when you are requesting a certificate for foobar.bank.com, your certificate request must come from an authorized email address at bank.com. That is also where your issued certificate would be sent. So, in order to get a certificate from a third party issuer, you have to:
Could a malicious actor compromise that mailbox in a way that allows them to request a certificate and then receive it? It's not impossible, but it would be a huge effort with a small payout. Honestly, if you've got access to that mailbox, you don't want to give yourself away by making false certreqs through it. You want to just exfiltrate as much data from it as you can. There's certainly something way more valuable in there.
That isn't true in general. In fact, it can't be.
It might be policy for most cases from the well-known certificate authorities, but it's not part of the protocol or anything like that.
If it were, then it would be impossible to set up your mailserver to begin with because you could never get a certificate for mail.bank.com
Yeah, letsencrypt doesn't do this for example. They do ask for an email address, but that's just for expiry notices.
They do require you control the domain, and run it on the server the DNS record points to. When using certbot at least.
I was wrong again today.
You don't need a https cert for a Mail server, fyi
Really? They don't use TLS at all? That sounds hilariously insecure
The email ecosystem is changing in recent years but yeah, it's best to expect that there is at least one opportunity for any given email to be sent over the internet unencrypted. MTA-STS has been slowly changing the landscape but adoption isn't going all that great.