Package: ocserv
Version: 1.5.0-1build1
Architecture: amd64
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Aron Xu <aron@debian.org>
Installed-Size: 843
Pre-Depends: init-system-helpers (>= 1.54~)
Depends: ssl-cert, systemd | systemd-standalone-sysusers | systemd-sysusers, systemd | systemd-standalone-tmpfiles | systemd-tmpfiles, libc6 (>= 2.38), libcjose0 (>= 0.6.0), libcrypt1 (>= 1:4.1.0), libcurl3t64-gnutls (>= 7.16.2), libev4t64 (>= 1:4.04), libgnutls30t64 (>= 3.8.6), libgssapi-krb5-2 (>= 1.14+dfsg), libjansson4 (>= 2.14), libllhttp9.4 (>= 9.3.0), liblz4-1 (>= 0.0~r130), libmaxminddb0 (>= 1.0.2), libnettle8t64, libnl-3-200 (>= 3.11.0), libnl-route-3-200 (>= 3.11.0), liboath0t64 (>= 1.8.0), libpam0g (>= 0.99.7.1), libprotobuf-c1 (>= 1.0.1), libradcli4 (>= 1.2.11), libreadline8t64 (>= 6.0), libseccomp2 (>= 0.0.0~20120605), libsystemd0, libtalloc2 (>= 2.0.4~git20101213), libtasn1-6 (>= 4.14)
Recommends: ca-certificates, dnsmasq, gnutls-bin, iproute2, iputils-ping | inetutils-ping
Suggests: freeradius, haproxy
Section: net
Priority: optional
Homepage: https://www.infradead.org/ocserv/
Description: OpenConnect VPN server compatible with Cisco AnyConnect VPN
 OpenConnect server (ocserv) is an SSL VPN server. Its purpose is to be a
 secure, small, fast and configurable VPN server. It implements the OpenConnect
 SSL VPN protocol, and has also (currently experimental) compatibility with
 clients using the AnyConnect SSL VPN protocol. The OpenConnect VPN protocol
 uses the standard IETF security protocols such as TLS 1.2, and Datagram TLS to
 provide the secure VPN service. The server is implemented primarily for the
 GNU/Linux platform but its code is designed to be portable to other UNIX
 variants as well.
 .
 Ocserv's main feature is isolation of the VPN users from the main VPN server
 process. Each authenticated user is assigned an unprivileged worker process,
 and a networking (tun) device. That not only eases the control of the resources
 of each user or group of users, but also prevents privilege escalation due to
 any bug on the VPN handling (worker) server. Each VPN user can be authenticated
 using password, PAM, public key (in a smart card or not) or any combination of
 methods.
