Originally created by @philkunz on GitHub (Jul 21, 2016).
Since the account key is the only component that is written by all parallel processes requesting a domain initially when not present, it would be cool if one could request it synchronously without having to specify a domain.
(the sync/async handling is handled by the calling script of cause and has nothing to do with letsencrypt.sh itself)
Originally created by @philkunz on GitHub (Jul 21, 2016).
Since the account key is the only component that is written by all parallel processes requesting a domain initially when not present, it would be cool if one could request it synchronously without having to specify a domain.
(the sync/async handling is handled by the calling script of cause and has nothing to do with letsencrypt.sh itself)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @philkunz on GitHub (Jul 21, 2016).
Since the account key is the only component that is written by all parallel processes requesting a domain initially when not present, it would be cool if one could request it synchronously without having to specify a domain.
(the sync/async handling is handled by the calling script of cause and has nothing to do with letsencrypt.sh itself)
@lukas2511 commented on GitHub (Jan 29, 2017):
I just implemented
--registerin6a32f20e00