On 1.9.2020. 15:22, Stuart Henderson wrote:
> On 2020-09-01, Hrvoje Popovski wrote:
>> Hi all,
>>
>> does anyone use an openconnect server on openbsd and have guidelines on
>> how to configure it? i see that an openconnect server can use radius, so
>> it's
t; Hi all,
> >
> > does anyone use an openconnect server on openbsd and have guidelines on
> > how to configure it? i see that an openconnect server can use radius, so
> > it's interesting to me. Which client do you use to connect to the
> > openconnect server?
>
On 2020-09-01, Hrvoje Popovski wrote:
> Hi all,
>
> does anyone use an openconnect server on openbsd and have guidelines on
> how to configure it? i see that an openconnect server can use radius, so
> it's interesting to me. Which client do you use to connect to the
>
Hi all,
does anyone use an openconnect server on openbsd and have guidelines on
how to configure it? i see that an openconnect server can use radius, so
it's interesting to me. Which client do you use to connect to the
openconnect server?
If there is something else that can use radius, i
have an soname — so if I add functions to
> libopenconnect and bump the minor release number, I think your GNOME and
> KDE authentication dialogs for the VPN are going to break. If you update
> OpenConnect and not rebuild those, of course. I appreciate you say you
> don't. But OpenConn
ation dialogs for the VPN are going to break. If you update
OpenConnect and not rebuild those, of course. I appreciate you say you
don't. But OpenConnect might occasionally have required security or
compatibility upgrades, so users might want to.
Does that mean I should actually make it jus
On Fri, 2012-11-09 at 12:19 +0100, Marc Espie wrote:
> autocrap is part of the problem, not the solution. Their documentation
> concerning version numbering, and all the fuzz they add around it don't
> help at all. The "old" style (major.minor) is fairly simple to understand
> and to use, actually,
On Fri, Nov 09, 2012 at 10:25:36AM +, Woodhouse, David wrote:
> On Fri, 2012-11-09 at 11:17 +0100, Marc Espie wrote:
> > On Thu, Nov 08, 2012 at 03:38:18PM +, Woodhouse, David wrote:
> > > On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote:
> > > >
> > > > Pass LIBTOOL=/usr/bin/libtool on
On Fri, 2012-11-09 at 11:17 +0100, Marc Espie wrote:
> On Thu, Nov 08, 2012 at 03:38:18PM +, Woodhouse, David wrote:
> > On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote:
> > >
> > > Pass LIBTOOL=/usr/bin/libtool on make's command line.
> > >
> > > Trying to get through the spaghetti of gnu
On Thu, Nov 08, 2012 at 03:38:18PM +, Woodhouse, David wrote:
> On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote:
> >
> > Pass LIBTOOL=/usr/bin/libtool on make's command line.
> >
> > Trying to get through the spaghetti of gnu autocrap only leads to
> > insanity.
> >
> > That falls under
On Thu, Nov 08, 2012 at 03:38:18PM +, Woodhouse, David wrote:
> On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote:
> >
> > Pass LIBTOOL=/usr/bin/libtool on make's command line.
> >
> > Trying to get through the spaghetti of gnu autocrap only leads to
> > insanity.
> >
> > That falls under the
On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote:
>
> Pass LIBTOOL=/usr/bin/libtool on make's command line.
>
> Trying to get through the spaghetti of gnu autocrap only leads to
> insanity.
>
> That falls under the "don't fight that shit, it's hopeless".
Hm, OpenBSD libtool doesn't seem to hono
Woodhouse, David wrote:
> It seems that libintl *is* present, but it's installed in /usr/local and
> the compiler doesn't find it by default. [...]
> surely I shouldn't have to advise users to build things that way when
> using the platform's stock libintl?
I would like to clarify that libintl i
On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote:
> Pass LIBTOOL=/usr/bin/libtool on make's command line.
Thanks, that works. This commit should make it work for everyone
automatically, without them having to override it manually:
http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/
On Thu, Nov 08, 2012 at 01:27:31PM +, Woodhouse, David wrote:
> On Thu, 2012-11-08 at 14:06 +0100, Marc Espie wrote:
> > *our* libtool looks first under .libs. If it doesn't, that's a bug.
> > I surmise the bug-reporter is actually using gnu-libtool, or the
> > libtool generated by THAT softwar
On Thu, Nov 08, 2012 at 12:57:42PM +, Stuart Henderson wrote:
> > Anyway, it doesn't *work* either ??? the build failed. It seems that when
> > building the openconnect executable, it finds the old libopenconnect.so
> > in /usr/local/lib *before* the new one it&#x
On 2012/11/08 11:23, Woodhouse, David wrote:
> I saw the OpenBSD 5.2 release and figured I should make sure the
> OpenConnect VPN client builds OK on it still. It does, but I noticed
> that it didn't build with localisation support, and tried to fix that.
>
> It seems that
I saw the OpenBSD 5.2 release and figured I should make sure the
OpenConnect VPN client builds OK on it still. It does, but I noticed
that it didn't build with localisation support, and tried to fix that.
It seems that libintl *is* present, but it's installed in /usr/local and
th
Please be gentle... this is my first ever port.
>From the site:
OpenConnect is a client for Cisco's AnyConnect SSL VPN, which is
supported by the ASA5500 Series, by IOS 12.4(9)T or later on Cisco
SR500, 870, 880, 1800, 2800, 3800, 7200 Series and Cisco 7301 Routers,
and probabl
19 matches
Mail list logo
