2:05 a.m.
I’ve enabled HTTPS for BV after a bit of a fight with the DNS entries. I’m planning to
enforce HTTPS only in a few days.
Have all of our GH pages hosted properties moved to HTTPS?
What about the other properties?
Emmanuel
3:06 a.m.
Excellent, thanks a lot! Do you have a link to instructions you followed?
Would like to do the same for another site of mine.
2018-06-16 9:05 GMT+02:00 Emmanuel Bernard <emmanuel(a)hibernate.org>:
I’ve enabled HTTPS for BV after a bit of a fight with the DNS
entries. I’m
planning to enforce HTTPS only in a few days.
Have all of our GH pages hosted properties moved to HTTPS?
What about the other properties?
Emmanuel
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
11:58 a.m.
https://blog.github.com/2018-05-01-github-pages-custom-domains-https/
update your DNS records to the new IPs,
Wait for propagation
And like Guillaume said, disable GH pages generation and reenable to trigger the move.
Emmanuel
On 16 Jun 2018, at 10:06, Gunnar Morling <gunnar(a)hibernate.org>
wrote:
Excellent, thanks a lot! Do you have a link to instructions you followed? Would like to
do the same for another site of mine.
2018-06-16 9:05 GMT+02:00 Emmanuel Bernard <emmanuel(a)hibernate.org>:
> I’ve enabled HTTPS for BV after a bit of a fight with the DNS entries. I’m planning
to enforce HTTPS only in a few days.
>
> Have all of our GH pages hosted properties moved to HTTPS?
> What about the other properties?
>
> Emmanuel
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
9:20 a.m.
Hi,
On Sat, Jun 16, 2018 at 9:08 AM Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
Have all of our GH pages hosted properties moved to HTTPS?
What about the other properties?
A month ago or so, I moved the hibernate.org DNS to the SSL enabled GitHub
hosts and enabled SSL (had to disable then reenable the website to trigger
the certificate generation).
The issue is that hibernate.org uses a JSON feed from in.relation.to and
thus requires in.relation.to to be served on HTTPS too (otherwise, the news
simply don't appear). So I haven't enforced HTTPS for now.
in.relation.to is a bit special as it's not hosted on GitHub but directly
on our CI (you can have only one website per organization on GH). Sanne
told me he started the work on getting in.relation.to on HTTPS but got
stuck somehow with the certificates. He will probably reply with the
details.
I concur it would be high time to move all our website to HTTPS so ready to
spend some cycle on it if any help is needed.
One thing we could do that would simplify a lot of things is moving
in.relation.to to its own organization and have the website on GH. It
wouldn't be too much work and would solve the issue once and for all and
get our web infrastructure consistent.
Thoughts on this idea?
--
Guillaume
12:01 p.m.
Let’s wait quickly for Sanne’s feedback on why he was having certificate issues. My
experience with let’s encrypt has been stellar so far (httpd).
On 16 Jun 2018, at 16:20, Guillaume Smet
<guillaume.smet(a)gmail.com> wrote:
One thing we could do that would simplify a lot of things is moving in.relation.to to its
own organization and have the website on GH. It wouldn't be too much work and would
solve the issue once and for all and get our web infrastructure consistent.
Thoughts on this idea?
10:49 a.m.
On Sat, 16 Jun 2018 at 18:51, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
Let’s wait quickly for Sanne’s feedback on why he was having certificate issues. My
experience with let’s encrypt has been stellar so far (httpd).
I was experimenting with "let's encrypt" but then you told me that I
wasn't allowed to use that service.
So if that's no longer true I can resume my experiments? I don't
remember the details of the issues I had exactly; there was something
related with using an incompatible httpd version.
> On 16 Jun 2018, at 16:20, Guillaume Smet <guillaume.smet(a)gmail.com> wrote:
>
> One thing we could do that would simplify a lot of things is moving in.relation.to
to its own organization and have the website on GH. It wouldn't be too much work and
would solve the issue once and for all and get our web infrastructure consistent.
>
> Thoughts on this idea?
I'm understanding GH now offers a
I'm still hoping to move our javadocs as well after we move the
websites though, so not sure if that's worth it as we'll always have
some
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
9:13 a.m.
On Mon, 18 Jun 2018 at 21:48, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
> On 18 Jun 2018, at 17:49, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>
> I was experimenting with "let's encrypt" but then you told me that I
> wasn't allowed to use that service.
I don’t remember saying that. Knowing me I surely gave you a reason :)
Yes, you did :)
10:31 a.m.
On Tue 18-06-19 15:13, Sanne Grinovero wrote:
On Mon, 18 Jun 2018 at 21:48, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
>
>
>
> > On 18 Jun 2018, at 17:49, Sanne Grinovero <sanne(a)hibernate.org> wrote:
> >
> > I was experimenting with "let's encrypt" but then you told me that
I
> > wasn't allowed to use that service.
>
> I don’t remember saying that. Knowing me I surely gave you a reason :)
Yes, you did :)
What was it?
10:36 a.m.
On Tue, 19 Jun 2018 at 16:32, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
On Tue 18-06-19 15:13, Sanne Grinovero wrote:
>On Mon, 18 Jun 2018 at 21:48, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
>>
>>
>>
>> > On 18 Jun 2018, at 17:49, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
>> >
>> > I was experimenting with "let's encrypt" but then you told me
that I
>> > wasn't allowed to use that service.
>>
>> I don’t remember saying that. Knowing me I surely gave you a reason :)
>
>Yes, you did :)
What was it?
Preference to use the existing certificate authority.
10:53 a.m.
On Tue 18-06-19 16:36, Sanne Grinovero wrote:
On Tue, 19 Jun 2018 at 16:32, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
>
> On Tue 18-06-19 15:13, Sanne Grinovero wrote:
> >On Mon, 18 Jun 2018 at 21:48, Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
> >>
> >>
> >>
> >> > On 18 Jun 2018, at 17:49, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
> >> >
> >> > I was experimenting with "let's encrypt" but then you
told me that I
> >> > wasn't allowed to use that service.
> >>
> >> I don’t remember saying that. Knowing me I surely gave you a reason :)
> >
> >Yes, you did :)
>
> What was it?
Preference to use the existing certificate authority.
Yes ok, that's the one I could reconstruct from first principle. Plus it
would give us EV which is better. But if that becomes a hurdle and slow
down the project by 2 months, then better start with a let's encrypt
one.
2347
days inactive
2350
days old
10 comments
4 participants
participants (4)
-
Emmanuel Bernard -
Guillaume Smet -
Gunnar Morling -
Sanne Grinovero