full-disclosure - Re: Ip address and mac address hardcoded

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJVRA1QN4dKo86Jt4rpEApjer+Aw7=pSttfN=QqWpLa1C39dsw@mail.gmail.com>
Date: Sat, 16 Nov 2013 15:18:20 -0800
From: coderman <coderman@...il.com>
To: mramelie@...hmail.com
Cc: Full Disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: Ip address and mac address hardcoded

On Sat, Nov 16, 2013 at 3:59 AM,  <mramelie@...hmail.com> wrote:
> ... I come acrosss an ip address and a
> mac address hardcoded in some libraries of a firmware for a vendor. Why
> should it be there this kind of hardcode?

i've seen this done for testing purposes, when running hardware
through a quality check harness which needs such static configuration.

what is the IP? (publicly route-able or internal only?)
what is the MAC OUI prefix? (valid vendor or some arbitrary unallocated ident?)

answering these questions would help identify test vs. backdoor intent...

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/