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: <20080516095529.GS3279@freenet.de>
Date:	Fri, 16 May 2008 11:55:29 +0200
From:	Michelle Konzack <linux4michelle@...ay-dogan.net>
To:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: Hardware designt to prevent Damages... [WAS: [patch 23/37] i2c-piix4: Blacklist two mainboards]

Hello Dick,

Thank you for the answer...

Even if I use several times an I2C current Sink/Source converter
from Dallas/Maxim the security is done by Hardware design...

So nobody will burn my Atmel ARM1176.


Thanks, Greetings and nice Day
    Michelle Konzack
    Systemadministrator
    24V Electronic Engineer
    Tamay Dogan Network
    Debian GNU/Linux Consultant



Am 2008-05-15 13:57:35, schrieb linux-os (Dick Johnson):
> Many (perhaps all) modern computers perform the final building
> process upon power up. This usually involves writing bits to
> some gate-arrays and performing hardware initializations with
> registers that disappear once the machine starts acting like
> a real PC. I wrote a BIOS for the AMD SC520 and most of the
> code involved "building" the machine. However, there was an
> unwritten rule that nothing could be done to hurt anything.
> 
> There is only one CPU that I know of, the 56000 DSP, that
> can be configured with insane instructions that will hurt
> it.
> 
> Nowadays, more power adjustment stuff is being put where
> it shouldn't be. A bad bit somewhere may cause a power
> supply to go out of regulation and burn out something
> (like the CPU). If you find something like this, the
> machine vendor should replace the machine and/or the
> machine should be black-listed. We can't have computers
> in which a random event such as an alpha-particle upset
> can actually hurt anything.
> 
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.22.1 on an i686 machine (5588.29 BogoMips).
> My book : http://www.AbominableFirebug.com/
------------------------ END OF REPLIED MESSAGE ------------------------


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
+49/177/9351947    50, rue de Soultz         MSN LinuxMichi
+33/6/61925193     67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Download attachment "signature.pgp" of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ