当前位置: 首页 > 图文教程 > 操作系统 > Unix/Linux > freeswan 文档摘录

Unix/Linux
Linux安全攻略 如何才能让内存不再泄漏
八大原因 让Linux远离普通用户
Linux下如何限制Root用户进行远程登陆
DenyHosts 阻止SSH暴力破解最好的方法
十一条守则 确保Linux系统安全的好办法
了解Linux系统内核安全的入侵侦察系统
斩断Linux邮件服务器上的垃圾邮件魔掌
Linux Ext3文件被删除后的恢复方法介绍
IP安全加密 IPSec安全技术全面接触
实用技巧 使用MD5加密GRUB密码操作步骤
感染Linux系统脚本程序的病毒技术介绍
使用 mailman 架设邮件列表
RedHat9.0下的DNS和虚拟主机的配置
利用IP 别名托管多个SSL 站点
嵌入式Linux在工业控制领域中的应用
用SSH客户端软件登录到服务器
Linux内核: 修改TCP/IP调优参数
实现Windows与Unix、Linux间数据交换
使用Linux脚本对无线网络进行管理
Linux下的网络HOOK实现以及使用方法

Unix/Linux 中的 freeswan 文档摘录


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-11-01   浏览: 151 ::
收藏到网摘: n/a

1)Building and installing the software2)Testing to see if install succeeded
Building and installing the software
There are several ways to build and install the software. All require that you have kernel source, correctly configured for your machine, as a starting point. If you don't have that yet, see the previous section
Whatever method you choose, it will do all of the following: add FreeS/WAN code to the kernel insert patches into standard kernel code to provide an interface add additional files which use that interface re-configure and re-compile the kernel to activate that code install the new kernel build the non-kernel FreeS/WAN programs and install them ipsec(8) in /usr/local/sbin others in /usr/local/lib/ipsec install FreeS/WAN man pages under /usr/local/man create the configuration file ipsec.conf(5). Editing this file to configure your IPSEC gateway is described in the next section. create an RSA public/private key pair for your system and place it in ipsec.secrets(5) install the initialisation script /etc/rc.d/init.d/ipsec create links to that script from the /etc/rc.d/rc[0-6].d directories so that each run level starts or stops IPSEC. (If the previous sentence makes no sense to you, try the From Power-up to Bash Prompt HowTo). Testing to see if install succeeded

To check that you have a sucessful install, you can reboot and check (by watching messages during boot or by looking at them later with dmesg(8)) that:the kernel reports the right version. If not, you are likely still running your old kernel. Check your lilo.conf(5) file and the installation directory (defined in the kernel make file, often /boot but the default is /), then rerun lilo(8). KLIPS initialisation messages appear Pluto reports that it is starting
You can also try the commands:ipsec --version, to test whether /usr/local/bin is in your path so you can use IPSEC administration commands ipsec whack --status, using ipsec_whack(8) to ask Pluto for status information
Of course any status information at this point should be uninteresting since you have not yet configured connections.