-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failure on OSX Lion python27 from ports #5
Comments
made the directory /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pysodium/pycache/ problem solved |
howdy, i just released a new version of pysodium, that moved away from cffi to ctypes, so this issue should never come up again. could you try with a fresh install of pysodium/pbp to confirm this? you can keep your key/config directories of course. see #6 |
oops after ssudo pip uninstall pysodium/pbp and then a suso pip reinstall MacBook-Pro:~ gwen$ sudo pip uninstall pysodium Requirement already satisfied (use --upgrade to upgrade): cffi in /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages (from pbp) Requirement already satisfied (use --upgrade to upgrade): SecureString in /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages (from pbp)
Running setup.py install for pysodium Successfully installed pbp pysodium gwens-MacBook-Pro:~ gwen$ Any suggestions? |
It can't seem to open libsodium.so.6. can it find libsodium.so? What if you provide a symlink from libsodium.so to libsodium.so.6? |
dunno about freebsd, does it need ldconfig? |
i was told to try /etc/rc.d/ldconfig start |
no ldconfig on OSX an the ctypes cant find lib issue seems to be documented here and file on my libsodium by hand or by macports shows same arch as the python interpreter.. and this was NOT happening before this last change stef...and the migration to cytpes seems to have activated this bug(not that I even understand except to know that its a change in how the lib is called... for python) also tried it in both locations with appropriate changes of LD_LIBRARY_CONFIG as well as path to change the interpreter used from macports to osx native
|
apparently libs on macosx are called something else from .so: https://stackoverflow.com/questions/11554355/mac-os-x-lion-python-ctype-cdll-error-lib-so-6-image-not-found sodium = ctypes.cdll.LoadLibrary("libsodium.dylib") |
working... ie that resolved the osx case |
uh stef? (=Q(P6b=tbfHtx;n>V(bn~Tgun}3aaajKbEfLt{2_cFHyBPIk10b&vqLE1)V4l&-m?w86%$$hNKOwW}G2DN&dbRI4DyV;V}@<mIeSFsfXh@l^9Ox?-=-M(F2yZ*-T$^@OA?$6I3UTt{Wc as a result which is a far cry from my present pcp key for curve p25519: 1l0$WoM5C8z=yeZG7?$]f^Uu8.g>4rf#t^6mfW9(rr910 and to tell the truth after decades of enduring the pgp format and monstrosity that pgp keys became will this be possible? |
hmm, not directly. tom now also uses separate keys for encryption and signing, that means double the key size, however in pbp these two are considered "short-term", and there's a long-term signing key. so in pbp there's gonna be 3*32 bytes. |
hmm do these need to be represented in an external presentation format to allow someone to encrypt to moi?
|
for encryption not, for signing yes. for replacing short term keys, while having a trust anchor in the long term secret key, yes. |
and thus the thrust of my inquiry.. I still want a 32 byte external encryption key format for printing on business cards etc.(yes some of us still use same) .. having this would allow one to boot strap into longer key representations and go dark more easily in any conversation whether initiated offline or online. |
for that i would recommend to publish the long-term signing key, which you can then use to issue new encryption keys to your peers when needed. |
and a signing key wont encrypt the initial conversation I want my first conversation to be private when bootstrapping from a business card into an encrypted online conversation.. |
so is it possible to have an option to export an encryption key alone or encryption and/or signing key |
or am I missing something and its(the option I am requesting ) already there? btw thanx for the fast response on the osx issue. |
you need different keys for signing and encrypting. |
yes I understand that.. but for a Person possessing a business card with an encryption key to contact me NO signature is necessary when I hand said business card in person to the recipient. I just want the ability to extract each keytype into its own printable representation, ie the above is merely one example, I can think of more in tradecraft where signatures are NOT necessary for secure comms just an encryption key. and while someone MAY be willing to type 32 bytes in to be able to reach me 64 is OUT of the question and 96 keystrokes beyond the pale. I will be testing next to export/import encryption and signature keys into datamatrix,QR and PDF -417 encodings for optical pickup, encryption + sig key is valuable for that use case and MITM attacks ARE of concern so sigs become important. |
I am NOT a python programmer but I did install libsodium python 2.7 virtualenv py-dev and libffi from ports and keep getting the following
pbp
Traceback (most recent call last):
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pbp", line 9, in
load_entry_point('pbp==0.2', 'console_scripts', 'pbp')()
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources.py", line 352, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources.py", line 2307, in load_entry_point
return ep.load()
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources.py", line 2021, in load
entry = import(self.module_name, globals(),globals(), ['name'])
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pbp/main.py", line 5, in
import publickey
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pbp/publickey.py", line 2, in
import pysodium as nacl, scrypt # external dependencies
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pysodium/init.py", line 30, in
from pysodium import sodium
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pysodium/sodium.py", line 130, in
lib = ffi.verify("#include <sodium.h>", libraries=["sodium"])
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/cffi/api.py", line 339, in verify
lib = self.verifier.load_library()
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/cffi/verifier.py", line 73, in load_library
self._write_source()
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/cffi/verifier.py", line 125, in _write_source
file = open(self.sourcefilename, 'w')
IOError: [Errno 2] No such file or directory: '/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pysodium/pycache/_cffi__x6f20fc6x6947e85f.c'
tried uninstalling and installing pbp via pip a couple of times(as well as libffi (via ports))
pyffi on the OSX 10.7 platform would seem to require python 3(I am stuck at python 2.7 for GNURADIO concerns)..
HELP? Suggestions?(and this is why I prefer delivery of security/crypto utils in c as the implementation vehicle tends to be more widely supported. python,ruby,java,what have you tends to be a bit more fragile with regards to the run time environment due to the additional layers of software infrastructure(and greatly increated local attack surface(host based attacks)) while warding off other classes of attacks... depends on where you want to draw your line in the sand.. and given I am very comfortable with c and the object code/linkages/machine code produced and NOT so comfy with python(as evidenced :)
ps will attempt openbsd amd64 5.1 next
The text was updated successfully, but these errors were encountered: