d worked fully days
> > And finish with https
> > Teamcity for, Igniters for.
> >
> > https://ci.ignite.apache.org
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> > developers.2346864.n4.nabble.com/SSL-certificate-for-the-
> > CI-server-tp19830p20532.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
> >
>
t; Can evil hacker steal right now
>
> For they we worked day and night
> Don’t slept and worked fully days
> And finish with https
> Teamcity for, Igniters for.
>
> https://ci.ignite.apache.org
>
>
>
> --
> View this message in context: http://apache-igni
in context:
http://apache-ignite-developers.2346864.n4.nabble.com/SSL-certificate-for-the-CI-server-tp19830p20532.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
s.
>>> >> 1. Getting a valid certificate is easy and doesn't cost a dime
>>> nowadays.
>>> >> Here's the very details set of instructions on how we do it for
>>> Apache
>>> >> Bigtop. They are easily applicable in Ignite CI's case
Here's the very details set of instructions on how we do it for
>> Apache
>> >> Bigtop. They are easily applicable in Ignite CI's case [1]. I'd be
>> >> happy to
>> >> help with this.
>> >> 2. Reconfiguring the server to respond only on HTT
. Reconfiguring the server to respond only on HTTPS port. That's another
> >> easy
> >> thing to do for anyone with the access to the box. I don't have this,
> >> so
> >> it'd be someone else.
> >>
> >> Thoughts?
> >> Cos
>
gt;> so
>> it'd be someone else.
>>
>> Thoughts?
>> Cos
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide#BigtopCISetupGuide-Advancedpart:SetupaSSLsecuredJenkinsmaster
>>
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/SSL-certificate-for-the-CI-server-tp19830p19840.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Hi Cos,
Alexey Chetaev, please join the conversation and share your thoughts on this.
—
Denis
> On Jul 19, 2017, at 9:44 AM, Konstantin Boudnik wrote:
>
> Hey guys.
>
> I've noticed that https://ci.ignite.apache.org/ has two issues:
> - it has the invalid certificate
> - the
Hey guys.
I've noticed that https://ci.ignite.apache.org/ has two issues:
- it has the invalid certificate
- the CI server isn't responding on the https port (there's only ngnix)
I don't about the rest of the group here, but all my browsers are enforcing
HTTPS connections for the obvious