Skip to content
Commits on Feb 9, 2012
  1. Merge pull request #2 from bithin/patch-1

    committed
    StringIO was imported twice.
  2. @bithinalangot
Commits on Mar 22, 2010
Commits on Jul 13, 2009
  1. Build a dylib on Darwin

    R. Tyler Ballance committed
Commits on Jul 10, 2009
  1. Add the ability to compile libseccure with 'slow' random, i.e. /dev/r…

    R. Tyler Ballance committed
    …andom instead of /dev/urandom
  2. Update licensing on the seccure code, moving to LGPL thanks to B. Poe…

    R. Tyler Ballance committed
    …ttering
Commits on Jul 8, 2009
  1. Remove NULL returns in non-exception error conditions

    R. Tyler Ballance committed
  2. Make sure the state and keypair objects are freed post-iterations as …

    R. Tyler Ballance committed
    …well
  3. Run loops over reading and encrypting the same sizes of data

    R. Tyler Ballance committed
  4. Compare memory regions, just to be safe

    R. Tyler Ballance committed
  5. Add a small test binary to encrypt random data *a lot*

    R. Tyler Ballance committed
Commits on Jul 7, 2009
  1. Prevent accidental attempts to re-initialize the secure memory pool

    R. Tyler Ballance committed
    Also disabling the termination of the secure memory pool, once terminated
    the memory pool cannot be revived for the life of the process.
  2. Author info

    R. Tyler Ballance committed
  3. Add some basic README junk

    R. Tyler Ballance committed
  4. Move the markdwon readme to reStructured text

    R. Tyler Ballance committed
  5. Add basic Sphinx-based documentation

    R. Tyler Ballance committed
  6. Compile, *then* commit. Stupid semi-colons

    R. Tyler Ballance committed
  7. Missing jumps to return early from the function

    R. Tyler Ballance committed
  8. Free the decrypted data object in the test as well

    R. Tyler Ballance committed
  9. Ensure we're not inadvertantly returning a half-allocated ECC_Data st…

    R. Tyler Ballance committed
    …ruct
  10. Make sure we're relying on the C API for the string length instead of…

    R. Tyler Ballance committed
    … len() which will only read to a NULL byte
  11. Add a couple error condition tests

    R. Tyler Ballance committed
Commits on Jul 6, 2009
  1. Add a simplistic GC test case

    R. Tyler Ballance committed
  2. Reduce the number of loops, no need to run as many now that debugging…

    R. Tyler Ballance committed
    … is over
  3. Add a wee bit more documentation

    R. Tyler Ballance committed
  4. Add some malloc() error checking

    R. Tyler Ballance committed
  5. Fix a bad cast caught with clang(1)

    R. Tyler Ballance committed
  6. Add a *lot* more loops to find more leaks

    R. Tyler Ballance committed
  7. Forcefully end the decrypted data string with a null byte

    R. Tyler Ballance committed
    Lest we have allocated a segment in non-nullbyted (yes, nullbyted)
    memory, and have garbage trailing off the end of the string.
  8. Set data member to NULL to make sure we can conditionalize against it…

    R. Tyler Ballance committed
    … later
  9. Print out the errno that's running around (for debug)

    R. Tyler Ballance committed
  10. Fix a leak underneath seccure's decompress_string() function (used he…

    R. Tyler Ballance committed
    …avily by ecc_encrypt())
    
    The gist of what's happening, is that dezerialize_mpi() gives us an (N) MPI which
    an affine_point struct's x,y are then assertained with. This N MPI was not
    being properly released after P.x and P.y were calculated, resulting in libseccure
    exhausting libgcrypt's secure memory pool.
    
    Valgrind results (valgrind --tool=memcheck --leak-check=full --show-reachable=yes ./test_integration -p /integration/keygen_encryptsalot):
    
    Before:
    	LEAK SUMMARY:
    	definitely lost: 7,208 bytes in 360 blocks.
    	indirectly lost: 17,363 bytes in 179 blocks.
    	possibly lost: 992 bytes in 2 blocks.
    	still reachable: 16,042 bytes in 85 blocks.
    	suppressed: 0 bytes in 0 blocks.
    
    After:
    	LEAK SUMMARY:
    	definitely lost: 3,232 bytes in 201 blocks.
    	indirectly lost: 19,628 bytes in 208 blocks.
    	possibly lost: 992 bytes in 2 blocks.
    	still reachable: 15,447 bytes in 67 blocks.
    	suppressed: 0 bytes in 0 blocks.
Something went wrong with that request. Please try again.