Failure to download the patches - security/SSL issue

[ghost]

Hello there - new at this entirely - sure this is a Johnny newboy question - just trying to find best way around 6.2 model for Citrix Licensing. This looks good but I fell at first hurdle. I got a security failure when i ran wget -O patcher.py https://raw.github.com/dalgibbard/citrix_xenserver_patcher/master/patcher.py I have detailed the message below - anyone tell me the best way to get around this. Also does anyone sell a commercial GUI product that does this (other than Citrix's core based model)?

Thanks K

MESSAGE

ERROR: certificate common name www.github.com' doesn't match requested host nameraw.github.com'.

To connect to raw.github.com insecurely, use `--no-check-certificate'. -bash: www.github.com doesnt: command not found

[dalgibbard]

wget --no-check-certificate -O patcher.py https://raw.github.com/dalgibbard/citrix_xenserver_patcher/master/patcher.py

Try that :) On 7 Aug 2014 13:30, "kerrinbanner" notifications@github.com wrote:

Hello there - new at this entirely - sure this is a Johnny newboy question

• just trying to find best way around 6.2 model for Citrix Licensing. This looks good but I fell at first hurdle. I got a security failure when i ran wget -O patcher.py https://raw.github.com/dalgibbard/citrix_xenserver_patcher/master/patcher.py I have detailed the message below - anyone tell me the best way to get around this. Also does anyone sell a commercial GUI product that does this (other than Citrix's core based model)?

Thanks K

MESSAGE ERROR: certificate common name www.github.com' doesn't match requested host nameraw.github.com'.

To connect to raw.github.com insecurely, use `--no-check-certificate'. -bash: www.github.com doesnt: command not found

— Reply to this email directly or view it on GitHub https://github.com/dalgibbard/citrix_xenserver_patcher/issues/15.

[dalgibbard]

Argh, awful formatting!

This:

wget --no-check-certificate -O patcher.py https://raw.github.com/dalgibbard/citrix_xenserver_patcher/master/patcher.py

[ghost]

That's brilliant Darren - top man - top superfast answer - dropped into my putty window and seems to work - don't want to start the upgrades yet as have a VM importing and suspect this could damage that process. i will post back later once i have run all the upgrades. Thanks very much K

[dalgibbard]

Sounds good! I'll leave this issue open for now to fix the documentation to add that flag.

[ghost]

Hi Darren - thanks for help yesterday - resolved that issue . I tried running this morning and it seems to be failing ! Any help would be greatly appreciated. Thanks K

[root@xenserver4 ~]# Downloading: XS62ESP1.zip -bash: Downloading:: command not found [root@xenserver4 ~]# Download Size: 311454853 Bytes Applying: XS62ESP10%] -bash: Download: command not found [root@xenserver4 ~]# Uncompressing... -bash: Uncompressing...: command not found [root@xenserver4 ~]# Internal Upload... -bash: Internal: command not found [root@xenserver4 ~]# The uploaded patch file already exists -bash: The: command not found [root@xenserver4 ~]# uuid: 0850b186-4d47-11e3-a720-001b2151a503 -bash: uuid:: command not found [root@xenserver4 ~]# Patch internal upload failed for: XS62ESP1.xsupdate -bash: Patch: command not found [root@xenserver4 ~]# [root@xenserver4 ~]# -bash: [root@xenserver4: command not found [root@xenserver4 ~]#

[ghost]

actually i think when i copied - somehow more lines appeared in the output. This is what the output actually said:

Thanks K

Would you like to install these items? [y/n]: y Starting patching... Downloading: XS62ESP1.zip Download Size: 311454853 Bytes Applying: XS62ESP10%] Uncompressing... Internal Upload... The uploaded patch file already exists uuid: 0850b186-4d47-11e3-a720-001b2151a503 Patch internal upload failed for: XS62ESP1.xsupdate [root@xenserver4 ~]#

[mf]

Can you please try this fork? https://github.com/mf/citrix_xenserver_patcher

[dalgibbard]

The last remaining bug looks like a duplicate of a few of the others floating around here, and i'm pretty sure that @mf 's change fixes it. Particularly as the original bug has been resolved, this is now closed :)