Bitcoin Forum
November 03, 2024, 05:45:30 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: HW/ASIC Builders - Need for PW protected HW/ASIC?  (Read 825 times)
rampone (OP)
Sr. Member
****
Offline Offline

Activity: 339
Merit: 250


dafq is goin on


View Profile
April 03, 2013, 12:21:17 PM
 #1

Hello,

i could explain it long, but time is btc right now so short story:

with asic hardware in a box, which produces you a gigantomanic amount of money in short time, would it not be advised, that in the miner FW is a "password" burnt in, so the device in itself is useless, might it be stolen on the parcel way (rogue adress redirection@DHL, some1 intercepting the delivery guy in front of door, badly paid parcel worker sees the miner package and says: TY byebye...etc...). The password would be transmitted via email to the real end consumer.

Just a thought: I would like/prefer Miners that are useless without additional authenticification/unlocking...


not like eldentyrell and tricone FW with a special signcryption server externally, "unlocking"/auth done locally in miner soft. maybe also switch off protection if you want to.

Sorry if this thought is already in a fred....

Idea cause by sgravina thread: https://bitcointalk.org/index.php?topic=163795.0

http://virwox.com - Bitcoins via CCard, Skrill, paysafe, paypal & SEPA
Convert your bitcoin into spendable fiat money in less than 2 days. Poker Players use this method to avoid "unnecessary trouble" with the country they live in ... PM me for details. +1:naz86,b4nana,tinua,smart1986,fhh
Soros Shorts
Donator
Legendary
*
Offline Offline

Activity: 1617
Merit: 1012



View Profile
April 03, 2013, 01:05:19 PM
 #2

Probably difficult for something as open as the Avalon.  Any customer-unique password stored in the WR703N could be defeated by a reflash.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!