mirror of
git://slackware.nl/current.git
synced 2024-12-28 09:59:53 +01:00
5a12e7c134
Wed Aug 26 10:00:38 CDT 2009 Slackware 13.0 x86_64 is released as stable! Thanks to everyone who helped make this release possible -- see the RELEASE_NOTES for the credits. The ISOs are off to the replicator. This time it will be a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. We're taking pre-orders now at store.slackware.com. Please consider picking up a copy to help support the project. Once again, thanks to the entire Slackware community for all the help testing and fixing things and offering suggestions during this development cycle. As always, have fun and enjoy! -P. |
||
|---|---|---|
| .. | ||
| openvpn.conf.sample | ||
| openvpn.SlackBuild | ||
| README | ||
| slack-desc | ||
OpenVPN is a full-featured SSL VPN which can accomodate a wide range of configurations, including remote access, site-to-site VPNs, WiFi security, and enterprise-scale remote access with load balancing, failover, and fine-grained access-controls. OpenVPN implements OSI layer 2 or 3 secure network extension using the industry standard SSL/TLS protocol, supports flexible client authentication methods based on certificates, smart cards, and/or 2-factor authentication, and allows user or group-specific access control policies using firewall rules applied to the VPN virtual interface. This build of OpenVPN depends upon having openssl (not just openssl-solibs) and lzo installed on your computer. Please note that there is no default config file for OpenVPN. This is by design. OpenVPN can technically use any config file in any location. However, this script does create an /etc/openvpn/ directory with certs/ and keys/ subdirectories. Feel free to place config files, keys, and certificates in these directories. certs/ and keys/ are owned by user root and group nobody and are not world readable nor writable. Additionally, they are not writable by group nobody. It is recommended that you run openvpn nobody:nobody, but you may use another non-privilaged user and group at your option. Just change the permissions on these permissions to reflect that if you do.