8000 Name conflict with paultag/minica · Issue #48 · jsha/minica · GitHub
[go: up one dir, main page]

Skip to content

Name conflict with paultag/minica #48

Open

Description

@JamesHagerman

Hello,

Currently, running apt install minica under Ubuntu installs a similar binary using the same name: https://github.com/paultag/minica

This was somewhat unexpected. It might be a good idea to include a note about the difference between the two projects in the README.md for others running into this issue.

Activity

  1. jsha commented on Oct 14, 2020

    @jsha
    Owner

    Thanks! I'd definitely take a PR to the README changing that.

    BTW I've seen an increased level of interest in the project recently - out of curiosity, was it posted somewhere?

  2. JamesHagerman commented on Oct 16, 2020

    @JamesHagerman
    Author

    Good to know! I don't know if I have enough context to provide a PR but I'll see what I can do.

    Maybe because it's way less work than using openssl directly? 🤣 Honestly, I'm not sure about the increase. I landed here because another developer used brew install minica in a project and I was trying to get it to work under Linux.

    On that note, it would be super helpful to provide an official Docker image. There are a good number of public images on Dockerhub (e.g. https://hub.docker.com/r/ryantk/minica) but without a Dockerfile in this repo, those images are rather questionable.

    Sadly, I don't know enough about Go to put one together without digging my heels in. 🤦

  3. pnc commented on Dec 30, 2020

    @pnc

    So, excitingly, Debian packages the (unmaintained upstream) paultag version. I think the major user-facing differences are that that version accepts CN/SNI names as unflagged arguments.

    @jsha Would you be open to a patch that made it possible to do minica example.com www.example.com for compatibility, and @tianon is it at all possible to make this version the new maintained upstream of the existing package? (One is MIT and one is Apache, unfortunately.)

  4. tianon commented on Dec 30, 2020

    @tianon

    cc @paultag, who I think is in a better position to opine on this

  5. paultag commented on Dec 30, 2020

    @paultag

    Hah, i wasn't tracking this, nor that the other minica was unmaintained. Happy to consolidate given scarce namespace.

  6. jsha commented on Dec 30, 2020

    @jsha
    Owner

    Also happy to consolidate, and I think the change y 804A ou propose, to take hostnames as args rather than flags, should probably be fine. There's another piece of functionality that's probably different: my minica reads its root from minica.pem and minica-key.pem in the current directory, or generates them if they don't exist. I don't know how @paultag's minica does it.

    I'm also totally happy to relicense if it makes things easier. I don't have a preference between MIT and Apache.

  7. paultag commented on Jan 1, 2021

    @paultag

    I'm also happy to relicense between MIT/Expat and Apache 2.0, those are both fine to me. Maybe a fallback if they privkey is missing? We can also try and ship a migration script in the package and suggest using it as long as nothing will get damaged by running it in place. After this is done, I'm happy to archive my repo.

  8. bennydubois commented on Mar 19, 2021

    @bennydubois

    "BTW I've seen an increased level of interest in the project recently - out of curiosity, was it posted somewhere?"

    For my part, I came straight here from a link on let's encrypt referencing your project
    https://letsencrypt.org/docs/certificates-for-localhost/

  9. pnc commented on Mar 19, 2021

    @pnc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0