From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17564 invoked by alias); 5 Jun 2010 18:52:51 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 15091 Received: (qmail 16095 invoked from network); 5 Jun 2010 18:52:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 Received-SPF: pass (ns1.primenet.com.au: SPF record at benizi.com designates 64.130.10.15 as permitted sender) Date: Sat, 5 Jun 2010 14:52:33 -0400 (EDT) From: "Benjamin R. Haskell" To: =?UTF-8?Q?Fran=C3=A7ois_Revol?= cc: zsh-users@zsh.org Subject: Re: $HOST on OS X In-Reply-To: Message-ID: References: <16277B2D-B9C7-4B56-A74C-AE6266BDA089@chemistry.ucsc.edu> User-Agent: Alpine 2.01 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463810530-1832456478-1275763954=:5029" ---1463810530-1832456478-1275763954=:5029 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Sat, 5 Jun 2010, François Revol wrote: > Le 5 juin 2010 à 17:45, Benjamin R. Haskell a écrit : > > > So, maybe there was some script you/someone ran that set > > HOST=e3191.c.akamaiedge.net, for convenience. (For uploading things > > to Akamai's CDN, maybe? Seems a bit of a stretch.) > > No it's only a bad habit of OSX to update hostname depending on the > joined network, I often noticed this when using wifi or an unusual > LAN. So when you open a Terminal at that point it shows this in the > prompt and other stuff... If that's the case, I might expect a hostname like pool-68-162-167-80.pitt.east.verizon.net (something from a DHCP pool assigned by an ISP). Not something on akamaiedge.net, which is certainly not an ISP. Unless someone's playing weird games with routing via Amazon-EC2. (More likely, that one in particular seems like some upstream DNS misconfiguration, akin to the bad PTR record for an RFC 1918 address in this post[1].) Regardless, OS X is far from the only O/S that'll update hostnames when you join a network. And especially on a laptop, it often makes sense. For instance, after associating with a university's wireless network, your host probably has a different name assigned to it. Why would it be bad to update it? > IMO it's a security risk though... What part, and how so? -- Best, Ben [1] http://www.techsupportforum.com/networking-forum/networking-support/407794-strange-hostname-private-ip.html ---1463810530-1832456478-1275763954=:5029--