Reenable redefined tests.

The test suite contains tests that are disabled because they have the same name
as other tests. Renaming them enables them again.

PKCS1_OAEP_Tests.testEncryptDecrypt1 is updated to work with the new interface
of PKCS1_OAEP.
Return a byte string if format is set to OpenSSH.

RSA.exportKey claims to return a byte string, so really return one.
Raise a ValueError as documented.

Also add a test case for it.
Merge remote-tracking branch 'sebastinas/reenable-tests'
Fixes to Counter module documentation

The example code contained special character '\x00' that is directly
shown by epydoc.

Counter module was not included in __init__ of Crypto.Util
Examples for DES and DES3 were inverted
Using MODE_CBC instead of MODE_ECB in README example

ECB mode has known disadvantages and while the use of it could be
intended, I think it would be a good idea to have a 'stronger' mode in
the example.

Thus, I adopted the example in the README to make use of MODE_CBC
instead of MODE_ECB.
AES was 1 byte too long in example
Add test vectors for ARC4

Test vectors are taken from RFC 6229.
All tests pass.
Added ARC4-drop[n] cipher
Run test_negative_number_roundtrip_mpzToLongObj_longObjToMPZ only if _fastmath
is available.
Store result of rabinMillerTest in an int.

rabinMillerTest returns an int but getStrongPrime stores the result in an
unsigned long int which makes the tests in line 1545 and 1621 useless.
Add tests for error propagation in _fastmath

Affects isPrime and getStrongPrime.

See https://github.com/dlitz/pycrypto/pull/23 ("Store result of
rabinMillerTest in an int.") for the bug report.
Merge remote-tracking branch 'sebastinas/clang' into error-propagation-fixes

Pull request: https://github.com/dlitz/pycrypto/pull/23
_fastmath: Propagate errors raised in rabinMillerTest
Merge branch 'error-propagation-fixes'
Fix typo in comment
_fastmath: Use default false_positive_prob is one is not specified

This should never happen, but the behaviour is saner if it does.
_fastmath: Replace 'long int' with 'long' to avoid confusion

"long int" is equivalent to "long" in C, and it's harder to misread it as
"int" this way.
setup.py: Add more compiler warnings and fix unsigned-signed comparisons