How to protect my Virtex5 design without battery?
in [FPGA]
|
Prev: fsm coding question
Next: Seeking some advice
From: vcar on 30 Dec 2009 04:02 On 12ÔÂ29ÈÕ, ÏÂÎç4ʱ29·Ö, Frank Buss <f...(a)frank-buss.de> wrote: > vcar wrote: > > For certainreasons, I could not use battery on my board, so the > > Virtex5 bitstream encryptioncould not be used. In this situation, what > > could I do to protect my design on areasonable level? > > I don't know the answers to your questions, but I guess an attacker could > at least just desolder the XCF16P and reading it like the FPGA does when > booting, so even the read protection bit of the flash is useless. If you > want to secure your device, I would use something like the DS2401. This > provides a unique id. You could save this in the flash and compare it from > the FPGA with the chip. The chip is available in packages which looks like > a capacitor or diode: > > http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=DS24.... > > I've written some VHDL code for reading the one-wire id: > > http://www.frank-buss.de/vhdl/spartan3e.html > > (see the DS2432 ROM id reader in the zip file) > > -- > Frank Buss, f...(a)frank-buss.dehttp://www.frank-buss.de,http://www.it4-systems.de Comparing to DS2401, DS28E01 or DS2432 is more applicable. If I use these chips, need I use BSCAN_VIRTEX5 + ICAP_VIRTEX5 to monitor JTAG activities?
From: Nico Coesel on 30 Dec 2009 06:32 vcar <hitsx(a)163.com> wrote: >On 12=D4=C229=C8=D5, =CF=C2=CE=E76=CA=B112=B7=D6, glen herrmannsfeldt <g...= >@ugcs.caltech.edu> wrote: >> Frank Buss <f...(a)frank-buss.de> wrote: >> > vcar wrote: >> >> For certainreasons, I could not use battery on my board, so the >> >> Virtex5 bitstream encryptioncould not be used. In this situation, what >> >> could I do to protect my design on areasonable level? >> >> Protecting against exact clones is difficult. In many cases, decoding >> the bits back to logic is hard enough not to worry about that. >> >> > I don't know the answers to your questions, but I guess an attacker cou= >ld >> > at least just desolder the XCF16P and reading it like the FPGA does whe= >n >> > booting, so even the read protection bit of the flash is useless. If yo= >u >> > want to secure your device, I would use something like the DS2401. This >> > provides a unique id. You could save this in the flash and compare it f= >rom >> > the FPGA with the chip. The chip is available in packages which looks l= >ike >> > a capacitor or diode: >> >> As long as they don't read this newsgroup and know what to look for... >> >> -- glen > >Hi, glen. >My point is to protect my board from cloning, so the attacker do not >need to decoding bit stream back to logic. Once they obtain the bit >stream, they can produce my board themselves. >I could not protect the PCB from cloning, so I have to do something on >my bit stream. Otherwise it is very easy to copy my board. In that case you'll need to add a microcontroller which does part of the job. -- Failure does not prove something is impossible, failure simply indicates you are not using the right tools... nico(a)nctdevpuntnl (punt=.) --------------------------------------------------------------
From: Ed McGettigan on 31 Dec 2009 15:45 On Dec 29, 6:42 pm, vcar <hi...(a)163.com> wrote: > On 12ÔÂ29ÈÕ, ÏÂÎç6ʱ12·Ö, glen herrmannsfeldt <g....(a)ugcs.caltech.edu> wrote: > > > > > > > Frank Buss <f...(a)frank-buss.de> wrote: > > > vcar wrote: > > >> For certainreasons, I could not use battery on my board, so the > > >> Virtex5 bitstream encryptioncould not be used. In this situation, what > > >> could I do to protect my design on areasonable level? > > > Protecting against exact clones is difficult. In many cases, decoding > > the bits back to logic is hard enough not to worry about that. > > > > I don't know the answers to your questions, but I guess an attacker could > > > at least just desolder the XCF16P and reading it like the FPGA does when > > > booting, so even the read protection bit of the flash is useless. If you > > > want to secure your device, I would use something like the DS2401. This > > > provides a unique id. You could save this in the flash and compare it from > > > the FPGA with the chip. The chip is available in packages which looks like > > > a capacitor or diode: > > > As long as they don't read this newsgroup and know what to look for... > > > -- glen > > Hi, glen. > My point is to protect my board from cloning, so the attacker do not > need to decoding bit stream back to logic. Once they obtain the bit > stream, they can produce my board themselves. > I could not protect the PCB from cloning, so I have to do something on > my bit stream. Otherwise it is very easy to copy my board.- Hide quoted text - > > - Show quoted text - If the bitstream is not using the AES encryption then there is very little that you can do to prevent the entire board from being cloned as anyone that has one of your original boards can easily extract the data from the PROM. There are some alternatives, but they aren't as secure. See Xilinx Whitepager WP266 and Application Note XAPP780 Ed McGettigan -- Xilinx Inc.
From: Frank Buss on 30 Dec 2009 07:34 vcar wrote: > Comparing to DS2401, DS28E01 or DS2432 is more applicable. You are right, the DS2432 looks interesting with the SHA1 hash function. But I couldn't find it at Digikey and you have to register at Maxim to just get the price for it, so maybe a small PIC (which has program read protection) is better. > If I use these chips, need I use BSCAN_VIRTEX5 + ICAP_VIRTEX5 to > monitor JTAG activities? I don't think this is needed, because an attacker could desolder the flash anyway and simulate a FPGA to read the bitstream, or use a logic analyzer for recording the FPGA boot process. -- Frank Buss, fb(a)frank-buss.de http://www.frank-buss.de, http://www.it4-systems.de
From: vcar on 4 Jan 2010 22:37
On 1ÔÂ1ÈÕ, ÉÏÎç4ʱ45·Ö, Ed McGettigan <ed.mcgetti....(a)xilinx.com> wrote: > On Dec 29, 6:42 pm, vcar <hi...(a)163.com> wrote: > > > > > > > On 12ÔÂ29ÈÕ, ÏÂÎç6ʱ12·Ö, glen herrmannsfeldt <g...(a)ugcs.caltech.edu> wrote: > > > > Frank Buss <f...(a)frank-buss.de> wrote: > > > > vcar wrote: > > > >> For certainreasons, I could not use battery on my board, so the > > > >> Virtex5 bitstream encryptioncould not be used. In this situation, what > > > >> could I do to protect my design on areasonable level? > > > > Protecting against exact clones is difficult. In many cases, decoding > > > the bits back to logic is hard enough not to worry about that. > > > > > I don't know the answers to your questions, but I guess an attacker could > > > > at least just desolder the XCF16P and reading it like the FPGA does when > > > > booting, so even the read protection bit of the flash is useless. If you > > > > want to secure your device, I would use something like the DS2401. This > > > > provides a unique id. You could save this in the flash and compare it from > > > > the FPGA with the chip. The chip is available in packages which looks like > > > > a capacitor or diode: > > > > As long as they don't read this newsgroup and know what to look for.... > > > > -- glen > > > Hi, glen. > > My point is to protect my board from cloning, so the attacker do not > > need to decoding bit stream back to logic. Once they obtain the bit > > stream, they can produce my board themselves. > > I could not protect the PCB from cloning, so I have to do something on > > my bit stream. Otherwise it is very easy to copy my board.- Hide quoted text - > > > - Show quoted text - > > If the bitstream is not using the AES encryption then there is very > little that you can do to prevent the entire board from being cloned > as anyone that has one of your original boards can easily extract the > data from the PROM. > > There are some alternatives, but they aren't as secure. See Xilinx > Whitepager WP266 and Application Note XAPP780 > > Ed McGettigan > -- > Xilinx Inc. Yeah, Now I decide to adopt DS2432 way. |