[GLLUG] Re: linux-user digest, Vol 1 #883 - 2 msgs
Mon, 4 Nov 2002 14:06:01 -0600
This girl who went to my home church who goes to MSU now. She is really nice.
My mom was talking with her at church the other day. I guess she isn't
really plugged into any fellowship group at State. My mom thought that you
could invite her to Navs or something. Anyhow,
Beth Schwartz: 355-9392
She lives in Snyder Hall.
On Monday 04 November 2002 11:00 am, firstname.lastname@example.org wrote:
> Send linux-user mailing list submissions to
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> You can reach the person managing the list at
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of linux-user digest..."
> Today's Topics:
> 1. Re: IP Aliases and routing (Brad Fears)
> 2. Open source courses through DOD (Subba Rao)
> Message: 1
> Subject: Re: [GLLUG] IP Aliases and routing
> From: Brad Fears <email@example.com>
> To: Subba Rao <firstname.lastname@example.org>
> Cc: "email@example.com" <firstname.lastname@example.org>
> Date: 04 Nov 2002 07:55:12 -0500
> I have a similar box, but with multiple NICs rather than aliases, and I
> use the NAT functions of IPTABLES to route my packets to their
> appropriate destination IPs. As long as the OS doesn't know the
> difference between aliases and physical interfaces, I'm pretty sure nat
> would work for you too.
> Regarding the server packages, most should have a configuration option
> for binding to a specific IP. I know at least Apache, OpenSSH, and most
> FTP servers can bind themselves to a specific IP address or listen on
> all addresses by default.
> --Brad Fears
> On Sat, 2002-11-02 at 10:48, Subba Rao wrote:
> > Hello,
> > We have a Linux PC which has only one NIC with several IP Aliased
> > addresses. The aliased addresses are on different subnets. Th Linux PC
> > is pretty much behaving like a router. I can ping all the address from
> > the actual gateway that is connected to the Linux PC. All the typical
> > servers (FTP, Telnet, SMTP, HTTP, Syslog etc.) are running on this Linux
> > PC.
> > One of the aliased addresses (S.S.S.S) is serving as the syslog server
> > for the gateway. When I watch the traffic using tcpdump, the syslog
> > packet makes it to the Linux PC but returned back (or dropped) because it
> > cannot route it to S.S.S.S.
> > I have 2 questions for this setup.
> > 1. How do I route the packets on the Linux PC to it's alias address
> > S.S.S.S?
> > 2. Do the Linux servers (FTP,Telnet,SMTP,Syslog.....etc) bind to the
> > actual interface address? Or they attached to the IP Aliases as well?
> > Thank you in advance for any help.
> > Subba Rao
> > email@example.com
> > 2002-11-02
> > _______________________________________________
> > linux-user mailing list
> > firstname.lastname@example.org
> > http://www.egr.msu.edu/mailman/listinfo/linux-user
> Message: 2
> Date: Mon, 4 Nov 2002 8:20:30 -0500
> From: "Subba Rao" <email@example.com>
> To: "firstname.lastname@example.org" <email@example.com>
> Subject: [GLLUG] Open source courses through DOD
> By Dan Caterinicchia
> Nov. 1, 2002
> What would happen if open source software were banned in the Defense
> A recent study conducted by Mitre Corp. for DOD posed that
> hypothetical question and found this answer: The department's
> cybersecurity capabilities would be crippled and other areas would be
> severely impacted.
> Mitre Corp. was asked to develop a listing of open-source software
> applications at DOD and to collect representative examples of how
> those applications are being used. Over a two-week period, an e-mailed
> survey identified 115 applications and 251 examples of use, and
> Mitre's report acknowledged that actual use could be "tens of
> thousands of times larger than the number of examples identified."
> To help analyze the data, the hypothetical question was posed: What
> would happen if open-source software were banned at DOD?
> Version 1.2 of the report, "Use of Free and Open Source Software
> (FOSS) in the U.S. Department of Defense," was released Sept. 20 to
> the Defense Information Systems Agency (DISA), and found that
> open-source software applications are most important in infrastructure
> support, software development, security and research.
> "The main conclusion of the analysis was that FOSS software plays a
> more critical role in the DOD than has generally been recognized,"
> according to the report.
> In open-source software, such as Linux, the source code is publicly
> available and gives users the right to use, copy, distribute and
> change it without having to ask for permission from any external group
> or person.
> After receiving a working draft of the report in May, DISA solicited
> insights from DOD and the private sector, said Rob Walker, DISA's
> Net-Centric Enterprise Services program manager, in a presentation at
> an open-source conference in Washington, D.C., this week.
> The examination raised three concerns about the use of open-source
> * Exposing system vulnerabilities.
> * Introducing Trojan software, which is hostile software covertly
> placed in ordinary applications.
> * Developing new software that incorporates "general public license"
> (GPL) source code. This means the entire new product must be given a
> GPL, which would impact DOD software development and research areas.
> Walker's presentation dismissed the first two concerns, finding that
> the pre-emptive identification of security holes by friendly analysts
> outweighs the danger of hostile attacks, and that the introduction of
> Trojan software in open-source environments is no greater than in
> proprietary ones.
> DOD officials' main open-source concern involves the licensing, but
> "with reasonable care, GPL software can be used without disrupting
> other licenses," Walker said. He added that the introduction of
> unusually restrictive licenses, like some used by Microsoft Corp.,
> "presents a more significant issue."
> Mitre's report recommended three policy-level actions to help promote
> optimum use of open-source within DOD:
> 1. Create a "generally recognized as safe" open-source software list
> to provide official recognition of applications that are
> commercially supported, widely used, and have proven track records
> of security and reliability.
> 2. Develop generic policies to promote broader and more effective use
> of open-source, and encourage the use of commercial products that
> work well with the software. A second layer of customized policies
> then should be created to deal with the four major use areas --
> infrastructure, development, security and research.
> 3. Encourage the use of open-source to promote diversity in systems
> architecture, which would reduce the cost and security risks of
> being fully dependent on a single software product.
> Best regards.
> Subba Rao
> linux-user mailing list
> End of linux-user Digest