0

In some of our environments we would like to use the TimestampServer option when signing so we don't have to worry about re-signing certificates. The issue we have is that in some environments we don't allow connections in or out on 80, only 443 and the TimestampServer parameter is expecting the url format to be http. Is there something I'm missing?

Improve this question
3
  • To add, we're using our own internal CA if that makes a difference.
    – SteamerJ
    Dec 7, 2018 at 16:01
  • Did you tried https TimestampServer? Please edit the question and add an error message, if any.
    – JosefZ
    Dec 7, 2018 at 18:47
  • I did but the error says it expects http for the URL format. I'm asking it it appears it's not supported but wanted to see if anyone else had ideas
    – SteamerJ
    Dec 7, 2018 at 18:48

1 Answer 1

Reset to default
0

Looks like the Timestamp Server protocol requires HTTP so HTTPS is not possible

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .