[tahoe-dev] [tahoe-lafs] #406: end-to-end encoding self-test

[tahoe-lafs]

#406: end-to-end encoding self-test
---------------------------+------------------------------------------------
 Reporter:  zooko          |           Owner:  zandr
     Type:  defect         |          Status:  new  
 Priority:  major          |       Milestone:  1.4.1
Component:  code-encoding  |         Version:  1.0.0
 Keywords:                 |   Launchpad_bug:       
---------------------------+------------------------------------------------
Changes (by zooko):

  * milestone:  1.4.0 => 1.4.1


Comment:

 Some tests on Zandr's lenny-armel box do indeed fail, such as
 {{{allmydata.test.test_system.SystemTest.test_upload_and_download_random_key}}}.
 See the buildbot results: http://allmydata.org/buildbot/builders/Zandr
 %20Lenny-armel/builds/37/steps/test/logs/stdio .  However, these are
 failing because encrypting a string and then decrypting the ciphertext
 doesn't yield the original string.  A subtler bug (and one that we've had
 before in pycryptopp) is when encrypting the string and decrypting the
 ciphertext does yield the original string, but only when you use the same
 (buggy) code for both encryption and decryption.  This ticket is to add a
 "test vector", for example a fixed ciphertext, computed with a known-good
 implementation of AES and then hardcoded into the test file as a string
 literal, and assert that when you decrypt that fixed ciphertext you get
 the correct plaintext.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/406#comment:12>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid