Originally created by @belliash on GitHub (Aug 6, 2017).
Actually --signcsr outputs certificate to stdout and --out parameter is not used.
Please implement ability to specify a location with output ceritificate file.
Originally created by @belliash on GitHub (Aug 6, 2017).
Actually --signcsr outputs certificate to stdout and --out parameter is not used.
Please implement ability to specify a location with output ceritificate file.
Why is it not a solution? Write it out to a temporary file, then check to make sure it's a valid cert (and not empty or an error message). If it is a valid cert, move it into the correct location and do whatever else is necessary.
@txr13 commented on GitHub (Aug 7, 2017):
Why is it not a solution? Write it out to a temporary file, then check to make sure it's a valid cert (and not empty or an error message). If it is a valid cert, move it into the correct location and do whatever else is necessary.
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 @belliash on GitHub (Aug 6, 2017).
Actually --signcsr outputs certificate to stdout and --out parameter is not used.
Please implement ability to specify a location with output ceritificate file.
@lukas2511 commented on GitHub (Aug 6, 2017):
Just use
dehydrated --signcsr /path/to/cert.csr > cert.pem, no need for a parameter.@belliash commented on GitHub (Aug 7, 2017):
This is not a solution, because on any error this would overwrite valid certificate with empty file.
@txr13 commented on GitHub (Aug 7, 2017):
Why is it not a solution? Write it out to a temporary file, then check to make sure it's a valid cert (and not empty or an error message). If it is a valid cert, move it into the correct location and do whatever else is necessary.