Shachar Shemesh wrote:
> Milton Calnek wrote:
>>
>>   On the last call to aes_key::encrypt_block(), size is less than 16,
>> for some reason
>> AES_cbc_encrypt() has a seg fault when size is not the block size.
>>
>>   
> There are two options. The first is that rsyncrypto relies on openssl to
> pad the size, or it does so itself. Off the top of my head, I find it

I'll agree with you here... rsyncrpto passes a block of the proper size
to AES_cbc_encrypt(). The problem I see is that we are reading the bytes read
and passing that a the size of the block... when in fact the block is a fixed
size.

I haven't actually read the buffer.get() yet, so I'm not entirely sure
about what I just wrote.



Yea: I have 0.9.8g repackaged.

-- 
Milton Calnek BSc, A/Slt(Ret.)
mil...@calnek.com
306-382-3657


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Rsyncrypto-devel mailing list
Rsyncrypto-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel

Reply via email to