New package: Keygen v0.1.0 #15941
New package: Keygen v0.1.0 #15941
Conversation
JuliaRegistrator
commented
Jun 6, 2020
JuliaRegistrator
commented
- Registering package: Keygen
- Repository: https://github.com/aminya/Keygen.jl
- Created by: @aminya
- Version: v0.1.0
- Commit: 7c0fe130fbf41d9aebadd28a2e944e5001a066ce
- Reviewed by: @aminya
- Reference: JuliaCrypto/OpenSSH.jl@7c0fe13#commitcomment-39708299
UUID: d86bbb82-37b3-4007-a431-d95a92b013b0 Repo: https://github.com/aminya/Keygen.jl.git Tree: d24c76ca2a1f853dfc28309b76d074aff286740a Registrator tree SHA: 58e84c9733c0606ca53349dbce519209d8a8402b
|
Your Since you are registering a new package, please make sure that you have read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1 If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text |
|
Should this be part of a larger OpenSSH.jl package rather than in a special Keygen.jl package? Note that we now have OpenSSH in Yggdrasil. |
|
I think we can have an But also have an application layer that generates the correct key for different tasks. For example for Documenter, GitHub secretes, etc. This could be called I am not picky about the name. 🤔 |
|
I think using our BB binaries and consolidating efforts into an OpenSSH.jl package perhaps in the JuliaCrypto org would be the right way. If you are up for it, let's get it moved and renamed and updated to use the BB binaries. I can invite your as a JuliaCrypto owner. |
|
Sure. I will close this until we have a working OpenSSH.jl. Then we can talk about the application layer. |
|
I transferred the repository, but I lost the write access I guess. I cannot change the repo name or see the projects tab. |
|
@ViralBShah Can you give @aminya the appropriate access? |
|
I didn't change the access. I just promoted @aminya to owner. See if that does the trick. |
