tgseclib/tests/Unit/Crypt/AES/OpenSSLTest.php

<?php
/**
 * @author    Andreas Fischer <bantu@phpbb.com>
 * @copyright MMXIII Andreas Fischer
 * @license   http://www.opensource.org/licenses/mit-license.html  MIT License
 */

class Unit_Crypt_AES_OpenSSLTest extends Unit_Crypt_AES_TestCase
{
    protected function setUp()
    {
        $this->engine = CRYPT_ENGINE_OPENSSL;
    }
}
Crypt: add OpenSSL support aside from the addition of OpenSSL support a few other changes have been included: - setEngine(), as added by petrich, is depricated (not that it was ever in trunk to begin with) it has been replaced with isValidEngine() and setPreferredEngine(). - replace _generate_xor() with increment_str() _increment_str() had extra functionality that wasn't being used. ie. it could concatenate multiple successive string increments to one another automatically. but not only was that functionality not used - it also made the function less versatile. _increment_str() can be used more easily for iterative brute forcing (for example) - rename Crypt_Base::_stringShift to Crypt_Base::_string_shift (for consistency) - more expansive unit test coverage 2014-11-29 07:39:21 -06:00			`<?php`
			`/**`
			`* @author Andreas Fischer <bantu@phpbb.com>`
			`* @copyright MMXIII Andreas Fischer`
			`* @license http://www.opensource.org/licenses/mit-license.html MIT License`
			`*/`

			`class Unit_Crypt_AES_OpenSSLTest extends Unit_Crypt_AES_TestCase`
			`{`
			`protected function setUp()`
			`{`
Tests: update unit tests to use CRYPT_ENGINE_* instead of CRYPT_MODE_* 2014-12-13 14:34:48 -06:00			`$this->engine = CRYPT_ENGINE_OPENSSL;`
Crypt: add OpenSSL support aside from the addition of OpenSSL support a few other changes have been included: - setEngine(), as added by petrich, is depricated (not that it was ever in trunk to begin with) it has been replaced with isValidEngine() and setPreferredEngine(). - replace _generate_xor() with increment_str() _increment_str() had extra functionality that wasn't being used. ie. it could concatenate multiple successive string increments to one another automatically. but not only was that functionality not used - it also made the function less versatile. _increment_str() can be used more easily for iterative brute forcing (for example) - rename Crypt_Base::_stringShift to Crypt_Base::_string_shift (for consistency) - more expansive unit test coverage 2014-11-29 07:39:21 -06:00			`}`
			`}`