/top/
/new/
/best/
/ask/
/show/
/job/
^
slacker news
login
about
←back to thread
Getting ready to issue IP address certificates
(community.letsencrypt.org)
314 points
Bogdanp
| 4 comments |
25 Jun 25 16:21 UTC
|
HN request time: 1.911s
|
source
Show context
mocko
◴[
25 Jun 25 17:16 UTC
]
No.
44379696
[source]
▶
>>44379034 (OP)
#
I can see how this would work on a technical level but what's the intended use case?
replies(13):
>>44379710
#
>>44379735
#
>>44379778
#
>>44379786
#
>>44379885
#
>>44379946
#
>>44380155
#
>>44380377
#
>>44380579
#
>>44380856
#
>>44381151
#
>>44381389
#
>>44386646
#
BiteCode_dev
◴[
25 Jun 25 17:21 UTC
]
No.
44379735
[source]
▶
>>44379696
#
Static ip for self hosting at home
replies(2):
>>44380087
#
>>44381743
#
1.
politelemon
◴[
25 Jun 25 17:57 UTC
]
No.
44380087
[source]
▶
>>44379735
#
The validity is just 6 days, so I'd assume it's not for long lived use cases? Or am I misunderstanding something
replies(3):
>>44380113
#
>>44380153
#
>>44381993
#
ID:
GO
2.
◴[
25 Jun 25 18:00 UTC
]
No.
44380113
[source]
▶
>>44380087 (TP)
#
3.
meepmorp
◴[
25 Jun 25 18:03 UTC
]
No.
44380153
[source]
▶
>>44380087 (TP)
#
they're only for publicly accessible IP addresses, so they'd work the same as regular letsencrypt certs - get a new one when the old one expires.
4.
XorNot
◴[
25 Jun 25 21:29 UTC
]
No.
44381993
[source]
▶
>>44380087 (TP)
#
Certificate validity has no bearing on availability. It just keeps revocation lists short.
↑