On 9/27/18 10:03 AM, Samuel Sieb wrote:
On 9/26/18 4:29 PM, Ed Greshko wrote:
> On 9/27/18 7:22 AM, Samuel Sieb wrote:
>> On 9/26/18 3:30 PM, Danesh Manoharan wrote:
>>> 3. On a machine outside.
>>> [root@testmachine ~]# wget
>>>
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-...
>>>
>>> --2018-09-27 06:25:26--
>>>
https://copr-be.cloud.fedoraproject.org/results/managerforlustre/manager-...
>>>
>>> Resolving copr-be.cloud.fedoraproject.org... 209.132.184.48
>>> Connecting to copr-be.cloud.fedoraproject.org|209.132.184.48|:443...
connected.
>>> ERROR: certificate common name “copr.fedorainfracloud.org” doesn’t match
requested
>>> host name “copr-be.cloud.fedoraproject.org”.
>>> To connect to
copr-be.cloud.fedoraproject.org insecurely, use
>>> ‘--no-check-certificate’.
>>
>> This might be a problem. If your work uses a proxy, it might block something
like
>> this.
>
> Well, he said "On a machine outside" which I took to mean not in the
office.
Yes, that was my point. It worked outside, but gave a certificate warning. If
they have a proxy like where I work and it detects that, it might completely block
the connection.
I see your point. I suppose I was confused since, like I showed, I am certainly
outside of his company (or any other) and I don't get a "certificate
warning".
So, I am left to wonder why he gets one and I don't.
--
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."