MarkAssPandi (@MarkAssPandi)

@cR0w @Sirs0ri @iaintshootinmis But this repo also includes a warning about NOT putting it in a DNS without doing it properly?
This thread feels like it's trying to misrepresent what tailscale is stating:
"tailcat address is normally a secret: knowing it is what lets a client connect. A DNS TXT record is not secret. It is public, world-readable, and actively scanned. Publishing an address in DNS hands it to everyone on the internet, so the server behind it must authenticate clients by something other than knowledge of the address: restrict the tunnel to known client keys with tailcat serve --allow=..., or, for SSH, require public keys with tailcat serve --ssh-authorized-keys=... ssh. Never publish the address of a no-auth-ssh server (or any other server that trusts whoever connects): that is a shell on your machine, published in a TXT record. See Protected SSH server over DNS for the safe setup."
They say directly to not put it there without proper authentication.
Unless I'm misreading what is being talked about here?