3 ms·

You can't get a certificate for localhost, but you can get one for foldinglocalhost.com and resolve that to 127.0.0.1.

• unilynx 8y ago
  That requires you to also ship the private key to end users, and your certificate will be revoked once the CA discovers it
  • euroclydon 8y ago
    No, you can just install a self-signed unique cert for each machine.
    • aaaaaaaaaab 8y ago
      But then why do you need the DNS/hosts file hack? You can issue a self-signed cert to localhost/127.0.0.1, put it in the user’s trust store and call it a day.
    • SahAssar 8y ago
      Asking users to install a CA or cert is not a good or scalable solution.
      • vertex-four 8y ago
        Since when does a desktop application need to ask the user anything to install a cert programmatically? Enforced desktop sandboxing hasn't really taken off.
• randomfool 8y ago
  Not according to https://bugs.chromium.org/p/chromium/issues/detail?id=378566#c41 https://bugs.chromium.org/p/chromium/issues/detail?id=378566...
  • bmm6o 8y ago
    That bug is stuck on not breaking exactly this kind of behavior. They cite Dropbox in that thread (though I haven't read the followups yet), who has www.dropboxlocalhost.com resolving to 127.0.0.1. It sounds like Spotify does something similar.
• amaccuish 8y ago
  Not on my network, since I ban dns rebinding