tdtd · HackerTrans

2 lata temudiscuss

This is certainly true on Windows, where loaded DLLs share the base addresses across processes even with ASLR enabled, but is it the case on Linux, where ASLR forces randomization of .so base addresses per process, so relocations will make the data in their pages distinct? Or is it the case that on modern architectures with IP-relative addressing (like x64) that relocations are so uncommon that most library pages contain none?

tdtd

2 lata temudiscuss

The attacker doesn’t resign the DNS record with their own key, they just let the legitimately signed record though and use the IP address in that legitimate record themselves. If someone owns the network (or is an active MitM) they can control where IP addresses route to.

tdtd

2 lata temudiscuss

If the network’s owner was the one doing DNS redirects, couldn’t they just instead use the IP address in the DNSSEC-signed record themselves? I don’t think DNSSEC is a robust protection if you don’t trust the network you’re connected to.

tdtd

3 lata temudiscuss

The "te" transliteration for 茶 in Min Nan comes from the Pe̍h-ōe-jī romanization system (https://en.wikipedia.org/wiki/Pe%CC%8Dh-%C5%8De-j%C4%AB), which doesn't use the letter 'd' at all.

As was common for Chinese romanization systems from before the 20th century, it used 't' for unaspirated /t/ (which we would use use 'd' for today in systems like Pinyin for Mandarin or Peng'im for Teochew), and used 'th' for aspirated /tʰ/ (which we sould use 't' for today in systems like Pinyin or Peng'im).

This isn't an archaic miss transliteration, it's just an alternative transliteration strategy. In many languages that primarily use the latin alphabet, the phonemes associated with 't' and 'd' are /t/ and /d/, primarily distinguished by voice instead of aspiration (where aspiration is allophonic), so it's logical that the creators of earlier romanization systems focused on preserving that voice distinction, even if it's less common today for a variety of reasons.

comments