upgrade pycryptodomex to 3.6.3

this is safe as long as the virtualenv has been fully regenerated
and/or the leftover buggy file python3.4/site-packages/Cryptodome/Util/_cpuid.cpython-34m.so
has been deleted
see Legrandin/pycryptodome#178

requirements.in

@@ -50,8 +50,6 @@ Flask-Login
 social-auth-app-flask-sqlalchemy
 social-auth-app-flask
 social-auth-core[openidconnect]
-# stick to pycryptodomex 3.4.6 as 3.6.3 breaks production
-pycryptodomex==3.4.6
 
 # Unit tests.
 nose

requirements.txt

@@ -63,7 +63,7 @@ pip-tools==2.0.2
 prompt-toolkit==1.0.15    # via ipython
 ptyprocess==0.6.0         # via pexpect
 pycallgraph==1.0.1
-pycryptodomex==3.4.6
+pycryptodomex==3.6.3      # via pyjwkest
 pygments==2.2.0           # via ipython
 pyjwkest==1.4.0           # via social-auth-core
 pyjwt==1.5.2              # via social-auth-core