liboqs-python
liboqs-python copied to clipboard
open-quantum-safe
PyPI library entry
Would be good to have an entry in PyPI to make this more accessible
We thought about that, and at this point don't want to add this to PyPI, because we don't want people to start using it for production code yet.
Closing issue. Won't consider a PyPI entry until NIST begins making recommendations on algorithms.
Maybe the time has come to reconsider this issue? As NIST now stated at least some finalists.
Also it would take care of the copycat who are publishing liboqs packages even-though not being affiliated.
Also it would take care of the copycat who are publishing liboqs packages even-though not being affiliated.
What do you mean by "not being affiliated"? I personally wouldn't mind anyone taking open responsibility for maintaining a distribution as the OQS team arguably cannot do that, also due to its size. The "do not use this code productively" disclaimer has not been removed from the repo, in my eyes primarily as the OQS team did not author or vet the standardized core crypto routines beyond running some generic tests and also cannot give commitments to provide any specific distro support -- and surely not on the breadth of platforms supported by Python. Right now, this would IMO have to come from anyone willing to create distributions/package things up (or sell this level of support).
Also it would take care of the copycat who are publishing liboqs packages even-though not being affiliated.
What do you mean by "not being affiliated"? I personally wouldn't mind anyone taking open responsibility for maintaining a distribution as the OQS team arguably cannot do that, also due to its size.
Getting more involvement in the project would be great. But I think it would still be desirable for anyone publishing a liboqs-python package to do so via this repository and integrated with our maintainers and processes.
@Ceddicedced im the guy that copied and released liboqs to pip under the name of "liboqs". Probably you were talking about me. I thought I left email to contact me in readme but I didnt. I looked at the state of the project and major problem of compiling libraries is now gone and I dont feel like maintaining my clone. I have deleted it and you may now take over the name if you want to
Would you be able to transfer the project to my account? Username dstebila.
Hi again @FunDan3, are you still able to transfer the liboqs pip name to us?
@dstebila I deleted the project, and to be honest I have no Idea how to move it. Sorry for late response. Please explain me how to transfer the name to you and I will do so
@ryjones Is there a Linux Foundation / PQCA organization account on PyPI that should be the owner of the liboqs-package? Should an OQS organization be created on PyPI?
Are we able to move forward on this? #120 brings it to our attention again.
we could publish as oqs-bot using the openquantumsafe namespace, I think, but I don't have any levers to pull to make pypi go faster.