5 ms·

Is one mitigation TLS certificate verification?

by pitaj 5y ago

xenophonf 5y ago
- rat9988 5y ago
  > Why not read the linked paper, You answered your own question. The answer is in page 12, which means there is too much information. He is not interested in the whole topic, just about this question. So he asks, maybe someone is charitable enough to answer. Nothing wrong with it.
  - tedunangst 5y ago
  - xenophonf 5y ago
    How could I possibly answer their question better than the experts who wrote the paper?
    - rat9988 5y ago
      Maybe you can't but someone else can. The question is open to anyone who can and wants to answer.
      - xenophonf 5y ago
        But the answer is right there, section 2, starting on page 12 of the linked paper. We're hackers. Autodidacticism is our creed. Research papers are our bread and butter. Why settle for speculation from the pseudonymous masses when a rich vein of well written analysis by reputable authors is one click away?
  - nixpulvis 5y ago
    Skim until you are in the right section? Literally titled: "Section II - Mitigation of bitsquatting attacks"
simulate-me 5y ago
It depends on whether or not the client specifically requested, or is expecting, traffic over HTTPS. But yes, if the user's client requests encrypted traffic, the attacker will not be able to produce a valid certificate. This attack isn't that different than a MITM.
- tedunangst 5y ago
  Nothing prevents an attacker from getting a cert for snytimg.com or oslashdot.org.
  - legalcorrection 5y ago
    That only helps the attacker if the error happened before reaching the DNS-specific path. If the error happens inside the DNS path, then the browser is still expecting to get a certificate for the correct website.
    - tedunangst 5y ago
      If the error happens inside the DNS path, the name in the answer won't match the name in the query. The browser is still expecting to get an answer for the hostname it sent.
      - deleted 5y ago
        [deleted]
legalcorrection 5y ago
Depends on where in the stack the error happened.

Is one mitigation TLS certificate verification?

by pitaj 5y ago

Is one mitigation TLS certificate verification?

xenophonf 5y ago

rat9988 5y ago
> Why not read the linked paper, You answered your own question. The answer is in page 12, which means there is too much information. He is not interested in the whole topic, just about this question. So he asks, maybe someone is charitable enough to answer. Nothing wrong with it.
- tedunangst 5y ago
- xenophonf 5y ago
  How could I possibly answer their question better than the experts who wrote the paper?
  - rat9988 5y ago
    Maybe you can't but someone else can. The question is open to anyone who can and wants to answer.
    - xenophonf 5y ago
      But the answer is right there, section 2, starting on page 12 of the linked paper. We're hackers. Autodidacticism is our creed. Research papers are our bread and butter. Why settle for speculation from the pseudonymous masses when a rich vein of well written analysis by reputable authors is one click away?
- nixpulvis 5y ago
  Skim until you are in the right section? Literally titled: "Section II - Mitigation of bitsquatting attacks"

simulate-me 5y ago

It depends on whether or not the client specifically requested, or is expecting, traffic over HTTPS. But yes, if the user's client requests encrypted traffic, the attacker will not be able to produce a valid certificate. This attack isn't that different than a MITM.

tedunangst 5y ago
Nothing prevents an attacker from getting a cert for snytimg.com or oslashdot.org.
- legalcorrection 5y ago
  That only helps the attacker if the error happened before reaching the DNS-specific path. If the error happens inside the DNS path, then the browser is still expecting to get a certificate for the correct website.
  - tedunangst 5y ago
    If the error happens inside the DNS path, the name in the answer won't match the name in the query. The browser is still expecting to get an answer for the hostname it sent.
    - deleted 5y ago
      [deleted]

legalcorrection 5y ago

Depends on where in the stack the error happened.