lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802010229250.4864@fbirervta.pbzchgretzou.qr>
Date:	Fri, 1 Feb 2008 02:37:08 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Justin Banks <justin.banks@...bone.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: how to tell i386 from x86-64 kernel


don't strip Ccs, thanks. (and try not to tofu either.)

On Jan 31 2008 17:01, Justin Banks wrote:
>
>uname -a will tell you, though.

No. uname is generally not a reliable source to tell you the bitness (or 
more precisely, the arch). It may even happen that you cannot find out 
at all if access permissions are set 'correctly'.
You may find ELF64 files flying around in the filesystem, and while that 
is a strong indication of a 64-bit kernel being running, it is not a 
definite Yes.


02:31 ccgmbh:~ > uname -a
Linux ccgmbh 2.6.23.10-ccj62-regular #1 SMP 2007/10/26 14:17:15 UTC i686 
athlon i386 GNU/Linux

02:32 ccgmbh:~ > file `which uname`
/bin/uname: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for 
GNU/Linux 2.6.4, dynamically linked (uses shared libs), stripped
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ