Virtex 5 bitstream encryption

Hello !
I would like to know the frequency used by Xilinx (Virtex 5) to
decrypt bitstream before configuration .
The decrypter is it slow with small area ? fast with big area ?
unfortunately it's not documented by xilinx .

Thank u for help

On Aug 27, 7:51*am, bamboutcha9...@hotmail.com wrote:
> Hello !
> *I would like to know the frequency used by Xilinx (Virtex 5) to
> decrypt bitstream before configuration .
> *The decrypter is it slow with small area ? fast with big area ?
> unfortunately it's not documented by xilinx .
>
> Thank u for help

Do you mean ENcrypt when you wrote DEcrypt ?
Peter Alfke

On 27 août, 17:09, Peter Alfke wrote:
> On Aug 27, 7:51*am, bamboutcha9...@hotmail.com wrote:
>
> > Hello !
> > *I would like to know the frequency used by Xilinx (Virtex 5) to
> > decrypt bitstream before configuration .
> > *The decrypter is it slow with small area ? fast with big area ?
> > unfortunately it's not documented by xilinx .
>
> > Thank u for help
>
> Do you mean ENcrypt when you wrote DEcrypt ?
> Peter Alfke

Peter ,
i mean "decrypt ", in fact encrypted bitstream is sent from Eprom to
Fpga to be decrypted then configured . i want to know more about this
decrypter . which AES 256 decryption architecture is used by xilinx
( area , throughput , ...) .

bamboutcha9999-at-hotmail.com wrote:
> Hello !
> I would like to know the frequency used by Xilinx (Virtex 5) to
> decrypt bitstream before configuration .
> The decrypter is it slow with small area ? fast with big area ?
> unfortunately it's not documented by xilinx .
>
> Thank u for help

It decrypts at the same rate as the configuration clock. This could be
anywhere from KHz to the maximum of 100 MHz as specified in the data sheet.

Ed McGettigan
--
Xilinx Inc.

On 27 août, 18:29, Ed McGettigan wrote:
> bamboutcha9...@hotmail.com wrote:
> > Hello !
> > *I would like to know the frequency used by Xilinx (Virtex 5) to
> > decrypt bitstream before configuration .
> > *The decrypter is it slow with small area ? fast with big area ?
> > unfortunately it's not documented by xilinx .
>
> > Thank u for help
>
> It decrypts at the same rate as the configuration clock. *This could be
> anywhere from KHz to the maximum of 100 MHz as specified in the data sheet.
>
> Ed McGettigan
> --
> Xilinx Inc.


Ed ,
thank for you answer .
The rate of config clk is fixed by the user ( from 2Mhz to 60Mhz ) so
i did not understand by "anywhere from KHz to the maximum of 100
MHz" , moreover with my
encrypted bitstream (Eprom => FPGA) i couldn't run over 42 Mhz .
why ?
What i want to know is the throughput of the decrypter (AES 256 CBC) ,
how many cycles takes this architecture used by Xilinx ? is it Safe
at 100% against attacks ( timing , fault attack , side channel
attack ....) ?
thank u

bamboutcha9999-at-hotmail.com wrote:
> On 27 août, 18:29, Ed McGettigan wrote:
>> bamboutcha9...@hotmail.com wrote:
>>> Hello !
>>> I would like to know the frequency used by Xilinx (Virtex 5) to
>>> decrypt bitstream before configuration .
>>> The decrypter is it slow with small area ? fast with big area ?
>>> unfortunately it's not documented by xilinx .
>>> Thank u for help
>> It decrypts at the same rate as the configuration clock. This could be
>> anywhere from KHz to the maximum of 100 MHz as specified in the data sheet.
>>
>> Ed McGettigan
>> --
>> Xilinx Inc.
>
>
> Ed ,
> thank for you answer .
> The rate of config clk is fixed by the user ( from 2Mhz to 60Mhz ) so
> i did not understand by "anywhere from KHz to the maximum of 100
> MHz" ,

2 MHz to 60 MHz falls within the window that I stated of KHz to 100 MHz.

> moreover with my
> encrypted bitstream (Eprom => FPGA) i couldn't run over 42 Mhz .
> why ?

Likely because of the timing relationships created by the EPROM. You
should review the data sheet for the EPROM to verify the maximum
frequency of operation in the mode that you are using it.

> What i want to know is the throughput of the decrypter (AES 256 CBC) ,
> how many cycles takes this architecture used by Xilinx ?

The decrypter input-to-output is 1:1, so there are no stalls required
for the input bitstream. I don't know what the latency is of the actual
block as it has no impact on the configuration sequence.

> is it Safe
> at 100% against attacks ( timing , fault attack , side channel
> attack ....) ?

Austin Lesea has said once or twice in this newsgroup that the NSA has
approved it as secure and we know of no one that has broken it.

Ed McGettigan
--
Xilinx Inc.