Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-22 Thread Deb Cooley
There is sufficient interest to adopt this draft. Thank you, Deb On Fri, Jun 9, 2023 at 5:06 PM Seo Suchan wrote: > for CAA mechanism for tor, I'm don't think acme working group is right > place to talk about it: as they effect non-acme CA that sign certificate > for onion, shouldn't it need

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-09 Thread Seo Suchan
for CAA mechanism for tor, I'm don't think acme working group is right place to talk about it: as they effect non-acme CA that sign certificate for onion, shouldn't it need to be handled on lamps subject (as there is where CAA rfc was discussed) 2023-06-10 오전 1:55에 Aaron Gable 이(가) 쓴 글: Hi

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-09 Thread Aaron Gable
Hi all, I support the draft for adoption. Specifically, I think it's a good thing to standardize the onion-csr-01 challenge type. I have two classes of comments that I look forward to discussing in-depth after adoption: 1) Obviously it's valuable for this draft to standardize a method that is

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-09 Thread Q Misell
Having discussed HiCA with some friends it seems they're being very naughty indeed and abusing what appears to be an RCE in ACME.sh to get their validation done?! https://github.com/acmesh-official/acme.sh/issues/4659 -- Any statements contained in this email are

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-09 Thread Seo Suchan
@mholt on github found they they are inject RCE onto acme.sh. be aware. https://github.com/acmesh-official/acme.sh/issues/4659 2023-06-09 오후 4:55에 Q Misell 이(가) 쓴 글: Hi Amir, TIL about HiCA. They do seem like a weird bunch! I note they only allow ACME.sh as an ACME client and forbid every

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-09 Thread Q Misell
Hi Amir, TIL about HiCA. They do seem like a weird bunch! I note they only allow ACME.sh as an ACME client and forbid every other client in their EULA ( https://www1.hi.cn/en/docs/getting-started/acme.sh-installation). They also have some interesting ideas about patents surrounding ACME (

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-08 Thread Amir Omidi
Wrong URL, apologies: https://www1.hi.cn/hica-vs-letsencrypt/ On Thu, Jun 8, 2023 at 15:08 Amir Omidi wrote: > I support the draft as it is for adoption. I’m also curious if > https://www.hi.cn/hica-vs-letsencrypt/ is potentially using the draft as > well for their onion support? > > On Sun,

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-08 Thread Amir Omidi
I support the draft as it is for adoption. I’m also curious if https://www.hi.cn/hica-vs-letsencrypt/ is potentially using the draft as well for their onion support? On Sun, Jun 4, 2023 at 08:07 Stephen Farrell wrote: > > Hiya, > > On 04/06/2023 12:06, Deb Cooley wrote: > > This will be a two

Re: [Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-04 Thread Stephen Farrell
Hiya, On 04/06/2023 12:06, Deb Cooley wrote: This will be a two week call for adoption ending on 16 June. Please speak up either for or against adopting this draft. I had a read of the draft. I support adoption. I'm not sure I understand the security of the challenge schemes

[Acme] Call for adoption of draft-misell-acme-onion-02

2023-06-04 Thread Deb Cooley
This will be a two week call for adoption ending on 16 June. Please speak up either for or against adopting this draft. Thanks, Deb ___ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme