[leaf-commits] src/bering-uclibc4/source/shorewall shorewall-4.4.13.1.tgz, NONE, 1.1 buildtool.cfg, 1.9, 1.10
KP Kirchd?rfer <[email protected]>
| Newsgroups | gmane.linux.leaf.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/leaf/src/bering-uclibc4/source/shorewall In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv10292 Modified Files: buildtool.cfg Added Files: shorewall-4.4.13.1.tgz Log Message: change shorewall source to be inline with SF FRS requirements --- NEW FILE: shorewall-4.4.13.1.tgz --- (This appears to be a binary file; contents omitted.) Index: buildtool.cfg =================================================================== RCS file: /cvsroot/leaf/src/bering-uclibc4/source/shorewall/buildtool.cfg,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** buildtool.cfg 4 Oct 2010 05:14:04 -0000 1.9 --- buildtool.cfg 4 Oct 2010 18:33:02 -0000 1.10 *************** *** 1,11 **** - <Server shorewall-net> - Type = http - Name = www.shorewall.net - Serverpath = /pub/shorewall - </Server> - <File shorewall-4.4.13.1.tgz> ! Server = shorewall-net ! Directory = 4.4/shorewall-4.4.13/superseded Envname = SHOREWALL_SOURCE </File> --- 1,6 ---- <File shorewall-4.4.13.1.tgz> ! Server = cvs4-sourceforge ! Revision = HEAD ! Directory = shorewall Envname = SHOREWALL_SOURCE </File> ------------------------------------------------------------------------------ Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d