From owner-freebsd-questions@freebsd.org Sat Oct 24 07:58:56 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38536A1D608 for ; Sat, 24 Oct 2015 07:58:56 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DE8FA144E for ; Sat, 24 Oct 2015 07:58:55 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1Zptiu-002rDI-T5>; Sat, 24 Oct 2015 09:58:44 +0200 Received: from f052150151.adsl.alicedsl.de ([78.52.150.151] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1Zptiu-003mZG-L6>; Sat, 24 Oct 2015 09:58:44 +0200 Date: Sat, 24 Oct 2015 09:58:39 +0200 From: "O. Hartmann" To: "Michael B. Eichorn" Cc: Erich Dollansky , freebsd-questions Subject: Re: replace uname -a informational string Message-ID: <20151024095839.2da2cb97.ohartman@zedat.fu-berlin.de> In-Reply-To: <1445658972.13154.44.camel@michaeleichorn.com> References: <20151023090805.5484ce9b@freyja.zeit4.iv.bundesimmobilien.de> <1445622325.1169.29.camel@michaeleichorn.com> <20151023225424.49220466.ohartman@zedat.fu-berlin.de> <20151024080936.0ff26783@X220.alogt.com> <1445658972.13154.44.camel@michaeleichorn.com> Organization: FU Berlin X-Mailer: Claws Mail 3.13.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/gbI3SmYpI9o0MaKG.Z2xNQu"; protocol="application/pgp-signature" X-Originating-IP: 78.52.150.151 X-ZEDAT-Hint: A X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Oct 2015 07:58:56 -0000 --Sig_/gbI3SmYpI9o0MaKG.Z2xNQu Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 23 Oct 2015 23:56:12 -0400 "Michael B. Eichorn" schrieb: > On Sat, 2015-10-24 at 08:09 +0800, Erich Dollansky wrote: > > Hi, > >=20 > > On Fri, 23 Oct 2015 22:54:24 +0200 > > "O. Hartmann" wrote: > > =20 > > > Am Fri, 23 Oct 2015 13:45:25 -0400 > > > "Michael B. Eichorn" schrieb: > > >=20 > > >=20 > > > First of all: Thank you very much for your concerns and answers. > > > =20 > > > > On Fri, 2015-10-23 at 09:08 +0200, O. Hartmann wrote: =20 > > > > > For security purposes, I need to replace the informations given > > > > > by > > > > > "uname -a" > > > > > to hode the kernel build system, name et cetera. =20 > > > >=20 > > > > I presume you intendend 'hide' here? > > > >=20 > > > > If you want to scrub a binaries of _all_ information about the > > > > building system this is a problem Debian is actively working on > > > > called 'reproducible builds' but is not possible today. > > > >=20 > > > > https://reproducible.debian.net > > > >=20 > > > > If you want to hide the hostname, why not just build with a > > > > different hostname set? =20 > > >=20 > > > Because it is not only the hostname, uname reveals the target host, > > > date and OS version. > > >=20 > > > In our case, the image ist built on a dedicated host for a security > > > appliabce based on NanoBSD and I'd like to hide the OS type, the OS > > > name, the build box' name and the build date.=20 > > > =20 > > why not replace uname at the source level then? > >=20 > > Erich =20 >=20 > That wouldn't hide the information in any substantial way. Uname is > basically an abstraction of a subset of sysctls. As such, the information > is integral to the kernel itself. Uname is just one of many tools that > can be used to display this information. >=20 > Fundamentally the kernel itself needs to be changed not uname. I'm well aware of that fact. At many places, the build-process sets variabl= es from the outside world while building binaries and kernel and since I build everythi= ng from scratch, I intend to manipulate those variables - if possible. --Sig_/gbI3SmYpI9o0MaKG.Z2xNQu Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWKzovAAoJEOgBcD7A/5N8dXUH/3iElYg/ZDi6vE5yqItk9KaN Y7wxyUwvEhU6nQouIrR8MCuhzig6ksSG5tGBv5FRH8s2u1UYjxb0ZR7rjCH6K+Qg /tuHNqgPjjhCZnDYDfsY9blGrj9ajlMjhtsEtcW9YhfNf0tcKdBNx2EGKyq86SYr +ejw0LIk9ggdijJIPuS4jug5lhRIhU0MQFvUgA+eujljKCWloYPeQEGhWsEYhGpH LEH4/PbOlZM8+/63vkNxqDYXBFb3R6/DYfXAvXOihv3p1sdvpbaMehdjhxU9mtIo KFHyAmQ7BdZr6UTxqjBBEvKWXk9yB3AG1w6VQo8XvyHOU276wlgT15hzer6Zi5A= =a7rV -----END PGP SIGNATURE----- --Sig_/gbI3SmYpI9o0MaKG.Z2xNQu--