Lex-2008
Joined 7 years ago
Joined 7 years ago
I meant to say that CAA record can also specify account, or at least Let’s Encrypt docs mention it[1]. So unless attacker has access to victim's account - they can't get a cert (unless they can hijack dns, too).
[1]: https://letsencrypt.org/docs/caa/#the-accounturi-parameter
Moreover, with dns-01, DNS provider can issue fake certificates - unless you self-host DNS - in which case, only your DNS registrar can... and a government.
Good point, I forgot about that! But then CAA record might help, I guess, if you specify your accounturi?
I'm not sure how CAs deal with situations when a domain has several authoritative DNS servers, but not all of them respond with expected reply. Would it would be a good idea for CAs to ask *all* authoritative DNS servers and require a coherent answer from them?
Alternatively, merchants can give users more cashback points for using their preferred way of paying. Not sure how this flies with payment processor rules, but I've seen it in the wild.
So I assume that if they were accepting more expensive cards, they might've increase the price of the $100.16 product for me, to offset their costs.
And yes, I also heard that payment processors have rules that require merchants to have the same price no matter what payment processor (or cash) customer will choose.
https://man.archlinux.org/man/wl-copy.1
(i was also interested :)
Another way I've seen elsewhere is to use a human-language explanation of how to build email address, something like this: "To get my email address, combine my first name (John) with my birth year (2000), separated by dash (-), and add email provider (@gmail.com)".
i.e. something like this: CREATE INDEX idx_events_type ON events(json_extract(data, '$.type'))?
i guess caveat here is that slight change in json path syntax (can't think of any right now) can cause SQLite to not use this index, while in case of explicitly specified Virtual Generated Columns you're guaranteed to use the index.