Trademark policy conformance verification

#1

I would like to add the ACME client I am actively maintaining https://github.com/bruncsak/letsencrypt.sh to the list of clients at https://letsencrypt.org/docs/client-options/#acme-v2-compatible-clients . There is a requirement not to infringe the trademark policy of Letsencrypt to do that. I am a technical and not a legal guy, so I am in trouble now. Could someone from Letsencrypt go through quickly on my repo and suggest modification if anything needed to be in accordance with Letsencrypt trademark policy, please?

#2

Hi @bruncsak,

Thanks for opening a thread. I’m not a legal person myself but I believe the only change required is renaming your client to something other than “letsencrypt”. I recommend choosing a name that emphasizes your project is an ACME client and so will likely work with other ACME CAs, not just Let’s Encrypt.

#3

Dear @cpu,

Thanks for the reply. The original upstream project was renamed from https://github.com/gheift/letsencrypt.sh to https://github.com/gheift/ght-acme.sh , probably due to https://github.com/gheift/ght-acme.sh/issues/35 . I could do the same on my fork too, but I do not know, is that a safe operation technically? Would that create dangling references, or not?

1 Like
#4

Yup! Looks like @josh filed that issue with the upstream project for the specific purpose of addressing the trademark policy conformance.

If you mean dangling Github references it won’t be a problem, Github will serve a redirect to the new project name. I can’t speak to whether there are additional application level concerns but from a Git and Github perspective it should be a safe operation.

2 Likes
#5

Dear @cpu,
I renamed my repository from bruncsak/letsencrypt.sh to bruncsak/ght-acme.sh .
Thanks a lot for your help.

3 Likes
#6

Glad to hear it. Happy to help!

1 Like