Conversation

Notices

1.  (mint@ryona.agency)'s status on Sunday, 25-Jun-2023 06:35:30 JST 
   Yeah, maybe writing an acme client in pure sh wasn't the best idea.
   https://github.com/acmesh-official/acme.sh/issues/4659
   •  (mint@ryona.agency)'s status on Sunday, 25-Jun-2023 07:02:12 JST 

     in reply to

     • Nekobit
     @neko The issue seems to be with a singular CA with jury-rigged ACME server and is fixed at least the base script. That CA immediately closed down after that for some reason. Can't say if it can't be exploited with dozens of hooks for DNS hosters, though.
   • Nekobit (neko@ryona.agency)'s status on Sunday, 25-Jun-2023 07:02:13 JST Nekobit

     in reply to
     @mint fuck, i used this on my old server. ive had more success with openbsd's acme-client though
      likes this.
   • gray (gray@ryona.agency)'s status on Sunday, 25-Jun-2023 07:08:52 JST gray

     in reply to

     • Nekobit
     @mint @neko used acme for my instance too. I neglected it and the carts expired though
      likes this.
   • nya~ (neganeko@ryona.agency)'s status on Sunday, 25-Jun-2023 17:59:20 JST nya~

     in reply to

     • Nekobit
     @mint @neko :laugh: what is even going on here
     
     > used exec to get better error messages
     
     the fuck
     
     I guess the only redeeming detail is that hopefully CAs are trustworthy so hopefully none of them would take advantage of this RCE vuln so hopefully no actual exploits happened in practice
     
     ... or HiCA sold an exploit service. who knows
     screenshot_2023-06-25_acmesh_hi…
     screenshot_2023-06-25_acmesh_ex…
      likes this.