Current Hostname Practice Considered Harmful
draft-huitema-privsec-harmfulname-01
| Document | Type |
Expired Internet-Draft
(intarea WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Huitema , Dave Thaler | ||
| Last updated | 2016-03-12 (Latest revision 2015-09-09) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Giving a hostname to your computer and publishing it as you roam from network to hot spot is the Internet equivalent of walking around with a name tag affixed to your lapel. The practice can significantly compromise your privacy, and should stop. There are several possible remedies, such as fixing a variety of protocols or avoiding disclosing a hostname at all. This document studies another possible remedy, which is to replace the static hostnames by frequently changing randomized values. This idea obviously needs more work.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)