It's up to you to decide if it's okay that you send a server provider (in this case late.sh) a bunch of your public keys which he could for example use to probe other servers to see if you have access to them.

Everyone has different opsec.

  ~/.ssh/id_ecdsa.pub
  ~/.ssh/id_ecdsa_sk.pub
  ~/.ssh/id_ed25519.pub
  ~/.ssh/id_ed25519_sk.pub
  ~/.ssh/id_xmss.pub
  ~/.ssh/id_dsa.pub

At the very bottom of the website they give you a command that would not leak your public keys.

`ssh-keygen -t ed25519 -f ~/.ssh/late_throwaway && ssh -o IdentitiesOnly=yes -i ~/.ssh/late_throwaway late.sh`

this would only send the late_throwaway public key

Once you leak your public key it could be used to check if another server recognizes that leaked public key.

Comments URL: https://news.ycombinator.com/item?id=47672764

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46383718

Points: 3

# Comments: 2

Am I the one who is crazy and nitpicking here?

[1] https://deep.43z.one

Comments URL: https://news.ycombinator.com/item?id=45062073

Points: 5

# Comments: 0

  # UMASK is the default umask value for pam_umask and is used by
  # useradd and newusers to set the mode of the new home directories.
  # 022 is the "historical" value in Debian for UMASK
  # 027, or even 077, could be considered better for privacy
  # There is no One True Answer here : each sysadmin must make up his/her
  # mind.

Would it really be so hard to make that switch to a more privacy focused umask?