Attestation signature verification failed (testproj) about django-u2f HOT 4 CLOSED

That's strange; I have never seen that error. Is it reproducible every time?

from django-u2f.

Ah, I think I tracked it down. It was my problem, nothing to do with your project. I set up a fresh Ubuntu Server 14.04 VM and the test project worked perfectly. After doing some searching online, it looked like the version of OpenSSL I have on my system might have been the issue, and compiling the most recent version of that (and recompiling M2Crypto) fixed my issues. (I'm on a Mac, running OS X 10.9 Mavericks.)

For anyone else who runs into this issue while trying to run this (or any other M2Crypto-related issues) on Mac, here's what I did to solve it. (Note: I tried the homebrew version of openssl, but for some reason it wouldn't work at all with M2Crypto, so I uninstalled it and did the following instead.)

I downloaded the latest OpenSSL and compiled it manually:

# Build 32-bit version
./config --prefix=$HOME
make && make install
# Build 64-bit version (need both versions for M2Crypto)
make clean && make dclean
./Configure darwin64-x86_64-cc --prefix=$HOME/ssl-x64
make && make install

Then I built "fat" libraries that combined the 32-bit and 64-bit versions:

lipo -create lib/libcrypto.a ssl-x64/lib/libcrypto.a -output lib/libcrypto.a
lipo -create lib/libssl.a ssl-x64/lib/libssl.a -output lib/libssl.a

Then I downloaded, compiled, and installed M2Crypto manually:

python setup.py build build_ext --openssl=$HOME
python setup.py install build_ext --openssl=$HOME

Then, when I followed the rest of your instructions (pip install -e ., etc.), and fired up the server, everything worked. (The reason it worked when I ran it "manually" before is that I was running u2f_server.py on a Linux box while the simple HTML was on my local machine, to avoid port conflicts...which is an obvious mistake in hindsight.)

Sources: I cobbled together this solution from here and here.

from django-u2f.

Great, glad you figured it out. Looks like M2Crypto could use some better error reporting? It seems like you can't tell the difference between an invalid certificate and an invalid install of the package?

from django-u2f.

Something like that... Maybe the issue had to do with the CAs that were installed, or something? Or maybe some defaults changed? (Just guessing here.) On top of that, I'm not completely sure which version of OpenSSL was getting used by default: which openssl returns the version bundled with Postgres.app, so it may well have been that one getting used rather than the one installed with OS X 10.9.

from django-u2f.