On Thu, Feb 19, 2009 at 11:41:36PM +0800, loody wrote:
> I have a homework to take aes for encryption and description.
This list is not not a substitute for teacher or teaching assistant
office hours.
--
Viktor.
__
Open
loody wrote:
Is there sample code or ducument I can realize how to use EVP?
On MacOSX, the normal man pages document the API for EVP*, I assume it
is the same on the other unix environments.
"apropos EVP" should get you started.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptograp
2009/2/18 Ger Hobbelt :
> On Tue, Feb 17, 2009 at 11:30 PM, Victor Duchovni
> wrote:
>>> Why are you trying to enforce the idea of cryptography as a black box,
>>> rather than something that people should learn about?
>>
>> Because in amost all cases that's exactly the right advice.
>
> Well, yes,
On Tue, Feb 17, 2009 at 11:30 PM, Victor Duchovni
wrote:
>> Why are you trying to enforce the idea of cryptography as a black box,
>> rather than something that people should learn about?
>
> Because in amost all cases that's exactly the right advice.
Well, yes, about the 'almost' you are spot on
> Victor Duchovni wrote:
> > Because in amost all cases that's exactly the right advice.
> >
> > The cryptography learning that is sufficient and desirable is from books
> > such as "Applied Cryptography" which cover protocols and algorithms
> > at a high level. Studying the implementation or cre
Victor Duchovni wrote:
Because in amost all cases that's exactly the right advice.
The cryptography learning that is sufficient and desirable is from books
such as "Applied Cryptography" which cover protocols and algorithms
at a high level. Studying the implementation or creating ones own
imple
On Tue, Feb 17, 2009 at 02:08:43PM -0800, Kyle Hamilton wrote:
> > You are asking the wrong questions. Why are you trying to reverse-engineer
> > the AES implementation? Why not just use it via the EVP interface?
>
> My guess is that he's trying to understand an actual in-world AES
> implementati
Hello,
owner-openssl-us...@openssl.org wrote on 02/17/2009 03:20:38 PM:
> 2009/2/17 Victor Duchovni :
> > On Mon, Feb 16, 2009 at 01:48:54PM +0800, loody wrote:
> >
> >> Dear all:
> >> I want to realize aes, so I trace enc_main in enc.c.
> >> But I find there are a lot call back functions such th
On Tue, Feb 17, 2009 at 8:57 AM, Victor Duchovni
wrote:
> On Tue, Feb 17, 2009 at 10:20:38PM +0800, loody wrote:
>
>> The round# is set according to the bits we pass to AES_set_encrypt_key.
>> And Nk*round# keys are also produced well in it.
>> But how about Nb, the number of column in state?
>> (
On Tue, Feb 17, 2009 at 10:20:38PM +0800, loody wrote:
> The round# is set according to the bits we pass to AES_set_encrypt_key.
> And Nk*round# keys are also produced well in it.
> But how about Nb, the number of column in state?
> (in 128, 192 and 256 bits block plaintext, the Nb, column# of sta
2009/2/17 Victor Duchovni :
> On Mon, Feb 16, 2009 at 01:48:54PM +0800, loody wrote:
>
>> Dear all:
>> I want to realize aes, so I trace enc_main in enc.c.
>> But I find there are a lot call back functions such that I spend more
>> time on tracing these call back functions than understanding aes
>>
On Mon, Feb 16, 2009 at 01:48:54PM +0800, loody wrote:
> Dear all:
> I want to realize aes, so I trace enc_main in enc.c.
> But I find there are a lot call back functions such that I spend more
> time on tracing these call back functions than understanding aes
> algorithm.
>
> I have studied the
Dear all:
I want to realize aes, so I trace enc_main in enc.c.
But I find there are a lot call back functions such that I spend more
time on tracing these call back functions than understanding aes
algorithm.
I have studied the aes flow chart on the wiki,
http://en.wikipedia.org/wiki/Advanced_Encr
13 matches
Mail list logo
