<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<br />Sad, and typical! I've moaned on pretty much at length here on the list about UCD's pro-monopoly computing-- indeed ridiculous that there has never been conscientious folk in the CS Dept to enough of a degree to get some FOSS support/adoption going on. I mean, not even support for wireless printing from a Mac in the library?? You'd think they could wrangle someone who knows BSD (that's what I coded C on when attending there eons ago.) Inept, yet tuition (& especially housing costs) continue up thru the stratosphere. (Oh wait-- this is a Linux list. Bon voyage to Linux Luddites Podcast btw.. I've recently spent more time, anyways, listening to BSDnow which is top-notch, so plenty else to do.)<br /><br />Best wishes to all..<br /><br />--<br /><a href="https://twitter.com/linuxusergroup" target="_blank" rel="noopener noreferrer">https://twitter.com/linuxusergroup</a><br /><br /><br />17. Dec 2016 07:27 by <a href="mailto:bill@broadley.org" target="_blank" rel="noopener noreferrer">bill@broadley.org</a>:<br /><br /><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><blockquote>I hit the same error yesterday. Bill said the Library broke it somehow.<br />The 'Official' Pulse client is working on Linux. And someone I chatted<br />with yesterday had an interested SSH port forwarding method of VPN, if<br />you have access to a server on campus.</blockquote><br />The first time I tried it, I stopped by the openconnect irc channel and worked<br />with (I think) the primary dev. We tracked it down to a SSL problem, which I<br />could even confirm with a browser.<br /><br />I reported that to the library, and they tweaked the SSL cert (it wasn't<br />properly signed).<br /><br />I lobbied for them to support openconnect since it was compatible, a signed<br />binary, 64 bit, and open source. The pulse client seems like some orphaned<br />juniper project that some 3rd party is trying to make some money off of. They<br />haven't even recompiled for 64 bit since. What's worse is that the binary<br />includes an old SSL library with known exploits, turns out that you need a<br />fairly new openssl library which actually emulates the broken behavior, but<br />doesn't allow the exploit.<br /><br />Kinda sad that campus is standardizing on an orphaned insecure unsigned binary<br />for such a critical piece of security infrastructure.<br /><br />In any case the #openconnect folks were really helpful, if you want to try to<br />get it working again I suggest trying there.<br /><br /><br /><br />_______________________________________________<br />vox-tech mailing list<br /><a href="mailto:vox-tech@lists.lugod.org" target="_blank" rel="noopener noreferrer">vox-tech@lists.lugod.org</a><br /><a href="http://lists.lugod.org/mailman/listinfo/vox-tech" target="_blank" rel="noopener noreferrer">http://lists.lugod.org/mailman/listinfo/vox-tech</a></blockquote> </body>
</html>