3 ms·

> be aware that these external names you're using for internal devices become a matter of public record this way Yes, I sometimes think about that, but have co

> be aware that these external names you're using for internal devices become a matter of public record this way Yes, I sometimes think about that, but have come to the conclusion that it's not likely to make any difference. If someone is trying to infiltrate my home network, then it's not going to really help them to know internal IP addresses as by the time they get to use them, they're already in.

qwertox 2y ago
You don't need to publish the IP addresses publicly if you use an internal DNS server. I think even Pi-hole could do this.
dspillett 2y ago
> If someone is trying to infiltrate my home network I don't think the publishing of host names was mentioned as a concern for small home networks, but more for larger organisations that might be subject to a coordinated break-in or simply have trade secrets¹² that might be hinted at by careless naming of resources. ---- [1] Their next big product/enhancement, as yet unannounced even within the company, for instance. [2] Hmm, checking what is recorded against one of DayJob's domains I see clues as to who some of our clients are. Not really a significant issue for security at all, but I know at least some of our contracts say we shouldn't openly talk about that we provide services to that client³ so I'll drop a message to the ISC to suggest we discuss if we need to care about the matter… [3] Though that is mostly in the form of not using their logos in our advertising and such.
- xena 2y ago
  That's why you have an internal domain that's not related to the company. Something like "packet-flinging.ninja". Everything's a tradeoff though.
  - deltaburnt 2y ago
    It seems really easy to associate a company with its internal domain though? Unless the company treats it as a secret only known between machines.
    - dspillett 2y ago
      > It seems really easy to associate a company with its internal domain though? Especially as people will talk about it as a “you'll never guess what…” when talking about places they work or have worked.
GoblinSlayer 2y ago
If your services work through http(s), they can be accessed from your browser.

qwertox 2y ago

You don't need to publish the IP addresses publicly if you use an internal DNS server. I think even Pi-hole could do this.

dspillett 2y ago

> If someone is trying to infiltrate my home network I don't think the publishing of host names was mentioned as a concern for small home networks, but more for larger organisations that might be subject to a coordinated break-in or simply have trade secrets¹² that might be hinted at by careless naming of resources. ---- [1] Their next big product/enhancement, as yet unannounced even within the company, for instance. [2] Hmm, checking what is recorded against one of DayJob's domains I see clues as to who some of our clients are. Not really a significant issue for security at all, but I know at least some of our contracts say we shouldn't openly talk about that we provide services to that client³ so I'll drop a message to the ISC to suggest we discuss if we need to care about the matter… [3] Though that is mostly in the form of not using their logos in our advertising and such.

xena 2y ago
That's why you have an internal domain that's not related to the company. Something like "packet-flinging.ninja". Everything's a tradeoff though.
- deltaburnt 2y ago
  It seems really easy to associate a company with its internal domain though? Unless the company treats it as a secret only known between machines.
  - dspillett 2y ago
    > It seems really easy to associate a company with its internal domain though? Especially as people will talk about it as a “you'll never guess what…” when talking about places they work or have worked.

GoblinSlayer 2y ago

If your services work through http(s), they can be accessed from your browser.