From sundaram at fedoraproject.org Mon Dec 1 10:03:33 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 01 Dec 2008 15:33:33 +0530
Subject: Bug Report
In-Reply-To:
References:
Message-ID: <4933B675.9040503@fedoraproject.org>
Boris Fridman wrote:
> Dear Redhat Company
> While Installation Where some bugs
> I don't know to which site to send the report so I've sent to this address.
>
> If I sent the report to an uncorrect address you can send me back the correct one.
> thank for attention.
>
> ????? ?????????????
> http://r.mail.ru/cln3834/my.mail.ru/?from_commercial=14
Please file a bug report in http://bugzilla.redhat.com. Thanks.
Rahul
From sundaram at fedoraproject.org Mon Dec 1 10:04:47 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 01 Dec 2008 15:34:47 +0530
Subject: Binary download page
In-Reply-To: <2fe59670811290924k49c03213u9a1ea044a2087e34@mail.gmail.com>
References: <2fe59670811290924k49c03213u9a1ea044a2087e34@mail.gmail.com>
Message-ID: <4933B6BF.2090103@fedoraproject.org>
Ali Venell wrote:
> Hi!
>
> Im trying to download Fedora 10 binaries of Subversion. From
> Subversion pages i get to this page:
>
> https://admin.fedoraproject.org/pkgdb/packages/name/subversion
>
> There is no clear link what i should do then. Where can I get them?
>
> -Ali
>
> P.s. If you make that unclear webpages you have to bear the stupid questions.
These webpages are specifically for administrators or package
maintainers and not meant for end users. You can use yumdownloader from
yum-utils for downloading the binary or source code of any package.
Rahul
From sundaram at fedoraproject.org Mon Dec 1 10:06:05 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 01 Dec 2008 15:36:05 +0530
Subject: compliments on download page
In-Reply-To: <493060C3.1040409@san.rr.com>
References: <493060C3.1040409@san.rr.com>
Message-ID: <4933B70D.1010205@fedoraproject.org>
James G. Sack (jim) wrote:
> Your F10 download page at
> http://fedoraproject.org/get-fedora
> seems exceptionally well thought out to provide everything that might be
> needed with minimal complexity and minimal useless trappings.
>
> Nice job!
Thank you very much for taking the time to offer some feedback. This is
a newly created page for the Fedora 10 release and we appreciate your
comments.
Rahul
From sundaram at fedoraproject.org Mon Dec 1 10:10:38 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 01 Dec 2008 15:40:38 +0530
Subject: A few missing items on your FAQ about using Yum to jump from
FC6 to FC8
In-Reply-To: <492D08EF.2030703@frii.com>
References: <492D08EF.2030703@frii.com>
Message-ID: <4933B81E.8080109@fedoraproject.org>
Matt Hillier wrote:
> You may have mentioned these someplace in the FAQ for using Yum to
> upgrade from FC6 to FC8, but I haven't found them after a few times
> through your WIKI. I had to do the following in addition to the
> instructions posted on the site:
>
> Things to do before you Yum upgrade from FC6 to FC8:
> 1. Turn off 'yum-updatesd' .
> 2. Disable selinux by setting /etc/selinux/config to 'disabled' and
> then reboot system.
> 3. Locate a FC7 install disk for the next step after you upgrade.
>
> Things to do after you Yum upgrade from FC6 to FC8:
> 1. Boot the system using the FC7 install disk and select the 'rescue'
> option.
> 2. Chroot /mnt/sysimage and fix the /boot/grub/device.map file for the
> device name change (ie. hda -> sda).
> 3. Make sure your disk labels are valid in /etc/fstab using 'e2label'
> on each /dev/sdX device and correct as required in the fstab by setting
> an absolute path ( ie. for swap ) or changing the disk label.
> 4. Make the new initrd file for your new kernel using the newly
> corrected path/device information with 'mkinitrd
> /boot/initrd-.img '
> 5. Exit from the 'chroot''d environment and the rescue live session,
> while ejecting the CD/DVD FC7 image from the optical drive.
> 6. Boot your upgraded system.
>
> Thanks for your time and the work on the WIKI! Please disregard this
> message if I've missed the part about performing these other steps.
>
You can very easily create a Fedora account to get edit access for the
wiki. Refer http://admin.fedoraproject.org/accounts.
Also note that Fedora 8 will not get updates after January 7 as has been
recently announced. We recommend that you upgrade to a currently
maintained release such as Fedora 9 or Fedora 10.
Rahul
From segunyisa at googlemail.com Mon Dec 1 10:55:07 2008
From: segunyisa at googlemail.com (olu yisa)
Date: Mon, 1 Dec 2008 10:55:07 +0000
Subject: Is fedora 10 a free software?
Message-ID:
Is fedora 10 a free software?How can i get it,if it's free.
From abu_hurayrah at hidayahonline.org Mon Dec 1 11:33:22 2008
From: abu_hurayrah at hidayahonline.org (Basil Mohamed Gohar)
Date: Mon, 01 Dec 2008 13:33:22 +0200
Subject: Is fedora 10 a free software?
In-Reply-To:
References:
Message-ID: <1228131202.3451.47.camel@beta>
On Mon, 2008-12-01 at 10:55 +0000, olu yisa wrote:
> Is fedora 10 a free software?How can i get it,if it's free.
>
Fedora 10 is both free as in freedom and free of charge. You can
download it via your preferred method here:
http://fedoraproject.org/en/get-fedora
Additionally, there may be some local free software enthusiasts or
Fedora Ambassadors in your area that may already have some installation
media available, if you know where to look. They would be happy to help
you out in getting a copy of Fedora as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From stickster at gmail.com Mon Dec 1 13:27:39 2008
From: stickster at gmail.com (Paul Frields)
Date: Mon, 1 Dec 2008 08:27:39 -0500
Subject: Infofeed needs F-10 updates/testing
Message-ID:
http://planet.fedoraproject.org/infofeed/
We need entries here for F-10 updates and updates-testing, when
someone gets a chance. Thanks!
Paul
From skvidal at fedoraproject.org Mon Dec 1 13:39:02 2008
From: skvidal at fedoraproject.org (Seth Vidal)
Date: Mon, 1 Dec 2008 08:39:02 -0500 (EST)
Subject: Infofeed needs F-10 updates/testing
In-Reply-To:
References:
Message-ID:
On Mon, 1 Dec 2008, Paul Frields wrote:
> http://planet.fedoraproject.org/infofeed/
>
> We need entries here for F-10 updates and updates-testing, when
> someone gets a chance. Thanks!
>
I'll add it.
thanks for the reminder.
-sv
From skvidal at fedoraproject.org Mon Dec 1 13:49:31 2008
From: skvidal at fedoraproject.org (Seth Vidal)
Date: Mon, 1 Dec 2008 08:49:31 -0500 (EST)
Subject: Infofeed needs F-10 updates/testing
In-Reply-To:
References:
Message-ID:
On Mon, 1 Dec 2008, Seth Vidal wrote:
>
>
> On Mon, 1 Dec 2008, Paul Frields wrote:
>
>> http://planet.fedoraproject.org/infofeed/
>>
>> We need entries here for F-10 updates and updates-testing, when
>> someone gets a chance. Thanks!
>>
>
> I'll add it.
>
> thanks for the reminder.
should be all set in the next half hour.
-sv
From kwade at redhat.com Mon Dec 1 14:00:27 2008
From: kwade at redhat.com (Karsten Wade)
Date: Mon, 1 Dec 2008 06:00:27 -0800
Subject: Sentence not complete in documentation.
In-Reply-To: <000e0ce07194582518045c927157@google.com>
References: <000e0ce07194582518045c927157@google.com>
Message-ID: <20081201140027.GA4382@calliope.phig.org>
On Wed, Nov 26, 2008 at 07:19:03AM +0000, claneys.skyne at gmail.com wrote:
> Hello,
> I have noticed an unfinished sentence in French documentation about ext4.
> There is link to this page and the affected extract :
>
> "6.2.2. EXT4
>
> Fedora 9 a d?but? par un aper?u g?n?ral du support ext4. Fedora 10
> propose un e2fsprogs enti?rement compatible-est4. De plus, l'?cran de
> partition d'Anacondapossext4 lorsque
> vous y"
>
> I hope, i'm refer to the correct person and apology my english.
Thank you for your report. I would like to pass it on to the French
translation team. Can you file a bug report, using the link in the
section:
http://docs.fedoraproject.org/release-notes/f10/fr/index.html#sn-Providing_feedback_on_release_notes
Thank you,
- Karsten
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From kwade at redhat.com Mon Dec 1 14:00:42 2008
From: kwade at redhat.com (Karsten Wade)
Date: Mon, 1 Dec 2008 06:00:42 -0800
Subject: tomboy, thereby mono shown installed on main website
In-Reply-To:
References:
Message-ID: <20081201140042.GB4382@calliope.phig.org>
On Tue, Nov 25, 2008 at 03:26:24PM -0800, G.LeeJ wrote:
> hi there..
>
> I am just wondering why at the mainwebsite you show a picture of
> fedora running with tomboy, clearly indicating that mono is in
> default install, yet at download page you have livecd, which at
> least up until version9 did NOT include mono or any of its apps..has
> that changed and if not, why does the dvd installer ship mono
> assuming the screenshot on main page is of the dvd installer ?
The Fedora Live CD is limited in size so does not include much of the
software that is default in the DVD installation.
The download page provides ways to get the CD and DVD images. When we
produce screenshot tours of the desktop, we usually use the software
installed by default from the DVD.
> I know in livecd 9 at least mono was gone and since debian does not
> ship mono out of the box either,I assumed that was why you weren't
> either, at least in livecd.
I don't see how those two could be related. Mono is free and open
source software and there are a number of popular applications written
in Mono, so it is natural that some of them are going to end up in the
default DVD where there is room for everything *and* the kitchen sink.
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From stickster at gmail.com Mon Dec 1 14:05:35 2008
From: stickster at gmail.com (Paul W. Frields)
Date: Mon, 1 Dec 2008 09:05:35 -0500
Subject: Infofeed needs F-10 updates/testing
In-Reply-To:
References:
Message-ID: <20081201140535.GB18297@localhost.localdomain>
On Mon, Dec 01, 2008 at 08:49:31AM -0500, Seth Vidal wrote:
>
>
> On Mon, 1 Dec 2008, Seth Vidal wrote:
>
>>
>>
>> On Mon, 1 Dec 2008, Paul Frields wrote:
>>
>>> http://planet.fedoraproject.org/infofeed/
>>>
>>> We need entries here for F-10 updates and updates-testing, when
>>> someone gets a chance. Thanks!
>>>
>>
>> I'll add it.
>>
>> thanks for the reminder.
>
> should be all set in the next half hour.
Thanks very much, Seth.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 1 17:35:25 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 1 Dec 2008 12:35:25 -0500
Subject: Meeting Reminder - Today at 22:00 UTC
Message-ID: <20081201173524.GA29640@sphe.res.cmu.edu>
Hey, just a reminder that we'll be having our weekly meeting today in
#fedora-meeting at 22:00 UTC. We'll be mostly going over the release
and what we can improve next time around, as Max suggested.
See you there,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 1 23:03:15 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 1 Dec 2008 18:03:15 -0500
Subject: Meeting Log - 2008-12-01
Message-ID: <20081201230314.GC4274@sphe.res.cmu.edu>
22:00 -!- ricky changed the topic of #fedora-meeting to: Fedora Websites - Who's here?
22:00 -!- tw2113 [n=tw2113 at fedora/tw2113] has joined #fedora-meeting
22:00 < tw2113> i'll attend just in case i have something to say
22:00 < ricky> Hey :-)
22:01 -!- rdieter [n=rdieter at ip68-110-20-4.om.om.cox.net] has joined #fedora-meeting
22:01 < ivazquez> Pong.
22:01 -!- stickster is now known as stickster_afk
22:01 -!- Sonar_Gal [n=Andrea at fedora/SonarGal] has joined #fedora-meeting
22:01 < ricky> giarc, ianweller, stiv2k, mizmo, anybody I missed: ping
22:03 -!- drago01 [n=linux at chello062178124130.3.13.univie.teleweb.at] has joined #fedora-meeting
22:03 < ricky> Oookaaay then.
22:04 < ricky> So this is the first meeting after the release - looks like everything went pretty well, but we had a couple of catches
22:04 < ricky> get-fedora was a big success - thanks to everybody that helped with that
22:04 < ricky> Next time around, it'll be ready earlier, so we'll have more time to verify the information there.
22:05 -!- Evil_Sonar_Chick [n=Andrea at fedora/SonarGal] has quit Operation timed out
22:05 < ricky> Until recently, there were some incorrect file sizes left over from the mockup. Also, the PPC DVD link was wrong for a tiny bit after the release, until it was reported/fixed
22:06 < ianweller> oh hi
22:06 < ricky> Another thing that needs to be standardized/documented is a process for how l10n should transition before a release
22:07 < ricky> I'll try to start a wiki page with specific tasks/due dates for every release
22:07 -!- llaumgui_ [n=llaumgui at cro34-2-82-226-153-125.fbx.proxad.net] has joined #fedora-meeting
22:07 < ricky> Anybody have any suggestions for that or anything we could have improved this release?
22:07 < ianweller> i think it worked out pretty well.
22:08 < ricky> Yup :-)
22:09 < giarc> seems like we had a lot fewer complaints on the site...which is great
22:09 < ivazquez> And quite a few kudos.
22:09 < stiv2k> hello
22:09 < stiv2k> sorry
22:09 < stiv2k> my laptop froze
22:10 < ricky> Somebody suggested that we have a link to http://fedoraproject.org/verify on the get-fedora pages. I wonder where that should go...
22:10 < ricky> Hopefully, we can make it fit in with the friendliness of the page, if you know what I mean
22:11 -!- cmpahar [n=cmpahar at 83.212.62.250] has joined #fedora-meeting
22:11 < ricky> Also, at least one person mentioned that they had to search for a second to find the "show me all options" link. Not sure if they were just too used to the old layout or if there's something we should change
22:13 < ianweller> probably both good ideas.
22:13 < giarc> for verify, can we just put the link to it at the top, like this page:
22:13 < giarc> http://fedoraproject.org/en/get-fedora-all
22:14 < ianweller> the /verify link could go in the sidebar. "Verify your ISOs!"
22:14 < ricky> I was thinking that it could go under resources
22:14 < giarc> ooh, i like that
22:14 < giarc> seems perfect
22:15 * ricky makes a note
22:15 < ricky> One other thing that was confusing was the process for translators
22:16 < ricky> I ended up making a completely separate copy of the repo - fedora-web.test and doing all of the F10 updates there (and pointing translators to work on that one)
22:16 * giarc ah, wondered why we ended up with two git repos
22:16 < stiv2k> ricky: hey btw you said you needed to show me something about the git access yesterday??
22:16 < ricky> Then I switched the live repo with that one on release day
22:17 -!- fraggle_ [n=fraggle at bea13-2-82-239-143-199.fbx.proxad.net] has quit "-ENOBRAIN"
22:17 < ricky> stiv2k: Yeah, I just wanted to walk you through making changes - things aren't that pretty in fedora-web right now
22:17 < stiv2k> ricky: gotcha
22:18 < ricky> I'll probably be away after the meeting, but ping me sometime and we can do that - maybe you can add the verify link then or something
22:18 < stiv2k> ricky: cool
22:19 < stiv2k> can I get the URL again? I'd like to take a look around
22:19 < giarc> using a branch for new .po files seems like it would work for next time
22:19 < ricky> You can browse it over http at http://git.fedorahosted.org/git/fedora-web.git, and you should be able to clone it with git clone ssh://git.fedorahosted.org/git/fedora-web.git now
22:20 < ricky> giarc: I was trying to find any way to avoid ugly merges. How would the branches be laid out?
22:20 < stiv2k> Permission denied (publickey).
22:20 < stiv2k> fatal: The remote end hung up unexpectedly
22:20 < stiv2k> I think I am mising a client side cert
22:21 < ricky> The thing is - we usually end up having to make changes to the F9 website at the same time while we work on the F10 website :-/
22:21 < rsc> ricky: the "fatal: The remote end hung up unexpectedly" happens very often
22:21 < ricky> stiv2k: Ah, you didn't upload an SSH public key to FAS
22:21 < giarc> if we git branch f11 and do work there, we can work in the master for current work, f11 for new
22:21 < rsc> ricky: I often need 3-5 tries once the pull/clone works.
22:22 < ricky> rsc: That's very strange. It should either just fail all the time or work all the time
22:22 < rsc> ricky: broken load balancing?
22:22 < ricky> rsc: Nope, it goes straight to one machine
22:22 < rsc> ricky: broken firewalling?
22:23 < ricky> Nope, I haven't heard of any other hosted project developers having this problem either :-/
22:23 < stiv2k> ricky: I'm trying to do it now but I'm slightly confused
22:23 < giarc> if we 'tag' a branch as live, we should be able to just 'update' the live site to the tag
22:23 < rsc> hm. Interesting.
22:23 * giarc does not have the git retry problem
22:24 < ricky> giarc: Maybe we can have a separate branch for each release and have the website generated straight from that branch.
22:24 < giarc> yeah, that is what i am thinking
22:24 < ricky> Then during the release, we just change the branch in a script and it gets updated.
22:24 < stiv2k> ricky: ah i think I got it now
22:24 < ricky> Transifex has full support for that, right?
22:24 < giarc> in svn, i make 'tags' from the branch when ready to release
22:25 < ricky> stiv2k: Once you upload the SSH public key, it'll take 1-2 hours for it to sync
22:25 < giarc> and production 'sites' are always based on the tag, that way we can add bug fixes to the branch if needed and re-tag
22:26 < rsc> giarc: but branches/tags on svn are the same.
22:26 < ricky> I'm not sure if untagging/retagging is the "git way" of doing things
22:26 < giarc> yeah, but not in concept
22:26 < giarc> in concept, tags are immutable
22:26 < giarc> not sure either
22:27 -!- llaumgui_ [n=llaumgui at cro34-2-82-226-153-125.fbx.proxad.net] has quit "Au revoir...."
22:27 < rsc> in concept. And in fact, it's a branch.
22:27 < giarc> yep
22:27 < ricky> Heh.
22:27 < giarc> but as long as it's treated as immutable, who cares?
22:27 < stiv2k> ricky: can I upload more than one key? I might want to use either of my two laptops
22:27 < ricky> We can probably get away with doing everything in branches :-)
22:27 -!- cmpahar [n=cmpahar at 83.212.62.250] has quit No route to host
22:27 < rsc> giarc: treated? I'm always commiting to tags :)
22:27 < giarc> yeah :-}
22:27 < giarc> well, then they are just branches
22:27 < ricky> stiv2k: Yup, just concatenate them together (just like an authorized_keys file)
22:27 < rsc> giarc: I can't see any read-only ability in svn.
22:28 < giarc> there is none
22:28 < giarc> unless you deny access to your tags dir
22:28 < rsc> which is nearly impossible.
22:28 < rsc> (svn+ssh e.g.)
22:28 < ricky> SCMs sure are confusing :-)
22:28 < rsc> (I'm SVN admin for > 1 year at work now)
22:28 < giarc> sure,it's just policy
22:28 < giarc> 3+
22:28 < giarc> here
22:29 < giarc> and it's just policy, as i said
22:29 < giarc> not read-only
22:29 < rsc> rules are there to get broken
22:30 < giarc> ok, your right. do you have any ideas how to solve the translation / multi repo issue from this release
22:30 < rsc> why not as before? Two repos?
22:30 < rsc> or SVN with branches.
22:31 < rsc> and choose stable/devel branch.
22:31 < giarc> so, in 3 release we have 4 repos?
22:31 < ricky> Here are my thoughts now:
22:31 < rsc> can't we kill the old one?)
22:31 < giarc> that does not seem right...
22:31 < ricky> The current website gets generated from the master branch
22:31 < rsc> at least SVN has the advantage, that we don't mirror the whole repository everywhere.
22:31 < rsc> (fedora-web.git > 50 MB here)
22:31 < ricky> Before a release (say before the F11 release), we make a F10 branch, and point the script that generates the website at that
22:32 < ricky> Then we do all F11 development in master, and repoint the script when we're ready to release
22:32 -!- ezq [n=ezq at 200-127-101-170.cab.prima.net.ar] has quit "Ex-Chat"
22:32 < ricky> That way, the master branch always contains what translators should concentrate on
22:32 < giarc> that would work, but i would just make an f11 branch, then you only need to change the script once
22:32 < giarc> oh, yeah, there is that
22:32 < rsc> ricky: but maybe not in git? Because otherwise we're blowing up the stuff to download heavily.
22:33 < ricky> How often do you need to reclone the entire repo?
22:33 < giarc> ( once per release per machine as i update them :-)
22:34 < rsc> a few times a year, when I don't know how to solve the conflicts or the stuff I broke.
22:35 < rsc> anyway, does git really understand the meaning of branching or tagging? Whatever branches were, didn't feel for me like branches.
22:35 < ricky> I guess we can look at clearing the history whenever it blows up
22:35 < ricky> rsc: What about it felt wrong?
22:35 < rsc> ricky: merging and so on. But maybe it's just git.
22:36 < rsc> ricky: merging mail/conflicts and similar stuff.
22:36 -!- ezq [n=ezq at 200-127-101-170.cab.prima.net.ar] has joined #fedora-meeting
22:36 < rsc> ricky: but I would like more to see the *.po automagically updated if some of the relevant source data changes.
22:36 < ricky> Yeah - I forget that waaay too often
22:36 -!- ezq [n=ezq at 200-127-101-170.cab.prima.net.ar] has left #fedora-meeting []
22:36 < ricky> Maybe we can put that into a commit hook or something.
22:37 < rsc> it's not you, it's a general problem, I think.
22:37 < ricky> All right, so I think we finally have a system planned out that will avoid merging as much as possible :-D
22:38 < ricky> I'll work on putting that into motion soon
22:38 < ricky> One other thing that we might want to work on is bugging translators before releases :-)
22:38 < rsc> and people to re-read that.
22:38 < ricky> We should make it a goal to not lose any translations in newer releases. This time around, we dropped quite a few :-/
22:39 -!- tw2113 is now known as tw-work
22:39 -!- tw-work [n=tw2113 at fedora/tw2113] has left #fedora-meeting ["I was raided by the FBI and all I got to keep was this lousy quit message!"]
22:39 < giarc> rsc, sorry, 'and people to re-read that' ... what do you mean?
22:39 < giarc> i did not follow what i should be re-reading :-}
22:40 < rsc> giarc: the translations should get re-read by others.
22:40 < giarc> ah, ok
22:40 < rsc> I don't know how this is for other languages, but some of them are lousy.
22:40 < ricky> Ah, yeah.
22:40 < giarc> how do we 'poke' them now?
22:40 < rsc> mailinglist IIRC.
22:40 < ricky> I usually just sent one big email to fedora-trans-list
22:40 < rsc> Can't we send the translation request to the individual translation lists?
22:41 < giarc> ah, so a post commit hook script to mail them our changes would perhaps be a good idea
22:41 < ricky> Good idea
22:41 < stiv2k> ricky: I don't know exactly what you meant by "concatenating" the RSA keys
22:41 < rsc> ricky: AFAIK there's a -de translation list for German ones.
22:41 < ricky> stiv2k: Basically just put them in a file on separate lines and upload that
22:41 < rsc> ricky: so there should be others as well?
22:41 < stiv2k> ricky: ah
22:41 < ricky> Yeah, we can look up all of the l10n lists
22:41 < ricky> I wonder if that's what docs does
22:42 < giarc> ricky, can't he just use the same key on the other machine as well ?
22:42 < rsc> ricky: no, they even don't do that.
22:42 < rsc> ricky: but they really *should* do that.
22:42 < ricky> giarc: If he wants to, yeah
22:42 < rsc> IMHO the l10n lists per language are more and better consumed rather the fedora-trans-list (if I speak for myself)
22:42 < stiv2k> ricky: can I retrieve the one I already uploaded? my other machine is off :S
22:43 < ricky> rsc: You might want to suggest that to them too next time - I never thought about that
22:43 < ricky> stiv2k: You don't currently have one stored
22:43 < stiv2k> ricky: I uploaded it... you said it might take a while to sync so maybe it's not in there yet
22:44 < ricky> stiv2k: Are you sure it worked? It's showing up blank in the db
22:44 < rsc> ricky: if I remember that the next time, yes.
22:44 < stiv2k> oh
22:44 < stiv2k> ricky: *shrug*
22:44 < ricky> (It goes to the db immediately, but takes 1-2 hours to sync to the machines)
22:44 < stiv2k> i will try it again
22:44 -!- MEP [n=MEP at host59-220-dynamic.2-79-r.retail.telecomitalia.it] has joined #fedora-meeting
22:44 < giarc> do we have anything else on our agenda?
22:44 < stiv2k> do I need a GPG key id
22:45 < ricky> I think people have been too busy with the release to work on the tasks list, so not many updates there
22:45 < rsc> ricky: is there a reason, that we've a KDE, a PPC, a GNOME but no x86_64 special page?
22:45 < ricky> stiv2k: You don't have to, but if you have one, it's nice to include
22:46 < giarc> hmmm...good question ; oversight?
22:46 < stiv2k> ricky: I'm not sure I have one, probably not...although I think the SSH RSA key went through this time
22:46 < ricky> Pretty much because i386 will work the most
22:46 -!- constanton [n=tmac at athedsl-4510554.home.otenet.gr] has joined #fedora-meeting
22:46 -!- che [n=rkastl at redhat/che] has joined #fedora-meeting
22:46 < ricky> stiv2k: Yup, it went through
22:46 < rsc> or is 64 bit hidden to avoid issues at newbies?
22:47 < ricky> Yeah, it's only on the "all options" page
22:47 < rsc> ricky: yes, most. Except I need KVM for 64 bit VMs ;)
22:47 < ricky> rsc: I don't think most newbies need that :-)
22:47 < rsc> hehe
22:47 < rsc> the verify page dropped out of /get-fedora AFAIK, but that was addressed, right?
22:47 < rsc> (sorry, was on the phone, wenn the meeting started)
22:47 < giarc> seems to have been
22:47 < ricky> Yeah, we plan to add that back under the resources
22:48 < giarc> adding under resouces
22:48 < rsc> ah one point, I got these days.
22:48 < stiv2k> yes maybe I will get to do that >:]
22:48 -!- ClausReheis [n=ClausReh at fedora/ClausReheis] has joined #fedora-meeting
22:48 < drago01> well we should offer the 64bit versions when the user is already using a 64bi os (check user agent)
22:48 < rsc> several security websites/teams claimed, that we've no visible link to a security section.
22:48 < rsc> drago01: no. That even causes issues with the static pages...
22:48 -!- constanton [n=tmac at athedsl-4510554.home.otenet.gr] has left #fedora-meeting []
22:49 < rsc> drago01: we would have to handle that using mod_rewrite which consumes much more ressources rather what we currently have.
22:49 < giarc> drago01, we have decided in the past to avoid guessing via the user-agent
22:49 < rsc> (correct me, but the fp.o servers serving the pages had heavy load during the release time)
22:49 < ricky> The vast majority of people don't even need x86_64 (but mistakenly think that they do)
22:50 < drago01> well if the hw supports it there is no reason to use i386 (it should die die die)
22:50 < ricky> We could do that type of guessing with javascript, but it's not that pretty, and l10n + javascript is usually annoying
22:50 < ricky> drago01: There actually is :-)
22:50 < rsc> so can we add maybe at ressources a link to our security pages or so?
22:50 < ricky> x86_64 is more memory-intensive, not to mention disk space with multilib
22:50 < rsc> drago01: x86_64 has currently tooo many issues and problems.
22:50 < ricky> We actually had problems on release day because one of our proxy servers was x86_64 instead of i686
22:50 < rsc> drago01: I've opened up several 64 bit specific bug reports since my workstation is x86_64-
22:51 < ricky> Thankfully, it didn't cause any downtime :-)
22:51 < ricky> So security links:
22:52 < ricky> The two security-related pages we have are http://fedoraproject.org/verify and http://fedoraproject.org/keys
22:52 < rsc> drago01: and thinking of proprietary software, which users will *definately* install (Nvidia, ATI, Flash, acroread), there are other nice problems.
22:52 < drago01> I am using 64 bit on my servers, desktop and laptop no issues that are arch specific .. the memory/diskspace is the only valid one but newer hw have enough to deal with that
22:52 < ricky> We're already planning to linnk /verify on the get-fedora pages
22:52 < ricky> Do you think most users need info from /keys?
22:52 < rsc> ricky: AFAIK the claims were related to the security team itself or to the updates with security infos
22:53 < rsc> ricky: let me maybe re-verify until the next meeting.
22:53 < drago01> rsc: nvidia, ati = no problem there are 64bit builds for years... flash is there now and acroread just works
22:53 < ricky> rsc: Ahh, OK
22:53 * giarc will read the log, but needs to head in a few
22:53 < ricky> drago01: We may have to reevaluate our choice as support changes, but at this point, i686 is the safest bet for users that don't know exactly what they want
22:53 < rsc> drago01: x86_64 flash is still broken. i386 works more or less. ATI and xorg 1.5 was sucking. Acroread only works with i386 compat libs same as flash.
22:53 < ricky> giarc: Thanks for coming!
22:54 < giarc> thanks for all your hard work!
22:54 < giarc> get-fedora worked out great
22:54 -!- giarc [i=hidden-u at gnat.asiscan.com] has quit "Leaving"
22:54 < ricky> drago01: Users that understand the reasons for running x86_64 can get it at the "show all options" page
22:54 < rsc> drago01: things are getting better, but other third party software still breaks on x86_64, I'm seeing this nearly daily - unluckily. Even with non-mentioned software here.
22:54 < drago01> rsc: ati does not suck less on i686
22:55 < rsc> even the ERP system has more x86_64 bugs rather ix86 ones :(
22:55 < rsc> maybe let's wait another few releases...users are mostly even not able to understand the difference of 32/64 bit.
22:55 < drago01> rsc: there is no reason why any software that does not ship any kernel level components to work any different with multilib on x86_64 than on i386
22:56 < ricky> Hmm. Thinking about security updates - if we can get them from an RSS feed from bodhi or something, we already have the code to format/display it (no translations, though) :-)
22:56 < rsc> drago01: theoretically. The ipmitool maintainer is still looking, why I'm generating more core dumps as he needs e.g.
22:56 < ricky> drago01: There's always laziness :-)
22:57 < rsc> ricky: let me check for the next meeting what they exactly were expecting.
22:57 < ricky> rsc: Sure thing, thanks for bringing it up
22:57 -!- wjd [n=wjd at static24-89-99-53.regina.accesscomm.ca] has quit Read error: 110 (Connection timed out)
22:57 < stiv2k> ricky: is there a web based package browser? other distros have them like packages.ubuntu.com
22:57 < drago01> and with dropping ram prices (you can get laptops with 8gb ram now) i686 should be dead soon (even vista64 is started to be shipped more often due to that)
22:57 < ricky> Right now, we don't have anything package browser targetted at users (only targetted at packagers)
22:57 < rsc> stiv2k: not that detailed, as ubuntu/debian.
22:58 < ricky> **targeted
22:58 < rsc> drago01: PAE works like a charm. And I've also lots of x86_64 incompatible Enterprise software, which refuses to work with multilib.
22:58 < rsc> drago01: especially perl on multilib is horrible.
22:58 < ricky> I think there have been mentions of projects to make one, but I'm not sure what the status on that is
22:58 < stiv2k> ricky: any plans to make one for users? just an idea.
22:58 < stiv2k> oh
22:59 < ricky> That has been brought up before - sounds like a cool python project for anybody that's interested :-)
22:59 < drago01> PAE does not solve the issue that a single app is limited to 2GB (on x86_64 even 32bit apps can access up to 4gb)
22:59 < rsc> drago01: right. But for x86_64 incompatible software the only solution.
22:59 < ricky> It'd be nice to have something very simple to start with - something like a web-based repoquery
23:00 < rsc> drago01: I'm trying to get *anything* to x86_64 at work, but I see, that there's too much old proprietary stuff out there, which does not work but is needed.
23:00 -!- pingou_laptop [n=Pingou at fedora/pingou] has quit Remote closed the connection
23:00 * ricky might run x86_64 on this machine next time around - but I'm also sticking with PAE for now :-)
23:00 < rsc> and if multilib also doesn't help, I need a plain ix86...mostly.
23:00 < ricky> rsc is scaring me away from x86_64 more and more :-P
23:00 < rsc> ricky: it works, as long as you've no proprietary software :)
23:01 < ricky> Ah, cool :-)
23:01 < ricky> Well, we've reached the hour mark, so I'll close it up
23:01 < rsc> are we payed by time?
23:01 < ricky> We got a bunch of things to improve for next release though - thanks for all of the ideas!
23:01 < stiv2k> :D
23:01 < ricky> Heh
23:02 * ricky isn't sure if there's another meeting in here at this time
23:02 < ricky> But anyway, thanks for coming, everybody :-) See you later!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From mairin at linuxgrrl.com Tue Dec 2 02:26:05 2008
From: mairin at linuxgrrl.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=)
Date: Mon, 01 Dec 2008 21:26:05 -0500
Subject: Meeting Log - 2008-12-01
In-Reply-To: <20081201230314.GC4274@sphe.res.cmu.edu>
References: <20081201230314.GC4274@sphe.res.cmu.edu>
Message-ID: <49349CBD.8080801@linuxgrrl.com>
Ricky Zhou wrote:
> 22:10 < ricky> Somebody suggested that we have a link to http://fedoraproject.org/verify on the get-fedora pages. I wonder where that should go...
> 22:10 < ricky> Hopefully, we can make it fit in with the friendliness of the page, if you know what I mean
Before we add another link to the page, can we get a bit more of the
context on how users are expected to interact with these sums? How often
do users typically use these? Is there any way to automate this
verification process? Isn't there an option to verify your media when
you go through anaconda? Is there a way we could provide only the
relevant sum after the user has downloaded an ISO? (for example, the
user clicks on the "Download Now!" link for the desktop live media, and
they get a direct link to the iso and in the background the page reloads
to a page with the sum for the desktop live media iso and instructions
on how to use it?)
Are these sums something we only expect more advanced users to care about?
> 22:11 -!- cmpahar [n=cmpahar at 83.212.62.250] has joined #fedora-meeting
> 22:11 < ricky> Also, at least one person mentioned that they had to search for a second to find the "show me all options" link. Not sure if they were just too used to the old layout or if there's something we should change
This should take a second to find, as it's not meant to be front and center.
> 22:13 < ianweller> probably both good ideas.
> 22:13 < giarc> for verify, can we just put the link to it at the top, like this page:
> 22:13 < giarc> http://fedoraproject.org/en/get-fedora-all
> 22:14 < ianweller> the /verify link could go in the sidebar. "Verify your ISOs!"
> 22:14 < ricky> I was thinking that it could go under resources
> 22:14 < giarc> ooh, i like that
Where is resources?
> 22:52 < ricky> The two security-related pages we have are http://fedoraproject.org/verify and http://fedoraproject.org/keys
> 22:52 < rsc> drago01: and thinking of proprietary software, which users will *definately* install (Nvidia, ATI, Flash, acroread), there are other nice problems.
> 22:52 < drago01> I am using 64 bit on my servers, desktop and laptop no issues that are arch specific .. the memory/diskspace is the only valid one but newer hw have enough to deal with that
> 22:52 < ricky> We're already planning to linnk /verify on the get-fedora pages
> 22:52 < ricky> Do you think most users need info from /keys?
> 22:52 < rsc> ricky: AFAIK the claims were related to the security team itself or to the updates with security infos
> 22:53 < rsc> ricky: let me maybe re-verify until the next meeting.
~m
From opensource at till.name Tue Dec 2 21:41:44 2008
From: opensource at till.name (Till Maas)
Date: Tue, 02 Dec 2008 22:41:44 +0100
Subject: Meeting Log - 2008-12-01
In-Reply-To: <49349CBD.8080801@linuxgrrl.com>
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
Message-ID: <200812022241.50606.opensource@till.name>
On Tue December 2 2008, M?ir?n Duffy wrote:
> Ricky Zhou wrote:
> > 22:10 < ricky> Somebody suggested that we have a link to
> > http://fedoraproject.org/verify on the get-fedora pages. I wonder where
> > that should go... 22:10 < ricky> Hopefully, we can make it fit in with
> > the friendliness of the page, if you know what I mean
>
> Before we add another link to the page, can we get a bit more of the
> context on how users are expected to interact with these sums? How often
> do users typically use these?
Everytime users download a new iso image, they should verify it using the
SHA1SUM file to ensure that nobody tampered it.
> Is there any way to automate this
> verification process?
The verification has to be done using tools that are not located located on
the iso file. Otherwise someone could tamper the tools on the iso file. But
Fedora could provide a tool that accepts a iso image and SHA1SUM-file and
reports to the user, whether or not the image was verified.
> Isn't there an option to verify your media when
> you go through anaconda?
This option cannot ensure that nobody tampered the iso image.
> Is there a way we could provide only the
> relevant sum after the user has downloaded an ISO? (for example, the
> user clicks on the "Download Now!" link for the desktop live media, and
> they get a direct link to the iso and in the background the page reloads
> to a page with the sum for the desktop live media iso and instructions
> on how to use it?)
I believe this is not technically not possible without using Javascript.
However it would be possible to create only one big SHA1SUM file for all
released iso images additionally to have several. But this requires someone
with access to the secret gpg keys to do this.
> Are these sums something we only expect more advanced users to care about?
I guess currently only more advanced users know the security risk that exists,
if they do not verify the iso images. I also guess that if less advanced
users know these, they would verify the iso images, too.
Regards,
Till
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
URL:
From duffy at fedoraproject.org Tue Dec 2 21:55:33 2008
From: duffy at fedoraproject.org (=?UTF-8?B?TcOhaXLDrcKtbiBEdWZmeQ==?=)
Date: Tue, 02 Dec 2008 16:55:33 -0500
Subject: Meeting Log - 2008-12-01
In-Reply-To: <200812022241.50606.opensource@till.name>
References: <20081201230314.GC4274@sphe.res.cmu.edu> <49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
Message-ID: <4935AED5.4080501@fedoraproject.org>
Till Maas wrote:
> On Tue December 2 2008, M?ir?n Duffy wrote:
>> Ricky Zhou wrote:
>>> 22:10 < ricky> Somebody suggested that we have a link to
>>> http://fedoraproject.org/verify on the get-fedora pages. I wonder where
>>> that should go... 22:10 < ricky> Hopefully, we can make it fit in with
>>> the friendliness of the page, if you know what I mean
>> Before we add another link to the page, can we get a bit more of the
>> context on how users are expected to interact with these sums? How often
>> do users typically use these?
>
> Everytime users download a new iso image, they should verify it using the
> SHA1SUM file to ensure that nobody tampered it.
But do they do this? I certainly don't. Who's to say if someone
compromised the ISO downloads that the SHA1SUM files were also not
compromised?
>
>> Is there any way to automate this
>> verification process?
>
> The verification has to be done using tools that are not located located on
> the iso file. Otherwise someone could tamper the tools on the iso file. But
> Fedora could provide a tool that accepts a iso image and SHA1SUM-file and
> reports to the user, whether or not the image was verified.
Can it automatically download the SHA1SUM file from a pre-established URL?
>
>> Isn't there an option to verify your media when
>> you go through anaconda?
>
> This option cannot ensure that nobody tampered the iso image.
It doesn't do what I suggested above?
>
>> Is there a way we could provide only the
>> relevant sum after the user has downloaded an ISO? (for example, the
>> user clicks on the "Download Now!" link for the desktop live media, and
>> they get a direct link to the iso and in the background the page reloads
>> to a page with the sum for the desktop live media iso and instructions
>> on how to use it?)
>
> I believe this is not technically not possible without using Javascript.
> However it would be possible to create only one big SHA1SUM file for all
> released iso images additionally to have several. But this requires someone
> with access to the secret gpg keys to do this.
Would that require the user to download all iso images?
>
>> Are these sums something we only expect more advanced users to care about?
>
> I guess currently only more advanced users know the security risk that exists,
> if they do not verify the iso images. I also guess that if less advanced
> users know these, they would verify the iso images, too.
But our job is to get users the software bits, not to educate them on
everything that could possibly go wrong in their doing so, right?
~m
From onekopaka at gmail.com Tue Dec 2 22:02:43 2008
From: onekopaka at gmail.com (Darren VanBuren)
Date: Tue, 2 Dec 2008 14:02:43 -0800
Subject: Meeting Log - 2008-12-01
In-Reply-To: <4935AED5.4080501@fedoraproject.org>
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
<4935AED5.4080501@fedoraproject.org>
Message-ID:
Some people won't be connected to the Internet during install, so you
would have to ask the user to connect to the Internet (maybe use the
code from the net install?)
Darren VanBuren
-------------------------
Sent from my iPod
On Dec 2, 2008, at 13:55, M?ir? n Duffy
wrote:
> Till Maas wrote:
>> On Tue December 2 2008, M?ir?n Duffy wrote:
>>> Ricky Zhou wrote:
>>>> 22:10 < ricky> Somebody suggested that we have a link to
>>>> http://fedoraproject.org/verify on the get-fedora pages. I
>>>> wonder where
>>>> that should go... 22:10 < ricky> Hopefully, we can make it fit in
>>>> with
>>>> the friendliness of the page, if you know what I mean
>>> Before we add another link to the page, can we get a bit more of the
>>> context on how users are expected to interact with these sums? How
>>> often
>>> do users typically use these?
>> Everytime users download a new iso image, they should verify it
>> using the SHA1SUM file to ensure that nobody tampered it.
>
> But do they do this? I certainly don't. Who's to say if someone
> compromised the ISO downloads that the SHA1SUM files were also not
> compromised?
>>> Is there any way to automate this verification process?
>> The verification has to be done using tools that are not located
>> located on the iso file. Otherwise someone could tamper the tools
>> on the iso file. But Fedora could provide a tool that accepts a iso
>> image and SHA1SUM-file and reports to the user, whether or not the
>> image was verified.
>
> Can it automatically download the SHA1SUM file from a pre-
> established URL?
>>> Isn't there an option to verify your media when you go through
>>> anaconda?
>> This option cannot ensure that nobody tampered the iso image.
>
> It doesn't do what I suggested above?
>>> Is there a way we could provide only the relevant sum after the
>>> user has downloaded an ISO? (for example, the
>>> user clicks on the "Download Now!" link for the desktop live
>>> media, and
>>> they get a direct link to the iso and in the background the page
>>> reloads
>>> to a page with the sum for the desktop live media iso and
>>> instructions
>>> on how to use it?)
>> I believe this is not technically not possible without using
>> Javascript. However it would be possible to create only one big
>> SHA1SUM file for all released iso images additionally to have
>> several. But this requires someone with access to the secret gpg
>> keys to do this.
>
> Would that require the user to download all iso images?
>>> Are these sums something we only expect more advanced users to
>>> care about?
>> I guess currently only more advanced users know the security risk
>> that exists, if they do not verify the iso images. I also guess
>> that if less advanced users know these, they would verify the iso
>> images, too.
>
> But our job is to get users the software bits, not to educate them
> on everything that could possibly go wrong in their doing so, right?
>
> ~m
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
From duffy at fedoraproject.org Tue Dec 2 22:14:49 2008
From: duffy at fedoraproject.org (=?UTF-8?B?TcOhaXLDrcKtbiBEdWZmeQ==?=)
Date: Tue, 02 Dec 2008 17:14:49 -0500
Subject: Meeting Log - 2008-12-01
In-Reply-To:
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
<4935AED5.4080501@fedoraproject.org>
Message-ID: <4935B359.9090201@fedoraproject.org>
Darren VanBuren wrote:
> Some people won't be connected to the Internet during install, so you
> would have to ask the user to connect to the Internet (maybe use the
> code from the net install?)
They're going to have to connect to the internet to get the SHA1SUM in
either case though, right? If the installer had some method of
downloading the sum from a server and the user didn't have an internet
connection, then it should allow the user to skip the check.
~m
From onekopaka at gmail.com Tue Dec 2 22:22:23 2008
From: onekopaka at gmail.com (Darren VanBuren)
Date: Tue, 2 Dec 2008 14:22:23 -0800
Subject: Meeting Log - 2008-12-01
In-Reply-To: <4935B359.9090201@fedoraproject.org>
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
<4935AED5.4080501@fedoraproject.org>
<4935B359.9090201@fedoraproject.org>
Message-ID: <3AA2A35E-1C45-423F-BAE0-B3CCA70606BA@gmail.com>
There already is an option to skip verification. But we should
"strongly suggest" that they verify.
Darren VanBuren
-------------------------
Sent from my iPod
On Dec 2, 2008, at 14:14, M?ir? n Duffy
wrote:
> Darren VanBuren wrote:
>> Some people won't be connected to the Internet during install, so
>> you would have to ask the user to connect to the Internet (maybe
>> use the code from the net install?)
>
> They're going to have to connect to the internet to get the SHA1SUM
> in either case though, right? If the installer had some method of
> downloading the sum from a server and the user didn't have an
> internet connection, then it should allow the user to skip the check.
>
> ~m
From mmcgrath at redhat.com Tue Dec 2 22:56:40 2008
From: mmcgrath at redhat.com (Mike McGrath)
Date: Tue, 2 Dec 2008 16:56:40 -0600 (CST)
Subject: Meeting Log - 2008-12-01
In-Reply-To: <4935AED5.4080501@fedoraproject.org>
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
<4935AED5.4080501@fedoraproject.org>
Message-ID:
On Tue, 2 Dec 2008, M?ir??n Duffy wrote:
> Till Maas wrote:
> > On Tue December 2 2008, M?ir?n Duffy wrote:
> > > Ricky Zhou wrote:
> > > > 22:10 < ricky> Somebody suggested that we have a link to
> > > > http://fedoraproject.org/verify on the get-fedora pages. I wonder where
> > > > that should go... 22:10 < ricky> Hopefully, we can make it fit in with
> > > > the friendliness of the page, if you know what I mean
> > > Before we add another link to the page, can we get a bit more of the
> > > context on how users are expected to interact with these sums? How often
> > > do users typically use these?
> >
> > Everytime users download a new iso image, they should verify it using the
> > SHA1SUM file to ensure that nobody tampered it.
>
This one's a two fold thing. The number of people that have access to
publish an iso as well as alter the verify page is actually very small (on
purpose).
I think this is one of those dirty little secrets where we publish the
information to keep ourselves safe but no one ever uses it. I'm not sure
if its because they don't care or don't know.
-Mike
From tmz at pobox.com Tue Dec 2 23:07:51 2008
From: tmz at pobox.com (Todd Zullinger)
Date: Tue, 2 Dec 2008 18:07:51 -0500
Subject: Meeting Log - 2008-12-01
In-Reply-To: <4935AED5.4080501@fedoraproject.org>
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
<4935AED5.4080501@fedoraproject.org>
Message-ID: <20081202230751.GG20204@inocybe.teonanacatl.org>
M?ir??n Duffy wrote:
> Till Maas wrote:
>> Everytime users download a new iso image, they should verify it
>> using the SHA1SUM file to ensure that nobody tampered it.
>
> But do they do this? I certainly don't.
I certainly do. But I'll freely admit that I'm not like many users.
> Who's to say if someone compromised the ISO downloads that the
> SHA1SUM files were also not compromised?
GPG is to say that. The SHA1SUM file is signed by the Fedora GPG key
(which sadly, now seems like it might change with each release, but
that's a different problem for a different list).
>>> Is there any way to automate this verification process?
I don't believe that there is. It's not something that I think every
user will take the time to perform, but we shouldn't make it too hard
for those who want to do so to find the information on how to do it.
Here's a short thread from fedora-list where a reasonably astute user
had trouble finding the info on how to verify the SHA1SUM file and
.iso files:
https://www.redhat.com/archives/fedora-list/2008-November/msg02357.html
I think after the infrastructure intrusion this past August that it is
especially important to make it easy to find the keys used to sign
software and releases. Those keys were changed, and users who are
accustomed to verifying their software should be able to locate the new
keys needed to verify the media prior to installing it.
(One of the biggest selling points to me when I switched to Red Hat
Linux many years ago was the use of pgp/gpg to ensure the integrity of
the software they ship.)
>>> Isn't there an option to verify your media when you go through
>>> anaconda?
>>
>> This option cannot ensure that nobody tampered the iso image.
>
> It doesn't do what I suggested above?
Perhaps part of the problem is that it's confusing when we talk use
the word verify. Do we mean "verify that the media was burned
properly" (which is what the installer's media check does), or do we
mean "verify that the file(s) we have downloaded are authentic files
from the Fedora Project and are not trojanned" ?
The page at fp.o/verify related to the latter.
>> I believe this is not technically not possible without using
>> Javascript. However it would be possible to create only one big
>> SHA1SUM file for all released iso images additionally to have
>> several. But this requires someone with access to the secret gpg
>> keys to do this.
>
> Would that require the user to download all iso images?
No, but the user would get a number of "No such file or directory"
errors when they run sha1sum. But this happens already, as the
SHA1SUM file contains multiple iso files usually.
I'm not sure if that's a large problem or not. It's never bothered
me. (But, as I said, I'm not the target audience.)
>>> Are these sums something we only expect more advanced users to
>>> care about?
>>
>> I guess currently only more advanced users know the security risk
>> that exists, if they do not verify the iso images. I also guess
>> that if less advanced users know these, they would verify the iso
>> images, too.
>
> But our job is to get users the software bits, not to educate them
> on everything that could possibly go wrong in their doing so,
> right?
I think it's a little of both perhaps. I do really like and
appreciate the work the website team has put into making it easy (and
attractive) to download Fedora. If we can find a way to make the
verification process a little less hidden, that would be great.
I think the use of strong digital signatures is one of Fedora's many
selling points over (most) closed source software. Not only does
Fedora offer freedom to users, I think we provide better security too.
And that's the kind of thing that's worth a little sales pitch. :)
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There is no pleasure in having nothing to do; the fun is in having
lots to do and not doing it.
-- Mary Wilson Little
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 542 bytes
Desc: not available
URL:
From tmz at pobox.com Tue Dec 2 23:28:26 2008
From: tmz at pobox.com (Todd Zullinger)
Date: Tue, 2 Dec 2008 18:28:26 -0500
Subject: Meeting Log - 2008-12-01
In-Reply-To:
References: <20081201230314.GC4274@sphe.res.cmu.edu>
<49349CBD.8080801@linuxgrrl.com>
<200812022241.50606.opensource@till.name>
<4935AED5.4080501@fedoraproject.org>
Message-ID: <20081202232826.GH20204@inocybe.teonanacatl.org>
Mike McGrath wrote:
> I think this is one of those dirty little secrets where we publish
> the information to keep ourselves safe but no one ever uses it.
I'd like to think that I'm not in too small a minority of people who
always verify the .iso files I download...
> I'm not sure if its because they don't care or don't know.
...but then I see how many people get mad that they can no longer
login as root via gdm and I suspect that a lot of users are in the
"don't care" category. :/
Still, if there's a way to fit in a link either to fp.o/verify or some
other page that explains how Fedora protects users by signing the .iso
and packages (which could in turn link to /verify and /keys), I think
that would be another nice selling point for Fedora.
Maybe it can be as simple as slightly different wording for the "Show
me all download options in one page!" balloon -- but nothing is
springing to my mind immediately.
BTW, great job on the website to all involved! get.fp.o turned out
really nice for this release.
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Any clod can have the facts; having opinions is an art.
-- Charles McCabe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 542 bytes
Desc: not available
URL:
From mattharper at mac.com Tue Dec 2 18:43:21 2008
From: mattharper at mac.com (MATT HARPER)
Date: Tue, 02 Dec 2008 10:43:21 -0800
Subject: globaldns.com
Message-ID: <91237D30-546F-41B1-8525-502E918D1A2E@mac.com>
Hello,
Please let me know if you might be interested in selling globaldns.com
Thank You,
matt Harper
From kresentphresh at gmail.com Tue Dec 2 20:32:07 2008
From: kresentphresh at gmail.com (Raz)
Date: Tue, 2 Dec 2008 12:32:07 -0800
Subject: Regarding Future OS
Message-ID:
Well, first off, I know this is going to the wrong people, this is
more a suggestion for the Development Team rather than the webmaster,
but I really didn't want to put this message on a public forum
because...well.... I'm a little susceptible to public criticism on this.
I'll try to make this as brief as I can - The reason I'm writing is
because I wanted to have the opportunity to bring up a handful of
suggestions... I've spent a lot of time using several different
operating systems as I was growing up - Starting using Windows when I
was about 7 or 8, jumped into Linux/Mac in my late-teens, and as such
I've gotten a lot of exposure to a lot of different methods of system
management... And being the analytical bastard that I am, I spent a
lot of time figuring out what was wrong with each system and figuring
out methods of solve those issues.
I see a lot of flaws in Apple and Microsoft's general design... Not so
much Apple's as Microsoft, but the point being that they both try to
blur the line between the hardware and the software. (As any good OS
should do.) Apple does this much better than Windows because Windows
is...well...junk. But nonetheless, BOTH of these companies fail at
another FAR more important level - Customer satisfaction.
Apple fails because they work too hard to get everything THEIR way -
They rely on a lot of proprietary hardware, they tend to try and keep
developers locked out of their little secrets, and they tend to charge
an insane amount for systems, hardware, accessories, whatever... To
their credit, I happen to think this hardware is at least SOMEWHAT
worth their price (Apple DOES offer some impressive hardware, and
their OS is quite nice), but should you REALLY need $1000 minimum just
to get into this setup? And it's not like you can just install OSX on
any PC. (Not easily, anyway.) Thus it's difficult to convince people
to migrate - They get kind of "locked in" with Apple just as much as
Microsoft tries to lock people in as well.
Microsoft is a whole other story, though - Microsoft not only tries to
lock people in, they also try to charge people for the most redundant
crap ever. (CAL licenses? Seriously, WTF... As if it costs more for
their software to allow more than 2 connections... Ridiculous.) Add to
that the fact that what they DO market is absolute over-priced crap,
and you have yourself another lovely corporation built on greed.
Granted, I don't have to give you guys a history lesson here, just
trying to give some background as to why I'm writing you.
I have a TON of ideas for a new type of Operating System, and I would
love to pass some of these along to you guys. I am a HUGE fan of
Fedora, I absolutely love your Operating System. But I do think it
could use a lot of improvement. And what better place to bring these
ideas than to an Open-Source OS - The operating system I envision
would also be completely free... So why not try to work with you guys
on achieving this?
Anyway... My ideas are pretty irrelevant at this stage in the game,
though... I'm not writing to you right now to say what you should do
with the OS. I'd love the opportunity to share these ideas with you in
the future, but right now I think there's something else that should
be done, and would be much better facilitated by YOU guys than myself.
(Because, let's face it - In the, uh, scheme of things, I really am
just a nobody from Seattle, and getting anything started in this
current economy is SUCH a pain in the ass...)
I propose the foundation of a new Software/Hardware alliance, and I
think YOU guys should start it. Much in the same sense that Google
founded the Open Handset Alliance to try and bring together people
towards a common goal of an open platform for handsets and ultra-
portables, I think a similar thing needs to be done for computers in
general. And I think this alliance should focus on a number of factors
- The way these companies treat customers, for example. Then you guys
should start focusing on building an Operating System that isn't only
superior to Windows and OSX, but also easier to use and manage. I know
exactly how you get people to migrate from OS X or Windows - It's all
about the ease of transition. People are turned off by the unfamiliar,
so you have to find a way to circumvent that. But you also have to
focus on the development level - You have to make it easy for people
to integrate with your OS. "Programs" and "Applications" are kind of a
thing of the past - Nobody wants to open AIM to use AOL , Jabber, AND
MSN, they'd rather have ONE program that does all three. Seamless
integration is the new forefront of application development, so you
also need to focus on how you can facilitate other software plugging
in with yours, which I have a lot of awesome theories on.
Ultimately my ideas are pretty ambitious, I know... I even think a new
Desktop Environment should be developed. (One which Gnome and KDE
could both kind of become "Modules" to. but you could also create
modules that SOMEWHAT emulate a Windows or OS X environment.) I think
Linux suffers from a number of inherent flaws that make it difficult
to convince people to use it. The filesystem organization is confusing
(which Apple did a REALLY good job of re-organizing, a similar
approach would be easy.) Software is kind of difficult to find, but if
there were a real alliance towards this sort of open-source platform,
that would change... Hell, if you could get Blizzard to join, you
could even start getting the Gamer community to migrate... Can you
imagine if they started developing these games to run on Linux instead
of Windows? Gamers would be THRILLED by the idea of getting more FPS
out of their system since they don't have to run the system-intensive
Windows OS behind their games anymore.
...Ahem..... Well, I wasn't trying to turn this into an essay... Let's
just say, I can design an OS superior to OS X or Windows, but none of
it will mean anything if I can't get some bigger players involved...
I'd love the chance to chat with someone over there about some of
these ideas in more detail, should you actually be interested. Either
way, though, I hope I get the chance to work with you guys in the
future, I think you've got the best OS out there, so I'd love to see
it go places, and I truly believe I can help.
Thanks for your time.
-Ryan Asbert
From stickster at gmail.com Wed Dec 3 13:39:51 2008
From: stickster at gmail.com (Paul W. Frields)
Date: Wed, 3 Dec 2008 08:39:51 -0500
Subject: New video promo for fp.o!
Message-ID: <20081203133809.GA5632@localhost.localdomain>
The Red Hat creative teams have put together a new video promo for
Fedora 10 release that is now up:
http://www.redhatmagazine.com/2008/12/02/video-fedora-10/
They've also provided a widget that we can put into rotation on the
fedoraproject.org home page as we've done for previous releases. We
can use the URL above, and the widget is here:
http://pfrields.fedorapeople.org/images/Fedora10_200x100%20widget_1208_ay.png
I think I recall we can "weight" these widgets to turn up more or less
often, right? It would be great to see this widget running about 2/3
of the time, since the landing site has a link to
get.fedoraproject.org for downloading.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Wed Dec 3 13:52:24 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Wed, 3 Dec 2008 08:52:24 -0500
Subject: New video promo for fp.o!
In-Reply-To: <20081203133809.GA5632@localhost.localdomain>
References: <20081203133809.GA5632@localhost.localdomain>
Message-ID: <20081203135224.GA877@sphe.res.cmu.edu>
On 2008-12-03 08:39:51 AM, Paul W. Frields wrote:
> I think I recall we can "weight" these widgets to turn up more or less
> often, right? It would be great to see this widget running about 2/3
> of the time, since the landing site has a link to
> get.fedoraproject.org for downloading.
I just added this to the banner rotation, so it should show up in an
hour or so. Also, there is a link on the blog post to fedora.org -
could you please change it to fedoraproject.org? :-)
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From eric at epkphoto.com Wed Dec 3 13:56:42 2008
From: eric at epkphoto.com (Eric Kerby)
Date: Wed, 3 Dec 2008 08:56:42 -0500
Subject: New video promo for fp.o!
In-Reply-To: <20081203133809.GA5632@localhost.localdomain>
References: <20081203133809.GA5632@localhost.localdomain>
Message-ID:
On Dec 3, 2008, at 8:39 AM, Paul W. Frields wrote:
> The Red Hat creative teams have put together a new video promo for
> Fedora 10 release that is now up:
>
> http://www.redhatmagazine.com/2008/12/02/video-fedora-10/
>
The Red Hat Magazine page has multiple mentions of "fedora.org"
instead of fp.o. There are a couple comments to this effect on the
page as well.
--
Eric Kerby
From stickster at gmail.com Wed Dec 3 14:12:13 2008
From: stickster at gmail.com (Paul W. Frields)
Date: Wed, 3 Dec 2008 09:12:13 -0500
Subject: New video promo for fp.o!
In-Reply-To:
References: <20081203133809.GA5632@localhost.localdomain>
Message-ID: <20081203141213.GE5632@localhost.localdomain>
On Wed, Dec 03, 2008 at 08:56:42AM -0500, Eric Kerby wrote:
> On Dec 3, 2008, at 8:39 AM, Paul W. Frields wrote:
>
>> The Red Hat creative teams have put together a new video promo for
>> Fedora 10 release that is now up:
>>
>> http://www.redhatmagazine.com/2008/12/02/video-fedora-10/
>>
>
> The Red Hat Magazine page has multiple mentions of "fedora.org" instead
> of fp.o. There are a couple comments to this effect on the page as well.
Yes, I brought this to their attention this morning when I saw it.
The text should be fixed shortly when the site updates.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From stickster at gmail.com Wed Dec 3 14:12:56 2008
From: stickster at gmail.com (Paul W. Frields)
Date: Wed, 3 Dec 2008 09:12:56 -0500
Subject: New video promo for fp.o!
In-Reply-To: <20081203135224.GA877@sphe.res.cmu.edu>
References: <20081203133809.GA5632@localhost.localdomain>
<20081203135224.GA877@sphe.res.cmu.edu>
Message-ID: <20081203141256.GF5632@localhost.localdomain>
On Wed, Dec 03, 2008 at 08:52:24AM -0500, Ricky Zhou wrote:
> On 2008-12-03 08:39:51 AM, Paul W. Frields wrote:
> > I think I recall we can "weight" these widgets to turn up more or less
> > often, right? It would be great to see this widget running about 2/3
> > of the time, since the landing site has a link to
> > get.fedoraproject.org for downloading.
> I just added this to the banner rotation, so it should show up in an
> hour or so. Also, there is a link on the blog post to fedora.org -
> could you please change it to fedoraproject.org? :-)
Thanks, and I requested those changes earlier this morning. There may
be some lag time until the update but it should happen shortly.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From onekopaka at gmail.com Wed Dec 3 15:21:07 2008
From: onekopaka at gmail.com (Darren VanBuren)
Date: Wed, 3 Dec 2008 07:21:07 -0800
Subject: globaldns.com
In-Reply-To: <91237D30-546F-41B1-8525-502E918D1A2E@mac.com>
References: <91237D30-546F-41B1-8525-502E918D1A2E@mac.com>
Message-ID: <36FD6A04-CC49-456A-9058-CA1F57AD27C3@gmail.com>
You probably saw the Fedora Apache Test page. This is the page shown
usually when a site isn't set up. Anyways, Red Hat and the Fedora
project do not own this domain, therefore we cannot sell it.
Darren VanBuren
-------------------------
Sent from my iPod
On Dec 2, 2008, at 10:43, MATT HARPER wrote:
> Hello,
>
> Please let me know if you might be interested in selling globaldns.com
>
> Thank You,
>
> matt Harper
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
From jbwillia at math.vt.edu Wed Dec 3 20:46:07 2008
From: jbwillia at math.vt.edu (ben)
Date: Wed, 03 Dec 2008 15:46:07 -0500
Subject: sha1sums on get-fedora
Message-ID: <4936F00F.9060709@math.vt.edu>
can we get the sha1sums for the f10 release on like the get-fedora page.
This would help alot of new people downloading Fedora to be able to find
the sha1sums quickly.
Yes for the older users, we know that we can get the sha1sums from the
mirrors and torrents but also with the sha1sums on the website those
keys can be checked in case someone is doing something they shouldnt
like repackageing the iso with rootkits installed.
Please remove this barrier to help the community
Southern_Gentlem
--
Ben Williams
Window-Linux Specialist
Mathematics Department-Virginia Tech
561E McBryde Hall
540 231-2739
From ricky at fedoraproject.org Thu Dec 4 18:54:18 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Thu, 4 Dec 2008 13:54:18 -0500
Subject: sha1sums on get-fedora
In-Reply-To: <4936F00F.9060709@math.vt.edu>
References: <4936F00F.9060709@math.vt.edu>
Message-ID: <20081204185418.GF2148@sphe.res.cmu.edu>
On 2008-12-03 03:46:07 PM, ben wrote:
> can we get the sha1sums for the f10 release on like the get-fedora page.
>
> This would help alot of new people downloading Fedora to be able to find
> the sha1sums quickly.
Ben interacts with a ton of users in #fedora every day, and mentioned
that many people wanted to see link to verification info - what do you
think? Can we go ahead and add a link in the resources box?
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From duffy at fedoraproject.org Thu Dec 4 18:58:44 2008
From: duffy at fedoraproject.org (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=)
Date: Thu, 04 Dec 2008 13:58:44 -0500
Subject: sha1sums on get-fedora
In-Reply-To: <20081204185418.GF2148@sphe.res.cmu.edu>
References: <4936F00F.9060709@math.vt.edu>
<20081204185418.GF2148@sphe.res.cmu.edu>
Message-ID: <49382864.3000402@fedoraproject.org>
Ricky Zhou wrote:
> On 2008-12-03 03:46:07 PM, ben wrote:
>> can we get the sha1sums for the f10 release on like the get-fedora page.
>>
>> This would help alot of new people downloading Fedora to be able to find
>> the sha1sums quickly.
> Ben interacts with a ton of users in #fedora every day, and mentioned
> that many people wanted to see link to verification info - what do you
> think? Can we go ahead and add a link in the resources box?
Oh the little box with the links to the user guides too?
That seems like a really good place for it.
~m
From Knight_tina at bsi.com Thu Dec 4 15:20:17 2008
From: Knight_tina at bsi.com (Tina Knight)
Date: Thu, 4 Dec 2008 10:20:17 -0500
Subject: Fedora 10 License Agreement
Message-ID: <1FFBB42D8816B54BA85D2EA11A944BB2022C90F5@BSICREMSG01CL.bsihq.com>
Our company is interested in downloading Fedora 10. I see on the web
site that the Fedora 9 - License Agreement is the last Agreement posted
for this software. Does this Agreement govern the use of version 10?
Tina Knight
Contracts
Business Software, Inc.
155 Technology Parkway, Suite 100
Norcross, Georgia 30092
770 449-3200 ext. 145 phone
770 448-3208 fax
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From kamisamanou at kamisamanou.net Fri Dec 5 03:34:58 2008
From: kamisamanou at kamisamanou.net (Kamisamanou Burgess)
Date: Thu, 4 Dec 2008 21:34:58 -0600
Subject: Fedora 10 License Agreement
In-Reply-To: <1FFBB42D8816B54BA85D2EA11A944BB2022C90F5@BSICREMSG01CL.bsihq.com>
References: <1FFBB42D8816B54BA85D2EA11A944BB2022C90F5@BSICREMSG01CL.bsihq.com>
Message-ID: <5dbb83710812041934h517ab2acka61f8ffad37f8622@mail.gmail.com>
It does. Fedora 10 is released under the same license as Fedora 9. It
is very important that you read all of the information on
http://fedoraproject.org/wiki/Legal and all the information that page
links to.
Sayonara,
Kamisamanou Burgess
http://www.kamisamanou.net
2008/12/4 Tina Knight :
> Our company is interested in downloading Fedora 10. I see on the web site
> that the Fedora 9 ? License Agreement is the last Agreement posted for this
> software. Does this Agreement govern the use of version 10?
>
>
>
>
>
>
>
> Tina Knight
>
> Contracts
>
> Business Software, Inc.
>
> 155 Technology Parkway, Suite 100
>
> Norcross, Georgia 30092
>
> 770 449-3200 ext. 145 phone
>
> 770 448-3208 fax
>
>
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
>
>
From mmcgrath at redhat.com Fri Dec 5 04:46:32 2008
From: mmcgrath at redhat.com (Mike McGrath)
Date: Thu, 4 Dec 2008 22:46:32 -0600 (CST)
Subject: Front Icon
Message-ID:
Can we shrink the front page icon?
http://fedoraproject.org/static/images/f10launch.png
Currently at 139K, its not huge or anything but I traveled a lot today and
it was noticeably slow to load compared to the rest of the content. if
there's nothing we can do, there's nothing we can do but I thought I'd
ask.
-Mike
From nicu_fedora at nicubunu.ro Fri Dec 5 08:13:19 2008
From: nicu_fedora at nicubunu.ro (Nicu Buculei)
Date: Fri, 05 Dec 2008 10:13:19 +0200
Subject: Front Icon
In-Reply-To:
References:
Message-ID: <4938E29F.3010301@nicubunu.ro>
Mike McGrath wrote:
> Can we shrink the front page icon?
>
> http://fedoraproject.org/static/images/f10launch.png
>
> Currently at 139K, its not huge or anything but I traveled a lot today and
> it was noticeably slow to load compared to the rest of the content. if
> there's nothing we can do, there's nothing we can do but I thought I'd
> ask.
Not by much if we want to keep the rounded corners transparent (PNG),
after optimization I can get it only to 132.5K, not much as a saving:
http://fedora.nicubunu.ro/banners/f10launch.png
So to a real decrease we have to make some compromises:
- switch to PNG with indexed colors at 58K, but the dithering really
looks ugly: http://fedora.nicubunu.ro/banners/f10launch_indexed.png
- switch to JPEG with no compression to preserve the image quality but
replace the transparent corners with a white background at 70K:
http://fedora.nicubunu.ro/banners/f10launch.jpg
- if needed, we can play further with JPEG compression and decrease the
file size more, like this at 34K (I believe it still look good but also
there is room to decrease the size):
http://fedora.nicubunu.ro/banners/f10launch1.jpg
--
nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com
Cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/
Open Clip Art Library: http://www.openclipart.org
my Fedora stuff: http://fedora.nicubunu.ro
From mmcgrath at redhat.com Fri Dec 5 22:39:13 2008
From: mmcgrath at redhat.com (Mike McGrath)
Date: Fri, 5 Dec 2008 16:39:13 -0600 (CST)
Subject: Front Icon
In-Reply-To: <4938E29F.3010301@nicubunu.ro>
References:
<4938E29F.3010301@nicubunu.ro>
Message-ID:
On Fri, 5 Dec 2008, Nicu Buculei wrote:
> Mike McGrath wrote:
> > Can we shrink the front page icon?
> >
> > http://fedoraproject.org/static/images/f10launch.png
> >
> > Currently at 139K, its not huge or anything but I traveled a lot today and
> > it was noticeably slow to load compared to the rest of the content. if
> > there's nothing we can do, there's nothing we can do but I thought I'd
> > ask.
>
> Not by much if we want to keep the rounded corners transparent (PNG), after
> optimization I can get it only to 132.5K, not much as a saving:
> http://fedora.nicubunu.ro/banners/f10launch.png
>
> So to a real decrease we have to make some compromises:
>
> - switch to PNG with indexed colors at 58K, but the dithering really looks
> ugly: http://fedora.nicubunu.ro/banners/f10launch_indexed.png
>
> - switch to JPEG with no compression to preserve the image quality but replace
> the transparent corners with a white background at 70K:
> http://fedora.nicubunu.ro/banners/f10launch.jpg
>
> - if needed, we can play further with JPEG compression and decrease the file
> size more, like this at 34K (I believe it still look good but also there is
> room to decrease the size): http://fedora.nicubunu.ro/banners/f10launch1.jpg
>
Naw, no worries. It's not costing that much but figured it would be worth
it
to ask.
-Mike
From kwade at fedoraproject.org Sat Dec 6 06:47:16 2008
From: kwade at fedoraproject.org (Karsten Wade)
Date: Sat, 6 Dec 2008 06:47:16 +0000 (UTC)
Subject: web/html/docs/release-notes index.php,1.51,1.52
Message-ID: <20081206064716.ADC4B70100@cvs1.fedora.phx.redhat.com>
Author: kwade
Update of /cvs/fedora/web/html/docs/release-notes
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv20680
Modified Files:
index.php
Log Message:
adding English-version language names to all language codes; next need to put them in original language.
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/release-notes/index.php,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- index.php 25 Nov 2008 06:09:58 -0000 1.51
+++ index.php 6 Dec 2008 06:46:46 -0000 1.52
@@ -39,46 +39,46 @@
For fixes or changes file a Fedora Documentation bug. Visit the Fedora Localization (L10n) release notes module page for Fedora 10 to get current statistics on the translations, including percentages completed.
From kwade at fedoraproject.org Sat Dec 6 07:41:08 2008
From: kwade at fedoraproject.org (Karsten Wade)
Date: Sat, 6 Dec 2008 07:41:08 +0000 (UTC)
Subject: web/html/docs/release-notes/f10 index.php,1.1,1.2
Message-ID: <20081206074108.7BC6A700DB@cvs1.fedora.phx.redhat.com>
Author: kwade
Update of /cvs/fedora/web/html/docs/release-notes/f10
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv28461/f10
Modified Files:
index.php
Log Message:
more work toward fixing bug 472919.
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/docs/release-notes/f10/index.php,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.php 25 Nov 2008 01:30:57 -0000 1.1
+++ index.php 6 Dec 2008 07:40:38 -0000 1.2
@@ -26,51 +26,51 @@
This document describes the changes in Fedora since the last release, and is full of vital information for both new and experienced users. The Release Notes are available in the following languages:
From sundaram at fedoraproject.org Tue Dec 9 14:40:18 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Tue, 09 Dec 2008 20:10:18 +0530
Subject: Fedora Software
In-Reply-To: <746cf2530812080601r66964707nf8bed7dc12acc31c@mail.gmail.com>
References: <746cf2530812080601r66964707nf8bed7dc12acc31c@mail.gmail.com>
Message-ID: <493E8352.1040009@fedoraproject.org>
konga_konga . wrote:
> Hi
>
> This is sathish from India working as a Asst.Prof., request you to send me
> the latest verson of Fedora software copy ...
>
> As we are working on linux for some applications...
You can just download it at http://get.fedoraproject.org or if it not
possible at all to get a copy via a local lug or magazine or other
means, apply for free media at
http://fedoraproject.org/wiki/Distribution/FreeMedia
Rahul
From neighborlee at gmail.com Fri Dec 12 18:07:07 2008
From: neighborlee at gmail.com (g.leej)
Date: Fri, 12 Dec 2008 10:07:07 -0800
Subject: not fedora, redhat.
Message-ID: <4942A84B.9090701@gmail.com>
Roadrunner, the number one Supercomputer
in the world <
from: https://fedoraproject.org/wiki/Overview
This is not true , it says redhat, please update.
thank you
lee
From ivazqueznet at gmail.com Fri Dec 12 21:57:24 2008
From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams)
Date: Fri, 12 Dec 2008 16:57:24 -0500
Subject: not fedora, redhat.
In-Reply-To: <4942A84B.9090701@gmail.com>
References: <4942A84B.9090701@gmail.com>
Message-ID: <1229119044.30148.240.camel@ignacio.lan>
On Fri, 2008-12-12 at 10:07 -0800, g.leej wrote:
> Roadrunner, the number one Supercomputer
> in the world <
>
> from: https://fedoraproject.org/wiki/Overview
>
> This is not true , it says redhat, please update.
>
> thank you
> lee
Page 29 of http://www.lanl.gov/orgs/hpc/roadrunner/pdfs/Koch%20-%
20Roadrunner%20Overview/RR%20Seminar%20-%20System%20Overview.pdf says
Fedora, and I'm more inclined to believe LANL.
--
Ignacio Vazquez-Abrams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
From eng.a.gimpiel at hotmail.com Fri Dec 12 21:58:23 2008
From: eng.a.gimpiel at hotmail.com (eng.a.gimpiel at hotmail.com)
Date: Fri, 12 Dec 2008 13:58:23 -0800
Subject: [SPAM] Vacation reply
In-Reply-To: <1229119044.30148.240.camel@ignacio.lan>
Message-ID:
An HTML attachment was scrubbed...
URL:
From mmcgrath at redhat.com Sat Dec 13 16:01:55 2008
From: mmcgrath at redhat.com (Mike McGrath)
Date: Sat, 13 Dec 2008 10:01:55 -0600 (CST)
Subject: Fedora Spins makes my head spin... (fwd)
Message-ID:
Forwarding on to our web team.
---------- Forwarded message ----------
Date: Sat, 13 Dec 2008 09:08:12
From: Ricardo Mendon?a Ferreira
To: admin at fedoraproject.org
Subject: Fedora Spins makes my head spin...
Hi there!
Excuse me, but is there a page in http://spins.fedoraproject.org/ that explains
what is each spin?
I've been a Fedora user since version 1 (up to version 6), and used it on
several computers. Now I wanted to give it a try again, and the possibility of
using an "official" Live CD (instead of going through the trouble of creating my
own) is very enticing.
The problem is: how am I supposed to know what is in each spin? The names are
cryptic, there are no links for documentation, no list of packages on each spin,
not even a brief description (or non-cryptic name) of each spin!
I believe that the spartan page is characteristic of the Linux ethos, but that's
also one of the reasons for it to not be so widely adopted... not to mention
that it doesn't make justice to the hard work of those who put effort and spent
time creating those spins.
I'll probably try the installation DVD using Qemu anyway, but I wanted to let
you know about this problem since I'm sure a lot of other people will think the
same: a good (even short) description of the spins would make them much, much
more useful and popular.
Thank you for your attention,
Ricardo.
From neighborlee at gmail.com Sat Dec 13 18:20:10 2008
From: neighborlee at gmail.com (g.leej)
Date: Sat, 13 Dec 2008 10:20:10 -0800
Subject: not fedora, redhat.
In-Reply-To: <1229119044.30148.240.camel@ignacio.lan>
References: <4942A84B.9090701@gmail.com>
<1229119044.30148.240.camel@ignacio.lan>
Message-ID: <4943FCDA.9010007@gmail.com>
Ignacio Vazquez-Abrams wrote:
> On Fri, 2008-12-12 at 10:07 -0800, g.leej wrote:
>
>> Roadrunner, the number one Supercomputer
>> in the world <
>>
>> from: https://fedoraproject.org/wiki/Overview
>>
>> This is not true , it says redhat, please update.
>>
>> thank you
>> lee
>>
>
> Page 29 of http://www.lanl.gov/orgs/hpc/roadrunner/pdfs/Koch%20-%
> 20Roadrunner%20Overview/RR%20Seminar%20-%20System%20Overview.pdf says
> Fedora, and I'm more inclined to believe LANL.
>
>
Fedora Linux (RHEL possible) < whatever that means,,possible ?
anyway,,I went back to original website, and its NOT clear at all by
just visiting there that fedora is involved.you need to update the link
then to show it more clearly if indeed fedora is still the case and not
RHEL.
cheers
lee
From sundaram at fedoraproject.org Sat Dec 13 18:40:24 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Sun, 14 Dec 2008 00:10:24 +0530
Subject: not fedora, redhat.
In-Reply-To: <4943FCDA.9010007@gmail.com>
References: <4942A84B.9090701@gmail.com> <1229119044.30148.240.camel@ignacio.lan>
<4943FCDA.9010007@gmail.com>
Message-ID: <49440198.3050506@fedoraproject.org>
g.leej wrote:
>>
> Fedora Linux (RHEL possible) < whatever that means,,possible ?
> anyway,,I went back to original website, and its NOT clear at all by
> just visiting there that fedora is involved.you need to update the link
> then to show it more clearly if indeed fedora is still the case and not
> RHEL.
It is actually both. There are a number of material online for further
information and providing them all in a overview wouldn't be appropriate.
Rahul
From tendwong at hotmail.com Sun Dec 14 08:01:37 2008
From: tendwong at hotmail.com (Tend Wong)
Date: Sun, 14 Dec 2008 16:01:37 +0800
Subject: Fedora 10 installation
Message-ID:
Hi,
Thanks for the nicely designed web site for Fedora. I happened to download the Live image for F10 but it was by no means intentional. I saw that it was an 'Installable Live CD' and I thought this to mean the 'Fedora Installation CD'. After downloading then did I realize that this was nothing but a demo CD. Also when I went to the torrents area, I saw the terms 'i386' and 'x86_64' which I found to be confusing. Does 'i386' imply only 386 machines? And does 'x86_64' imply both '32 bit x86' and '64 bit x86' machines? I believe the common notations 'x86' which refer to all 32 bit Intel x86 machines and 'x64' for Intel 64 bit machines are much more easier to understand.
Rgds,
Tend.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ed at huff20may77.us Sun Dec 14 17:39:01 2008
From: ed at huff20may77.us (Edward J. Huff)
Date: Sun, 14 Dec 2008 12:39:01 -0500
Subject: client-side cert should work for Firefox too
Message-ID: <1229276341.31151.2.camel@gamma.localnet>
Since you generate client-side certificates, why don't you generate them
for use in place of passwords when logging into the website?
Then you wouldn't have to insist on changing passwords.
--
Edward J. Huff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
From girisha.a.l at gmail.com Mon Dec 15 07:33:29 2008
From: girisha.a.l at gmail.com (girisha a l)
Date: Mon, 15 Dec 2008 13:03:29 +0530
Subject: help me i have problem in fedora 8
Message-ID: <15729a150812142333s597832d4t81b78a6def330b23@mail.gmail.com>
Dear Sir/Madam,
I am Girisha working for SRI VANI EDUCATION CENTRE.
we are using your product ie fedora system software 1 to 8 i have problem
in fedora 8.
i have installed fedora 8 in the system often the key board will not work
only the mouse is active I could not could solve this problem.
i can login in to after login only mouse is active the keyboard will not
work can you help me out in solving this problem.
With Worm Regards
Girisha
SVEC
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ivazqueznet at gmail.com Mon Dec 15 14:56:16 2008
From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams)
Date: Mon, 15 Dec 2008 09:56:16 -0500
Subject: help me i have problem in fedora 8
In-Reply-To: <15729a150812142333s597832d4t81b78a6def330b23@mail.gmail.com>
References: <15729a150812142333s597832d4t81b78a6def330b23@mail.gmail.com>
Message-ID: <1229352976.4301.46.camel@ignacio.lan>
On Mon, 2008-12-15 at 13:03 +0530, girisha a l wrote:
> Dear Sir/Madam,
>
> I am Girisha working for SRI VANI EDUCATION CENTRE.
>
> we are using your product ie fedora system software 1 to 8 i have
> problem in fedora 8.
>
> i have installed fedora 8 in the system often the key board will not
> work only the mouse is active I could not could solve this problem.
>
> i can login in to after login only mouse is active the keyboard will
> not work can you help me out in solving this problem.
>
> With Worm Regards
>
> Girisha
> SVEC
The webmaster at fedoraproject.org address is only for issues related to
Fedora's websites. For end-user Fedora support, please refer to the help
resources described here:
http://fedoraproject.org/wiki/Communicate
--
Ignacio Vazquez-Abrams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
From ivazqueznet at gmail.com Mon Dec 15 15:01:09 2008
From: ivazqueznet at gmail.com (Ignacio Vazquez-Abrams)
Date: Mon, 15 Dec 2008 10:01:09 -0500
Subject: Fedora 10 installation
In-Reply-To:
References:
Message-ID: <1229353269.4301.52.camel@ignacio.lan>
On Sun, 2008-12-14 at 16:01 +0800, Tend Wong wrote:
> Hi,
> Thanks for the nicely designed web site for Fedora. I happened to
> download the Live image for F10 but it was by no means intentional. I
> saw that it was an 'Installable Live CD' and I thought this to mean
> the 'Fedora Installation CD'. After downloading then did I realize
> that this was nothing but a demo CD. Also when I went to the torrents
> area, I saw the terms 'i386' and 'x86_64' which I found to be
> confusing. Does 'i386' imply only 386 machines? And does 'x86_64'
> imply both '32 bit x86' and '64 bit x86' machines? I believe the
> common notations 'x86' which refer to all 32 bit Intel x86 machines
> and 'x64' for Intel 64 bit machines are much more easier to
> understand.
>
> Rgds,
> Tend.
The installable CD is in fact installable; an icon on the desktop
initiates the installation process.
As for your other remarks, we will take them into consideration. Thank
you for your input.
If you want further help with Fedora then please refer to the resources
described here:
http://fedoraproject.org/wiki/Communicate
--
Ignacio Vazquez-Abrams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
From kwalper at gmail.com Mon Dec 15 13:41:47 2008
From: kwalper at gmail.com (kerry walper)
Date: Mon, 15 Dec 2008 05:41:47 -0800
Subject: I want to help support development
Message-ID: <200812150541.47339.computerupgradeandrepair@gmail.com>
Hello, my name is Kerry Walper. I am a guide and moderator at mepislovers.org
The members at mepislovers asked for mepis tee shirts. I have a tee shirt
making home based busines so I set up a website to sell mepis tees to our
members. I sell the tees for $17.00. Out of the $17.00 I donate $5.00 from
each sale to mepis development. I've been working on the website for a few
days and I just got my paypal express add to cart button working so you can
pay with paypal or credit cards.
I would like to do the same for fedora. Not sure how many fedora tees will be
sold but I would like permission to add fedora to my list of available tee
shirts. If you don't have the power to grant my request could you forward
this message to whoever could grant me permission? Thank you. Kerry Walper
aka mepnoob2005 at mepislovers.org
From signedadam at googlemail.com Mon Dec 15 14:07:30 2008
From: signedadam at googlemail.com (Adam Watts)
Date: Mon, 15 Dec 2008 14:07:30 +0000
Subject: Hello! Need help here.
Message-ID:
Hi there Web Maser of the Fedora project.
I have created a new account with you and i see on my
Todo queue:
- You have not submitted an SSH key, some Fedora resources require an SSH
key. Please submit yours by editing My
Account
Download a client-side
certificate
Can you tell me what this is, and do i need to do it ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From tendwong at hotmail.com Tue Dec 16 02:23:48 2008
From: tendwong at hotmail.com (Tend Wong)
Date: Tue, 16 Dec 2008 10:23:48 +0800
Subject: Fedora 10 installation
In-Reply-To: <1229353269.4301.52.camel@ignacio.lan>
References:
<1229353269.4301.52.camel@ignacio.lan>
Message-ID:
Hi Ignacio,
Thank you for your prompt reply. I was actually comparing the Live CD with the Full DVD version which I thought should have been the default installation of Fedora. I have since downloaded the Full DVD version with no problems and the setup carried out smoothly. It is my suggestion that the web page for 'Get Fedora' list all the installations for Fedora instead of just providing shortcuts to the Live CD i.e. there should be a shortcut for the Full DVD version as well and it should not be only hidden behind the mirror and torrent links.
Again I thank you for listening to user's inputs.
Cheers.> Subject: Re: Fedora 10 installation> From: ivazqueznet at gmail.com> To: tendwong at hotmail.com> CC: webmaster at fedoraproject.org> Date: Mon, 15 Dec 2008 10:01:09 -0500> > On Sun, 2008-12-14 at 16:01 +0800, Tend Wong wrote:> > Hi,> > Thanks for the nicely designed web site for Fedora. I happened to> > download the Live image for F10 but it was by no means intentional. I> > saw that it was an 'Installable Live CD' and I thought this to mean> > the 'Fedora Installation CD'. After downloading then did I realize> > that this was nothing but a demo CD. Also when I went to the torrents> > area, I saw the terms 'i386' and 'x86_64' which I found to be> > confusing. Does 'i386' imply only 386 machines? And does 'x86_64'> > imply both '32 bit x86' and '64 bit x86' machines? I believe the> > common notations 'x86' which refer to all 32 bit Intel x86 machines> > and 'x64' for Intel 64 bit machines are much more easier to> > understand.> > > > Rgds,> > Tend.> > The installable CD is i!
n fact installable; an icon on the desktop> initiates the installation process.> > As for your other remarks, we will take them into consideration. Thank> you for your input.> > If you want further help with Fedora then please refer to the resources> described here:> > http://fedoraproject.org/wiki/Communicate> > -- > Ignacio Vazquez-Abrams
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From butjeffsays at gmail.com Tue Dec 16 04:34:04 2008
From: butjeffsays at gmail.com (Jeffrey Ravenhorst)
Date: Mon, 15 Dec 2008 23:34:04 -0500
Subject: Self Introduction
Message-ID:
Hello everyone,
My name is Jeffrey Ravenhorst, and i'm interested in contributing to the
fedora websites project.
I've been doing web programming/design for about 6 years now (i guess that's
not a really long time, but i'm only 21), and its pretty much my favorite
thing to do as far as computing goes. I'm currently a senior at Longwood
University in virginia, usa, working on a BS in computer science (they
really don't do much web stuff there, but i do a lot on my own and for
work). Anyways, i hope i can help out... here are some of the things i
consider myself useful for:
php, mysql, xhtml, xml, javascript, css, java, c++, graphic design and
probably others.
Me and 3 other students are making a cluster of 32 fedora 9 machines for our
CMSC department (very small department...) so that's what got me into fedora
(i've always used XP.. but i just wiped my laptop and put fedora 10 on it).
So, let me know where i should start! Especially for the next month... it's
winter break, and if i'm not involved in something productive i'll surely
get the winter-time blues.
--
Jeffrey Ravenhorst
Phi Mu Alpha Sinfonia - Mu Delta
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From m.mannattil at gmail.com Tue Dec 16 05:14:11 2008
From: m.mannattil at gmail.com (Manu Mannattil)
Date: Tue, 16 Dec 2008 10:44:11 +0530
Subject: Website Fonts
Message-ID:
Hi,
I'm Manu Mannattil from Kerala, India and I've been using Fedora since it
was first started in 2004. I like it very much and I'm a regular visitor to
the site. But the fonts in the site are too small that hinders readability,
and they don't have smooth edges (especially for stuff in the bottom of the
site.) Please do rectify this problem.
--
\m/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From sundaram at fedoraproject.org Wed Dec 17 09:23:33 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Wed, 17 Dec 2008 14:53:33 +0530
Subject: Fedora 10 installation
In-Reply-To:
References: <1229353269.4301.52.camel@ignacio.lan>
Message-ID: <4948C515.4030807@fedoraproject.org>
Tend Wong wrote:
> Hi Ignacio,
>
> Thank you for your prompt reply. I was actually comparing the Live
> CD with the Full DVD version which I thought should have been the
> default installation of Fedora. I have since downloaded the Full DVD
> version with no problems and the setup carried out smoothly. It is my
> suggestion that the web page for 'Get Fedora' list all the installations
> for Fedora instead of just providing shortcuts to the Live CD i.e. there
> should be a shortcut for the Full DVD version as well and it should not
> be only hidden behind the mirror and torrent links.
>
> Again I thank you for listening to user's inputs.
It isn't hidden. The page with the full list of options is linked
prominently (blue banner that says show me all download options) from
http://get.fedoraproject.org. If you click on that, you can see that
page is a quite a maze of links. That however is very confusing to many
end users, especially the non-technical ones and we believe providing
one obvious choice is better. The Live CD (x86 arch) was picked because
it allows users to try, demo or install as necessary with a smaller
download size. It is obviously the most popular choice for downloads as
well.
Thank you for your feedback.
Rahul
From sparks at fedoraproject.org Thu Dec 18 20:11:55 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Thu, 18 Dec 2008 20:11:55 +0000 (UTC)
Subject: web/html/docs/security-guide - New directory
Message-ID: <20081218201155.857E87012F@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv2085/security-guide
Log Message:
Directory /cvs/fedora/web/html/docs/security-guide added to the repository
From sparks at fedoraproject.org Thu Dec 18 20:12:31 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Thu, 18 Dec 2008 20:12:31 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US - New directory
Message-ID: <20081218201231.A8D377012F@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv2190/en_US
Log Message:
Directory /cvs/fedora/web/html/docs/security-guide/en_US added to the repository
From sparks at fedoraproject.org Thu Dec 18 20:23:43 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Thu, 18 Dec 2008 20:23:43 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US
Security_Guide-Encryption-Data_in_Motion-Secure_Shell.php, NONE, 1.1
Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.php,
NONE, 1.1 Security_Guide-Encryption-Data_in_Motion.php, NONE, 1.1
Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.php,
NONE, 1.1 We_Need_Feedback.php, NONE,
1.1 chap-Security_Guide-Encryption.php, NONE, 1.1
chap-Security_Guide-General_Principles_of_Information_Security.php,
NONE, 1.1 chap-Security_Guide-LUKS_Disk_Encryption.php, NONE,
1.1 chap-Security_Guide-References.php, NONE,
1.1 chap-Security_Guide-Secure_Installation.php, NONE,
1.1 chap-Security_Guide-Securing_Your_Network.php, NONE,
1.1 chap-Security_Guide-Security_Overview.php, NONE,
1.1 chap-Security_Guide-Software_Maintenance.php, NONE,
1.1 index.php, NONE, 1.1 pref-Security_Guide-Preface.php, NONE,
1.1 sect-Security_Guide-Additional_Resources-Related_Books.php, NONE,
1.1
sect-Security_Guide-Additional_Resources-Related_Documentation.php,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.php,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.php,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.php,
NONE,
1.1 sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.php,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.php,
NONE, 1.1
sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.php,
NONE, 1.1
sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.php,
NONE, 1.1
sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.php,
NONE, 1.1
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.php,
NONE, 1.1
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.php,
NONE, 1.1
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.php,
NONE, 1.1 sect-Security_Guide-Attackers_and_Vulnerabilities.php, NONE,
1.1
sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.php,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.php,
NONE,
1.1 sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.php,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.php,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.php,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-Command_Options.php,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.php,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.php,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.php,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-Target_Options.php,
NONE, 1.1 sect-Security_Guide-Common_Exploits_and_Attacks.php, NONE,
1.1
sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.php,
NONE, 1.1
sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.php,
NONE, 1.1 sect-Security_Guide-Evaluating_the_Tools-Nessus.php,
NONE, 1.1 sect-Security_Guide-Evaluating_the_Tools-Nikto.php, NONE,
1.1 sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.php,
NONE,
1.1 sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.php,
NONE, 1.1 sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.php,
NONE, 1.1 sect-Security_Guide-Firewalls-Additional_Resources.php,
NONE,
1.1 sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.php,
NONE, 1.1 sect-Security_Guide-Firewalls-Common_IPTables_Filtering.php,
NONE, 1.1 sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.php,
NONE, 1.1
sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.php,
NONE, 1.1 sect-Security_Guide-Firewalls-IPv6.php, NONE, 1.1
sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.php,
NONE, 1.1 sect-Security_Guide-Firewalls-Using_IPTables.php, NONE,
1.1 sect-Security_Guide-Firewalls.php, NONE, 1.1
sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.php,
NONE, 1.1
sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.php,
NONE, 1.1
sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.php,
NONE, 1.1 sect-Security_Guide-IPTables-Additional_Resources.php, NONE,
1.1 sect-Security_Guide-IPTables-Command_Options_for_IPTables.php,
NONE, 1.1
sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.php,
NONE, 1.1 sect-Security_Guide-IPTables-IPTables_Control_Scripts.php,
NONE, 1.1 sect-Security_Guide-IPTables-IPTables_and_IPv6.php,
NONE, 1.1 sect-Security_Guide-IPTables-Saving_IPTables_Rules.php,
NONE, 1.1 sect-Security_Guide-IPTables.php, NONE, 1.1
sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.php,
NONE,
1.1 sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.php,
NONE, 1.1 sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.php,
NONE, 1.1
sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.php,
NONE, 1.1
sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.php,
NONE, 1.1 sect-Security_Guide-Kerberos-Additional_Resources.php, NONE,
1.1 sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.php,
NONE,
1.1 sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.php,
NONE, 1.1 sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.php,
NONE, 1.1 sect-Security_Guide-Kerberos-How_Kerberos_Works.php,
NONE, 1.1 sect-Security_Guide-Kerberos-Kerberos_Terminology.php,
NONE, 1.1 sect-Security_Guide-Kerberos-Kerberos_and_PAM.php, NONE, 1.1
sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.php,
NONE, 1.1 sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.php,
NONE, 1.1 sect-Security_Guide-Kerberos.php, NONE,
1.1 sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.php,
NONE, 1.1
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.php,
NONE, 1.1
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.php,
NONE, 1.1
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.php,
NONE, 1.1 sect-Security_Guide-Option_Fields-Access_Control.php,
NONE, 1.1 sect-Security_Guide-Option_Fields-Expansions.php, NONE,
1.1 sect-Security_Guide-Option_Fields-Shell_Commands.php, NONE, 1.1
sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.php,
NONE, 1.1
sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.php,
NONE,
1.1 sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.php,
NONE, 1.1
sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.php,
NONE, 1.1
sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.php,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.php,
NONE,
1.1 sect-Security_Guide-Pluggable_Authentication_Modules_PAM.php,
NONE, 1.1
sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.php,
NONE, 1.1 sect-Security_Guide-Securing_FTP-Anonymous_Access.php, NONE,
1.1
sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.php,
NONE, 1.1 sect-Security_Guide-Securing_FTP-User_Accounts.php, NONE,
1.1 sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.php,
NONE, 1.1
sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.php,
NONE, 1.1
sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.php,
NONE, 1.1
sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.php,
NONE,
1.1 sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.php,
NONE, 1.1
sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.php,
NONE, 1.1
sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.php,
NONE, 1.1 sect-Security_Guide-Securing_Sendmail-Mail_only_Users.php,
NONE, 1.1 sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.php,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.php,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.php,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.php,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.php,
NONE, 1.1 sect-Security_Guide-Security_Updates.php, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_FTP.php, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_NFS.php, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_NIS.php, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_Portmap.php, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_Sendmail.php, NONE,
1.1
sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.php,
NONE, 1.1
sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.php,
NONE, 1.1 sect-Security_Guide-Server_Security.php, NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.php,
NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.php,
NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.php,
NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.php,
NONE, 1.1 sect-Security_Guide-Single_Sign_on_SSO.php, NONE, 1.1
sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.php,
NONE, 1.1
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.php,
NONE, 1.1
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.php,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.php,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.php,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.php,
NONE, 1.1 sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.php,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.php,
NONE, 1.1 sect-Security_Guide-TCP_Wrappers_and_xinetd.php, NONE, 1.1
sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.php,
NONE, 1.1
sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.php,
NONE, 1.1
sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.php,
NONE, 1.1
sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.php,
NONE,
1.1 sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.php,
NONE, 1.1
sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.php,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.php,
NONE, 1.1 sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.php,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.php,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.php,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.php,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.php,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.php,
NONE, 1.1 sect-Security_Guide-Virtual_Private_Networks_VPNs.php, NONE,
1.1
sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.php,
NONE, 1.1
sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.php,
NONE, 1.1 sect-Security_Guide-Vulnerability_Assessment.php, NONE, 1.1
sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.php,
NONE, 1.1
sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.php,
NONE, 1.1
Message-ID: <20081218202343.1D4B67012F@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv3735
Added Files:
Security_Guide-Encryption-Data_in_Motion-Secure_Shell.php
Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.php
Security_Guide-Encryption-Data_in_Motion.php
Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.php
We_Need_Feedback.php chap-Security_Guide-Encryption.php
chap-Security_Guide-General_Principles_of_Information_Security.php
chap-Security_Guide-LUKS_Disk_Encryption.php
chap-Security_Guide-References.php
chap-Security_Guide-Secure_Installation.php
chap-Security_Guide-Securing_Your_Network.php
chap-Security_Guide-Security_Overview.php
chap-Security_Guide-Software_Maintenance.php index.php
pref-Security_Guide-Preface.php
sect-Security_Guide-Additional_Resources-Related_Books.php
sect-Security_Guide-Additional_Resources-Related_Documentation.php
sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.php
sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.php
sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.php
sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.php
sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.php
sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.php
sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.php
sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.php
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.php
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.php
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.php
sect-Security_Guide-Attackers_and_Vulnerabilities.php
sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.php
sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.php
sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.php
sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.php
sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.php
sect-Security_Guide-Command_Options_for_IPTables-Command_Options.php
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.php
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.php
sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.php
sect-Security_Guide-Command_Options_for_IPTables-Target_Options.php
sect-Security_Guide-Common_Exploits_and_Attacks.php
sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.php
sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.php
sect-Security_Guide-Evaluating_the_Tools-Nessus.php
sect-Security_Guide-Evaluating_the_Tools-Nikto.php
sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.php
sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.php
sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.php
sect-Security_Guide-Firewalls-Additional_Resources.php
sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.php
sect-Security_Guide-Firewalls-Common_IPTables_Filtering.php
sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.php
sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.php
sect-Security_Guide-Firewalls-IPv6.php
sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.php
sect-Security_Guide-Firewalls-Using_IPTables.php
sect-Security_Guide-Firewalls.php
sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.php
sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.php
sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.php
sect-Security_Guide-IPTables-Additional_Resources.php
sect-Security_Guide-IPTables-Command_Options_for_IPTables.php
sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.php
sect-Security_Guide-IPTables-IPTables_Control_Scripts.php
sect-Security_Guide-IPTables-IPTables_and_IPv6.php
sect-Security_Guide-IPTables-Saving_IPTables_Rules.php
sect-Security_Guide-IPTables.php
sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.php
sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.php
sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.php
sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.php
sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.php
sect-Security_Guide-Kerberos-Additional_Resources.php
sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.php
sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.php
sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.php
sect-Security_Guide-Kerberos-How_Kerberos_Works.php
sect-Security_Guide-Kerberos-Kerberos_Terminology.php
sect-Security_Guide-Kerberos-Kerberos_and_PAM.php
sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.php
sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.php
sect-Security_Guide-Kerberos.php
sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.php
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.php
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.php
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.php
sect-Security_Guide-Option_Fields-Access_Control.php
sect-Security_Guide-Option_Fields-Expansions.php
sect-Security_Guide-Option_Fields-Shell_Commands.php
sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.php
sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.php
sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.php
sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.php
sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM.php
sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.php
sect-Security_Guide-Securing_FTP-Anonymous_Access.php
sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.php
sect-Security_Guide-Securing_FTP-User_Accounts.php
sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.php
sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.php
sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.php
sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.php
sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.php
sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.php
sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.php
sect-Security_Guide-Securing_Sendmail-Mail_only_Users.php
sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.php
sect-Security_Guide-Security_Updates.php
sect-Security_Guide-Server_Security-Securing_FTP.php
sect-Security_Guide-Server_Security-Securing_NFS.php
sect-Security_Guide-Server_Security-Securing_NIS.php
sect-Security_Guide-Server_Security-Securing_Portmap.php
sect-Security_Guide-Server_Security-Securing_Sendmail.php
sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.php
sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.php
sect-Security_Guide-Server_Security.php
sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.php
sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.php
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.php
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.php
sect-Security_Guide-Single_Sign_on_SSO.php
sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.php
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.php
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.php
sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.php
sect-Security_Guide-TCP_Wrappers_and_xinetd.php
sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.php
sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.php
sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.php
sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.php
sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.php
sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.php
sect-Security_Guide-Virtual_Private_Networks_VPNs.php
sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.php
sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.php
sect-Security_Guide-Vulnerability_Assessment.php
sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.php
sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.php
Log Message:
Initial build of 1.0.
***** Error reading new file: [Errno 2] No such file or directory: 'Security_Guide-Encryption-Data_in_Motion-Secure_Shell.php'
***** Error reading new file: [Errno 2] No such file or directory: 'Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.php'
***** Error reading new file: [Errno 2] No such file or directory: 'Security_Guide-Encryption-Data_in_Motion.php'
***** Error reading new file: [Errno 2] No such file or directory: 'Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.php'
***** Error reading new file: [Errno 2] No such file or directory: 'We_Need_Feedback.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-Encryption.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-General_Principles_of_Information_Security.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-LUKS_Disk_Encryption.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-References.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-Secure_Installation.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-Securing_Your_Network.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-Security_Overview.php'
***** Error reading new file: [Errno 2] No such file or directory: 'chap-Security_Guide-Software_Maintenance.php'
***** Error reading new file: [Errno 2] No such file or directory: 'index.php'
***** Error reading new file: [Errno 2] No such file or directory: 'pref-Security_Guide-Preface.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Related_Books.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Related_Documentation.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Attackers_and_Vulnerabilities.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Command_Options_for_IPTables-Command_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Command_Options_for_IPTables-Target_Options.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Common_Exploits_and_Attacks.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Evaluating_the_Tools-Nessus.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Evaluating_the_Tools-Nikto.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-Additional_Resources.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-Common_IPTables_Filtering.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-IPv6.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls-Using_IPTables.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Firewalls.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables-Additional_Resources.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables-Command_Options_for_IPTables.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables-IPTables_Control_Scripts.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables-IPTables_and_IPv6.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables-Saving_IPTables_Rules.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Additional_Resources.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-How_Kerberos_Works.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Kerberos_Terminology.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Kerberos_and_PAM.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Kerberos.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Option_Fields-Access_Control.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Option_Fields-Expansions.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Option_Fields-Shell_Commands.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Pluggable_Authentication_Modules_PAM.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_FTP-Anonymous_Access.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_FTP-User_Accounts.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_Sendmail-Mail_only_Users.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Security_Updates.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Securing_FTP.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Securing_NFS.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Securing_NIS.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Securing_Portmap.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Securing_Sendmail.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Server_Security.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Single_Sign_on_SSO.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-TCP_Wrappers_and_xinetd.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Virtual_Private_Networks_VPNs.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-Vulnerability_Assessment.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.php'
***** Error reading new file: [Errno 2] No such file or directory: 'sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.php'
From sparks at fedoraproject.org Mon Dec 22 15:55:09 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 15:55:09 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US
Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html, NONE, 1.1
Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html,
NONE, 1.1 Security_Guide-Encryption-Data_in_Motion.html, NONE, 1.1
Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html,
NONE, 1.1 We_Need_Feedback.html, NONE,
1.1 chap-Security_Guide-Encryption.html, NONE, 1.1
chap-Security_Guide-General_Principles_of_Information_Security.html,
NONE, 1.1 chap-Security_Guide-References.html, NONE,
1.1 chap-Security_Guide-Secure_Installation.html, NONE,
1.1 chap-Security_Guide-Securing_Your_Network.html, NONE,
1.1 chap-Security_Guide-Security_Overview.html, NONE,
1.1 chap-Security_Guide-Software_Maintenance.html, NONE,
1.1 index.html, NONE, 1.1 pref-Security_Guide-Preface.html, NONE,
1.1 sect-Security_Guide-Additional_Resources-Related_Books.html, NONE,
1.1
sect-Security_Guide-Additional_Resources-Related_Documentation.html,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html,
NONE,
1.1 sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html,
NONE, 1.1
sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html,
NONE, 1.1
sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html,
NONE, 1.1
sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html,
NONE, 1.1
sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html,
NONE, 1.1
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html,
NONE, 1.1
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html,
NONE, 1.1
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html,
NONE, 1.1 sect-Security_Guide-Attackers_and_Vulnerabilities.html,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html,
NONE,
1.1 sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html,
NONE, 1.1
sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html,
NONE, 1.1
sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html,
NONE, 1.1 sect-Security_Guide-Common_Exploits_and_Attacks.html, NONE,
1.1
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html,
NONE, 1.1
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html,
NONE, 1.1
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html,
NONE,
1.1 sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html,
NONE, 1.1
sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html,
NONE, 1.1
sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html,
NONE, 1.1 sect-Security_Guide-Evaluating_the_Tools-Nessus.html,
NONE, 1.1 sect-Security_Guide-Evaluating_the_Tools-Nikto.html, NONE,
1.1 sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html,
NONE,
1.1 sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html,
NONE, 1.1 sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html,
NONE, 1.1 sect-Security_Guide-Firewalls-Additional_Resources.html,
NONE,
1.1 sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html,
NONE,
1.1 sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html,
NONE, 1.1 sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html,
NONE, 1.1
sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html,
NONE, 1.1 sect-Security_Guide-Firewalls-IPv6.html, NONE, 1.1
sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html,
NONE, 1.1 sect-Security_Guide-Firewalls-Using_IPTables.html,
NONE, 1.1 sect-Security_Guide-Firewalls.html, NONE, 1.1
sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.html,
NONE, 1.1
sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.html,
NONE, 1.1
sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.html,
NONE, 1.1 sect-Security_Guide-IPTables-Additional_Resources.html,
NONE,
1.1 sect-Security_Guide-IPTables-Command_Options_for_IPTables.html,
NONE, 1.1
sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html,
NONE, 1.1 sect-Security_Guide-IPTables-IPTables_Control_Scripts.html,
NONE, 1.1 sect-Security_Guide-IPTables-IPTables_and_IPv6.html, NONE,
1.1 sect-Security_Guide-IPTables-Saving_IPTables_Rules.html,
NONE, 1.1 sect-Security_Guide-IPTables.html, NONE, 1.1
sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html,
NONE,
1.1 sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html,
NONE,
1.1 sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html,
NONE, 1.1
sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html,
NONE, 1.1
sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html,
NONE, 1.1 sect-Security_Guide-Kerberos-Additional_Resources.html,
NONE,
1.1 sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html,
NONE,
1.1 sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html,
NONE, 1.1 sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html,
NONE, 1.1 sect-Security_Guide-Kerberos-How_Kerberos_Works.html,
NONE, 1.1 sect-Security_Guide-Kerberos-Kerberos_Terminology.html,
NONE, 1.1 sect-Security_Guide-Kerberos-Kerberos_and_PAM.html, NONE,
1.1
sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html,
NONE, 1.1 sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html,
NONE, 1.1 sect-Security_Guide-Kerberos.html, NONE,
1.1 sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html,
NONE, 1.1
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html,
NONE, 1.1
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html,
NONE, 1.1
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html,
NONE, 1.1 sect-Security_Guide-LUKS_Disk_Encryption.html, NONE,
1.1 sect-Security_Guide-Option_Fields-Access_Control.html, NONE,
1.1 sect-Security_Guide-Option_Fields-Expansions.html, NONE,
1.1 sect-Security_Guide-Option_Fields-Shell_Commands.html, NONE, 1.1
sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html,
NONE, 1.1
sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html,
NONE, 1.1
sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html,
NONE, 1.1
sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html,
NONE, 1.1
sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html,
NONE, 1.1
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html,
NONE,
1.1 sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html,
NONE, 1.1
sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html,
NONE, 1.1 sect-Security_Guide-Securing_FTP-Anonymous_Access.html,
NONE, 1.1
sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html,
NONE, 1.1 sect-Security_Guide-Securing_FTP-User_Accounts.html, NONE,
1.1 sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html,
NONE, 1.1
sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html,
NONE, 1.1
sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html,
NONE, 1.1
sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html,
NONE,
1.1 sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html,
NONE, 1.1
sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html,
NONE, 1.1
sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html,
NONE, 1.1 sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html,
NONE, 1.1 sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.html,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.html,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.html,
NONE, 1.1
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.html,
NONE, 1.1 sect-Security_Guide-Security_Updates.html, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_FTP.html, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_NFS.html, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_NIS.html, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_Portmap.html, NONE,
1.1 sect-Security_Guide-Server_Security-Securing_Sendmail.html, NONE,
1.1
sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html,
NONE, 1.1
sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html,
NONE, 1.1 sect-Security_Guide-Server_Security.html, NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html,
NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html,
NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html,
NONE, 1.1
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html,
NONE, 1.1 sect-Security_Guide-Single_Sign_on_SSO.html, NONE, 1.1
sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html,
NONE, 1.1
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html,
NONE, 1.1
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html,
NONE, 1.1 sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html,
NONE, 1.1
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html,
NONE, 1.1 sect-Security_Guide-TCP_Wrappers_and_xinetd.html, NONE, 1.1
sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html,
NONE, 1.1
sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html,
NONE, 1.1
sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html,
NONE, 1.1
sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html,
NONE,
1.1 sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html,
NONE, 1.1
sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html,
NONE,
1.1 sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html,
NONE, 1.1
sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html,
NONE, 1.1 sect-Security_Guide-Virtual_Private_Networks_VPNs.html,
NONE, 1.1
sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html,
NONE, 1.1
sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html,
NONE, 1.1 sect-Security_Guide-Vulnerability_Assessment.html, NONE, 1.1
sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html,
NONE, 1.1
sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html,
NONE, 1.1
Message-ID: <20081222155509.06A9170130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv8959
Added Files:
Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html
Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html
Security_Guide-Encryption-Data_in_Motion.html
Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html
We_Need_Feedback.html chap-Security_Guide-Encryption.html
chap-Security_Guide-General_Principles_of_Information_Security.html
chap-Security_Guide-References.html
chap-Security_Guide-Secure_Installation.html
chap-Security_Guide-Securing_Your_Network.html
chap-Security_Guide-Security_Overview.html
chap-Security_Guide-Software_Maintenance.html index.html
pref-Security_Guide-Preface.html
sect-Security_Guide-Additional_Resources-Related_Books.html
sect-Security_Guide-Additional_Resources-Related_Documentation.html
sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html
sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html
sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html
sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html
sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html
sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html
sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html
sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html
sect-Security_Guide-Attackers_and_Vulnerabilities.html
sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html
sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html
sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html
sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html
sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html
sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html
sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html
sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html
sect-Security_Guide-Common_Exploits_and_Attacks.html
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html
sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html
sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html
sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html
sect-Security_Guide-Evaluating_the_Tools-Nessus.html
sect-Security_Guide-Evaluating_the_Tools-Nikto.html
sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html
sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html
sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html
sect-Security_Guide-Firewalls-Additional_Resources.html
sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html
sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html
sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html
sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html
sect-Security_Guide-Firewalls-IPv6.html
sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html
sect-Security_Guide-Firewalls-Using_IPTables.html
sect-Security_Guide-Firewalls.html
sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.html
sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.html
sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.html
sect-Security_Guide-IPTables-Additional_Resources.html
sect-Security_Guide-IPTables-Command_Options_for_IPTables.html
sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html
sect-Security_Guide-IPTables-IPTables_Control_Scripts.html
sect-Security_Guide-IPTables-IPTables_and_IPv6.html
sect-Security_Guide-IPTables-Saving_IPTables_Rules.html
sect-Security_Guide-IPTables.html
sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html
sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html
sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html
sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html
sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html
sect-Security_Guide-Kerberos-Additional_Resources.html
sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html
sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html
sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html
sect-Security_Guide-Kerberos-How_Kerberos_Works.html
sect-Security_Guide-Kerberos-Kerberos_Terminology.html
sect-Security_Guide-Kerberos-Kerberos_and_PAM.html
sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html
sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html
sect-Security_Guide-Kerberos.html
sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html
sect-Security_Guide-LUKS_Disk_Encryption.html
sect-Security_Guide-Option_Fields-Access_Control.html
sect-Security_Guide-Option_Fields-Expansions.html
sect-Security_Guide-Option_Fields-Shell_Commands.html
sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html
sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html
sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html
sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html
sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html
sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html
sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html
sect-Security_Guide-Securing_FTP-Anonymous_Access.html
sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html
sect-Security_Guide-Securing_FTP-User_Accounts.html
sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html
sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html
sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html
sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html
sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html
sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html
sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html
sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html
sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.html
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.html
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.html
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.html
sect-Security_Guide-Security_Updates.html
sect-Security_Guide-Server_Security-Securing_FTP.html
sect-Security_Guide-Server_Security-Securing_NFS.html
sect-Security_Guide-Server_Security-Securing_NIS.html
sect-Security_Guide-Server_Security-Securing_Portmap.html
sect-Security_Guide-Server_Security-Securing_Sendmail.html
sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html
sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html
sect-Security_Guide-Server_Security.html
sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html
sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html
sect-Security_Guide-Single_Sign_on_SSO.html
sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html
sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html
sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html
sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html
sect-Security_Guide-TCP_Wrappers_and_xinetd.html
sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html
sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html
sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html
sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html
sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html
sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html
sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html
sect-Security_Guide-Virtual_Private_Networks_VPNs.html
sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html
sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html
sect-Security_Guide-Vulnerability_Assessment.html
sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html
sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html
Log Message:
Initial build in html.
--- NEW FILE Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html ---
3.6.??Secure Shell
Secure Shell (SSH) also provides encrypted tunnels between computers but only using a single port. Port forwarding can be done over an SSH tunnel and traffic will be encrypted as it passes over that tunnel but using port forwarding isn't as fluid as a VPN.
Virtual Private Networks (VPN) provide encrypted tunnels between computers or networks of computers across all ports. With a VPN in place, all network traffic from the client is forwarded to the server through the encrypted tunnel. This means that the client is logically on the same network as the server it is connected to via the VPN. VPNs are very common and are simple to use and setup.
Data in motion is data that is being transmitted over a network. The biggest threats to data in motion are interception and alteration. Your user name and password should never be transmitted over a network without protection as it could be intercepted and used by someone else to impersonate you or gain access to sensitive information. Other private information such as bank account information should also be protected when transmitted across a network. If the network session was encrypted then you would not have to worry as much about the data being compromised while it is being transmitted.
Data in motion is particularly vulnerable to attackers because the attacker does not have to be near the computer in which the data is being stored rather they only have to be somewhere along the path. Encryption tunnels can protect data along the path of communications.
GnuPG (GPG) is an open source version of PGP that allows you to sign and/or encrypt a file or an email message. This is useful to maintain integrity of the message or file and also protects the confidentiality of the information contained within the file or email. In the case of email, GPG provides dual protection. Not only can it provide Data at Rest protection but also Data In Motion protection once the message has been sent across the network.
File based encryption is intended to protect a file after it has left your computer, such as when you send a CD through the mail. Some file based encryption solutions will leave remnants of the encrypted files that an attacker who has physical access to your computer can recover under some circumstances. To protect the contents of those files from attackers who may have access to your computer, use file based encryption combined with another solution such as full disk encryption.
There are two main types of data that must be protected: data at rest and data in motion. These different types of data are protected in similar ways using similar technology but the implementations can be completely different. No single protective implementation can prevent all possible methods of compromise as the same information may be at rest and in motion at different points in time.
3.1.??Data at Rest
Data at rest is data that is stored on a hard drive, tape, CD, DVD, disk, or other media. This information's biggest threat comes from being physically stolen. Laptops in airports, CDs going through the mail, and backup tapes that get left in the wrong places are all examples of events where data can be compromised through theft. If the data was encrypted on the media then you wouldn't have to worry as much about the data being compromised.
The United States' National Security Agency (NSA) provides hardening guides and hardening tips for many different operating systems to help government agencies, businesses, and individuals help secure their system against attacks. In addition to specific settings to change, a set of general principles have been developed to give you a high level view of information security.
4.1.??General Principles
Encrypt all data transmitted over the network. Encrypting authentication information (such as passwords) is particularly important.
Minimize the amount of software installed and running in order to minimize vulnerability.
Use security-enhancing software and tools whenever available (e.g. SELinux and IPTables).
Run each network service on a separate server whenever possible. This minimizes the risk that a compromise of one service could lead to a compromise of others.
Maintain user accounts. Create a good password policy and enforce its use. Delete unused user accounts.
Review system and application logs on a routine basis. Send logs to a dedicated log server. This prevents intruders from easily avoiding detection by modifying the local logs.
Never login directly as root, unless absolutely necessary. Administrators should use sudo to execute commands as root when required. The accounts capable of using sudo are specified in /etc/sudoers, which is edited with the visudo utility. By default, relavent logs are written to /var/log/secure.
The following references are pointers to additional information that is relevant to SELinux and Fedora but beyond the scope of this guide. Note that due to the rapid development of SELinux, some of this material may only apply to specific releases of Fedora.
Books
SELinux by Example
Mayer, MacMillan, and Caplan
Prentice Hall, 2007
Tutorials and Help
Understanding and Customizing the Apache HTTP SELinux Policy
Security begins with the first time you put that CD or DVD into your disk drive to install Fedora. Configuring your system securely from the beginning makes it easier to implement additional security settings later.
5.1.??Disk Partitions
The NSA recommends creating separate partitions for /boot, /, /home, /tmp, and /var/tmp. The reasons for each are different and we will address each partition.
/boot - This partition is the first partition that is read by the system during boot up. The boot loader and kernel images that are used to boot your system into Fedora are stored in this partition. This partition should not be encrypted. If this partition is included in / and that partition is encrypted or otherwise becomes unavailable then your system will not be able to boot.
/home - When user data (/home) is stored in / instead of in a separate partition, the partition can fill up causing the operating system to become unstable. Also, when upgrading your system to the next version of Fedora it is a lot easier when you can keep your data in the /home partition as it will not be overwritten during installation. If the root partition (/) becomes corrupt your data could be lost forever. By using a separate partition there is slightly more protection against data loss. You can also target this partition for frequent backups.
/tmp and /var/tmp - Both the /tmp and the /var/tmp directories are used to store data that doesn't need to be stored for a long period of time. However if a lot of data floods one of these directories it can consume all of your storage space. If this happens and these directories are stored within / then your system could become unstable and crash. For this reason, moving these directories into their own partitions is a good idea.
Securing a Linux environment begins with the workstation. Whether locking down a personal machine or securing an enterprise system, sound security policy begins with the individual computer. A computer network is only as secure as its weakest node.
2.1.1.??Evaluating Workstation Security
When evaluating the security of a Fedora workstation, consider the following:
BIOS and Boot Loader Security ??? Can an unauthorized user physically access the machine and boot into single user or rescue mode without a password?
Password Security ??? How secure are the user account passwords on the machine?
Administrative Controls ??? Who has an account on the system and how much administrative control do they have?
Available Network Services ??? What services are listening for requests from the network and should they be running at all?
Personal Firewalls ??? What type of firewall, if any, is necessary?
Security Enhanced Communication Tools ??? Which tools should be used to communicate between workstations and which should be avoided?
2.1.2.??BIOS and Boot Loader Security
Password protection for the BIOS (or BIOS equivalent) and the boot loader can prevent unauthorized users who have physical access to systems from booting using removable media or obtaining root privileges through single user mode. The security measures you should take to protect against such attacks depends both on the sensitivity of the information on the workstation and the location of the machine.
For example, if a machine is used in a trade show and contains no sensitive information, then it may not be critical to prevent such attacks. However, if an employee's laptop with private, unencrypted SSH keys for the corporate network is left unattended at that same trade show, it could lead to a major security breach with ramifications for the entire company.
If the workstation is located in a place where only authorized or trusted people have access, however, then securing the BIOS or the boot loader may not be necessary.
2.1.2.1.??BIOS Passwords
The two primary reasons for password protecting the BIOS of a computer are[5]:
Preventing Changes to BIOS Settings ??? If an intruder has access to the BIOS, they can set it to boot from a diskette or CD-ROM. This makes it possible for them to enter rescue mode or single user mode, which in turn allows them to start arbitrary processes on the system or copy sensitive data.
Preventing System Booting ??? Some BIOSes allow password protection of the boot process. When activated, an attacker is forced to enter a password before the BIOS launches the boot loader.
Because the methods for setting a BIOS password vary between computer manufacturers, consult the computer's manual for specific instructions.
If you forget the BIOS password, it can either be reset with jumpers on the motherboard or by disconnecting the CMOS battery. For this reason, it is good practice to lock the computer case if possible. However, consult the manual for the computer or motherboard before attempting to disconnect the CMOS battery.
2.1.2.1.1.??Securing Non-x86 Platforms
Other architectures use different programs to perform low-level tasks roughly equivalent to those of the BIOS on x86 systems. For instance, Intel?? Itanium??? computers use the Extensible Firmware Interface (EFI) shell.
For instructions on password protecting BIOS-like programs on other architectures, refer to the manufacturer's instructions.
2.1.2.2.??Boot Loader Passwords
The primary reasons for password protecting a Linux boot loader are as follows:
Preventing Access to Single User Mode ??? If attackers can boot the system into single user mode, they are logged in automatically as root without being prompted for the root password.
Preventing Access to the GRUB Console ??? If the machine uses GRUB as its boot loader, an attacker can use the GRUB editor interface to change its configuration or to gather information using the cat command.
Preventing Access to Insecure Operating Systems ??? If it is a dual-boot system, an attacker can select an operating system at boot time (for example, DOS), which ignores access controls and file permissions.
Fedora ships with the GRUB boot loader on the x86 platform. For a detailed look at GRUB, refer to the Red Hat Installation Guide.
2.1.2.2.1.??Password Protecting GRUB
You can configure GRUB to address the first two issues listed in Section??2.1.2.2, ???Boot Loader Passwords??? by adding a password directive to its configuration file. To do this, first choose a strong password, open a shell, log in as root, and then type the following command:
/sbin/grub-md5-crypt
When prompted, type the GRUB password and press Enter. This returns an MD5 hash of the password.
Next, edit the GRUB configuration file /boot/grub/grub.conf. Open the file and below the timeout line in the main section of the document, add the following line:
password --md5 <password-hash>
Replace <password-hash> with the value returned by /sbin/grub-md5-crypt[6].
The next time the system boots, the GRUB menu prevents access to the editor or command interface without first pressing p followed by the GRUB password.
Unfortunately, this solution does not prevent an attacker from booting into an insecure operating system in a dual-boot environment. For this, a different part of the /boot/grub/grub.conf file must be edited.
Look for the title line of the operating system that you want to secure, and add a line with the lock directive immediately beneath it.
For a DOS system, the stanza should begin similar to the following:
title DOS lock
Warning
A password line must be present in the main section of the /boot/grub/grub.conf file for this method to work properly. Otherwise, an attacker can access the GRUB editor interface and remove the lock line.
To create a different password for a particular kernel or operating system, add a lock line to the stanza, followed by a password line.
Each stanza protected with a unique password should begin with lines similar to the following example:
title DOS lock password --md5 <password-hash>
2.1.3.??Password Security
Passwords are the primary method that Fedora uses to verify a user's identity. This is why password security is so important for protection of the user, the workstation, and the network.
For security purposes, the installation program configures the system to use Message-Digest Algorithm (MD5) and shadow passwords. It is highly recommended that you do not alter these settings.
If MD5 passwords are deselected during installation, the older Data Encryption Standard (DES) format is used. This format limits passwords to eight alphanumeric characters (disallowing punctuation and other special characters), and provides a modest 56-bit level of encryption.
If shadow passwords are deselected during installation, all passwords are stored as a one-way hash in the world-readable /etc/passwd file, which makes the system vulnerable to offline password cracking attacks. If an intruder can gain access to the machine as a regular user, he can copy the /etc/passwd file to his own machine and run any number of password cracking programs against it. If there is an insecure password in the file, it is only a matter of time before the password cracker discovers it.
Shadow passwords eliminate this type of attack by storing the password hashes in the file /etc/shadow, which is readable only by the root user.
This forces a potential attacker to attempt password cracking remotely by logging into a network service on the machine, such as SSH or FTP. This sort of brute-force attack is much slower and leaves an obvious trail as hundreds of failed login attempts are written to system files. Of course, if the cracker starts an attack in the middle of the night on a system with weak passwords, the cracker may have gained access before dawn and edited the log files to cover his tracks.
In addition to format and storage considerations is the issue of content. The single most important thing a user can do to protect his account against a password cracking attack is create a strong password.
2.1.3.1.??Creating Strong Passwords
When creating a secure password, it is a good idea to follow these guidelines:
Do Not Use Only Words or Numbers ??? Never use only numbers or words in a password.
Some insecure examples include the following:
8675309
juan
hackme
Do Not Use Recognizable Words ??? Words such as proper names, dictionary words, or even terms from television shows or novels should be avoided, even if they are bookended with numbers.
Some insecure examples include the following:
john1
DS-9
mentat123
Do Not Use Words in Foreign Languages ??? Password cracking programs often check against word lists that encompass dictionaries of many languages. Relying on foreign languages for secure passwords is not secure.
Some insecure examples include the following:
cheguevara
bienvenido1
1dumbKopf
Do Not Use Hacker Terminology ??? If you think you are elite because you use hacker terminology ??? also called l337 (LEET) speak ??? in your password, think again. Many word lists include LEET speak.
Some insecure examples include the following:
H4X0R
1337
Do Not Use Personal Information ??? Avoid using any personal information in your passwords. If the attacker knows your identity, the task of deducing your password becomes easier. The following is a list of the types of information to avoid when creating a password:
Some insecure examples include the following:
Your name
The names of pets
The names of family members
Any birth dates
Your phone number or zip code
Do Not Invert Recognizable Words ??? Good password checkers always reverse common words, so inverting a bad password does not make it any more secure.
Some insecure examples include the following:
R0X4H
nauj
9-DS
Do Not Write Down Your Password ??? Never store a password on paper. It is much safer to memorize it.
Do Not Use the Same Password For All Machines ??? It is important to make separate passwords for each machine. This way if one system is compromised, all of your machines are not immediately at risk.
The following guidelines will help you to create a strong password:
Make the Password at Least Eight Characters Long ??? The longer the password, the better. If using MD5 passwords, it should be 15 characters or longer. With DES passwords, use the maximum length (eight characters).
Mix Upper and Lower Case Letters ??? Fedora is case sensitive, so mix cases to enhance the strength of the password.
Mix Letters and Numbers ??? Adding numbers to passwords, especially when added to the middle (not just at the beginning or the end), can enhance password strength.
Include Non-Alphanumeric Characters ??? Special characters such as &, $, and > can greatly improve the strength of a password (this is not possible if using DES passwords).
Pick a Password You Can Remember ??? The best password in the world does little good if you cannot remember it; use acronyms or other mnemonic devices to aid in memorizing passwords.
With all these rules, it may seem difficult to create a password that meets all of the criteria for good passwords while avoiding the traits of a bad one. Fortunately, there are some steps you can take to generate an easily-remembered, secure password.
2.1.3.1.1.??Secure Password Creation Methodology
There are many methods that people use to create secure passwords. One of the more popular methods involves acronyms. For example:
Think of an easily-remembered phrase, such as:
"over the river and through the woods, to grandmother's house we go."
Next, turn it into an acronym (including the punctuation).
otrattw,tghwg.
Add complexity by substituting numbers and symbols for letters in the acronym. For example, substitute 7 for t and the at symbol (@) for a:
o7r at 77w,7ghwg.
Add more complexity by capitalizing at least one letter, such as H.
o7r at 77w,7gHwg.
Finally, do not use the example password above for any systems, ever.
While creating secure passwords is imperative, managing them properly is also important, especially for system administrators within larger organizations. The following section details good practices for creating and managing user passwords within an organization.
2.1.3.2.??Creating User Passwords Within an Organization
If an organization has a large number of users, the system administrators have two basic options available to force the use of good passwords. They can create passwords for the user, or they can let users create their own passwords, while verifying the passwords are of acceptable quality.
Creating the passwords for the users ensures that the passwords are good, but it becomes a daunting task as the organization grows. It also increases the risk of users writing their passwords down.
For these reasons, most system administrators prefer to have the users create their own passwords, but actively verify that the passwords are good and, in some cases, force users to change their passwords periodically through password aging.
2.1.3.2.1.??Forcing Strong Passwords
To protect the network from intrusion it is a good idea for system administrators to verify that the passwords used within an organization are strong ones. When users are asked to create or change passwords, they can use the command line application passwd, which is Pluggable Authentication Manager (PAM) aware and therefore checks to see if the password is too short or otherwise easy to crack. This check is performed using the pam_cracklib.so PAM module. Since PAM is customizable, it is possible to add more password integrity checkers, such as pam_passwdqc (available from http://www.openwall.com/passwdqc/) or to write a new module. For a list of available PAM modules, refer to http://www.kernel.org/pub/linux/libs/pam/mod
ules.html. For more information about PAM, refer to Section??2.4, ???Pluggable Authentication Modules (PAM)???.
The password check that is performed at the time of their creation does not discover bad passwords as effectively as running a password cracking program against the passwords.
Many password cracking programs are available that run under Fedora, although none ship with the operating system. Below is a brief list of some of the more popular password cracking programs:
Note
None of these tools are supplied with Fedora and are therefore not supported by Fedora. in any way.
John The Ripper ??? A fast and flexible password cracking program. It allows the use of multiple word lists and is capable of brute-force password cracking. It is available online at http://www.openwall.com/john/.
Crack ??? Perhaps the most well known password cracking software, Crack is also very fast, though not as easy to use as John The Ripper. It can be found online at http://www.crypticide.com/users/alecm/.
Slurpie ??? Slurpie is similar to John The Ripper and Crack, but it is designed to run on multiple computers simultaneously, creating a distributed password cracking attack. It can be found along with a number of other distributed attack security evaluation tools online at http://www.ussrback.com/distributed.htm.
Warning
Always get authorization in writing before attempting to crack passwords within an organization.
2.1.3.2.2.??Password Aging
Password aging is another technique used by system administrators to defend against bad passwords within an organization. Password aging means that after a specified period (usually 90 days), the user is prompted to create a new password. The theory behind this is that if a user is forced to change his password periodically, a cracked password is only useful to an intruder for a limited amount of time. The downside to password aging, however, is that users are more likely to write their passwords down.
There are two primary programs used to specify password aging under Fedora: the chage command or the graphical User Manager (system-config-users) application.
The -M option of the chage command specifies the maximum number of days the password is valid. For example, to set a user's password to expire in 90 days, use the following command:
chage -M 90 <username>
In the above command, replace <username> with the name of the user. To disable password expiration, it is traditional to use a value of 99999 after the -M option (this equates to a little over 273 years).
You can also use the chage command in interactive mode to modify multiple password aging and account details. Use the following command to enter interactive mode:
chage <username>
The following is a sample interactive session using this command:
[root at interch-dev1 ~]# chage davido Changing the aging information for davido Enter the new value, or press ENTER for the default Minimum Password Age [0]: 10 Maximum Password Age [99999]: 90 Last Password Change (YYYY-MM-DD) [2006-08-18]: Password Expiration Warning [7]: Password Inactive [-1]: Account Expiration Date (YYYY-MM-DD) [1969-12-31]: [root at interch-dev1 ~]#
Refer to the man page for chage for more information on the available options.
You can also use the graphical User Manager application to create password aging policies, as follows. Note: you need Administrator privileges to perform this procedure.
Click the System menu on the Panel, point to Administration and then click Users and Groups to display the User Manager. Alternatively, type the command system-config-users at a shell prompt.
Click the Users tab, and select the required user in the list of users.
Click Properties on the toolbar to display the User Properties dialog box (or choose Properties on the File menu).
Click the Password Info tab, and select the check box for Enable password expiration.
Enter the required value in the Days before change required field, and click OK.
Password Info pane illustration.
Figure??2.1.??Specifying password aging options
2.1.4.??Administrative Controls
When administering a home machine, the user must perform some tasks as the root user or by acquiring effective root privileges via a setuid program, such as sudo or su. A setuid program is one that operates with the user ID (UID) of the program's owner rather than the user operating the program. Such programs are denoted by an s in the owner section of a long format listing, as in the following example:
-rwsr-xr-x 1 root root 47324 May 1 08:09 /bin/su
Note
The s may be upper case or lower case. If it appears as upper case, it means that the underlying permission bit has not been set.
For the system administrators of an organization, however, choices must be made as to how much administrative access users within the organization should have to their machine. Through a PAM module called pam_console.so, some activities normally reserved only for the root user, such as rebooting and mounting removable media are allowed for the first user that logs in at the physical console (refer to Section??2.4, ???Pluggable Authentication Modules (PAM)??? for more information about the pam_console.so module.) However, other important system administration tasks, such as altering network settings, configuring a new mouse, or mounting network devices, are not possible without administrative privileges. As a result, system administrators must decide how much access the users
on their network should receive.
2.1.4.1.??Allowing Root Access
If the users within an organization are trusted and computer-literate, then allowing them root access may not be an issue. Allowing root access by users means that minor activities, like adding devices or configuring network interfaces, can be handled by the individual users, leaving system administrators free to deal with network security and other important issues.
On the other hand, giving root access to individual users can lead to the following issues:
Machine Misconfiguration ??? Users with root access can misconfigure their machines and require assistance to resolve issues. Even worse, they might open up security holes without knowing it.
Running Insecure Services ??? Users with root access might run insecure servers on their machine, such as FTP or Telnet, potentially putting usernames and passwords at risk. These services transmit this information over the network in plain text.
Running Email Attachments As Root ??? Although rare, email viruses that affect Linux do exist. The only time they are a threat, however, is when they are run by the root user.
2.1.4.2.??Disallowing Root Access
If an administrator is uncomfortable allowing users to log in as root for these or other reasons, the root password should be kept secret, and access to runlevel one or single user mode should be disallowed through boot loader password protection (refer to Section??2.1.2.2, ???Boot Loader Passwords??? for more information on this topic.)
Table??2.1.??Methods of Disabling the Root Account
2.1.4.2.1.??Disabling the Root Shell
To prevent users from logging in directly as root, the system administrator can set the root account's shell to /sbin/nologin in the /etc/passwd file. This prevents access to the root account through commands that require a shell, such as the su and the ssh commands.
Important
Programs that do not require access to the shell, such as email clients or the sudo command, can still access the root account.
2.1.4.2.2.??Disabling Root Logins
To further limit access to the root account, administrators can disable root logins at the console by editing the /etc/securetty file. This file lists all devices the root user is allowed to log into. If the file does not exist at all, the root user can log in through any communication device on the system, whether via the console or a raw network interface. This is dangerous, because a user can log in to his machine as root via Telnet, which transmits the password in plain text over the network. By default, Fedora's /etc/securetty file only allows the root user to log in at the console physically attached to the machine. To prevent root from logging in, remove the contents of this file by typing the following command:
echo > /etc/securetty
Warning
A blank /etc/securetty file does not prevent the root user from logging in remotely using the OpenSSH suite of tools because the console is not opened until after authentication.
2.1.4.2.3.??Disabling Root SSH Logins
To prevent root logins via the SSH protocol, edit the SSH daemon's configuration file (/etc/ssh/sshd_config). Change the line that reads:
# PermitRootLogin yes
to read as follows:
PermitRootLogin no
2.1.4.2.4.??Disabling Root Using PAM
PAM, through the /lib/security/pam_listfile.so module, allows great flexibility in denying specific accounts. The administrator can use this module to reference a list of users who are not allowed to log in. Below is an example of how the module is used for the vsftpd FTP server in the /etc/pam.d/vsftpd PAM configuration file (the \ character at the end of the first line in the following example is not necessary if the directive is on one line):
This instructs PAM to consult the /etc/vsftpd.ftpusers file and deny access to the service for any listed user. The administrator can change the name of this file, and can keep separate lists for each service or use one central list to deny access to multiple services.
If the administrator wants to deny access to multiple services, a similar line can be added to the PAM configuration files, such as /etc/pam.d/pop and /etc/pam.d/imap for mail clients, or /etc/pam.d/ssh for SSH clients.
Rather than completely denying access to the root user, the administrator may want to allow access only via setuid programs, such as su or sudo.
2.1.4.3.1.??The su Command
When a user executes the su command, they are prompted for the root password and, after authentication, is given a root shell prompt.
Once logged in via the su command, the user is the root user and has absolute administrative access to the system[7]. In addition, once a user has become root, it is possible for them to use the su command to change to any other user on the system without being prompted for a password.
Because this program is so powerful, administrators within an organization may wish to limit who has access to the command.
One of the simplest ways to do this is to add users to the special administrative group called wheel. To do this, type the following command as root:
usermod -G wheel <username>
In the previous command, replace <username> with the username you want to add to the wheel group.
You can also use the User Manager to modify group memberships, as follows. Note: you need Administrator privileges to perform this procedure.
Click the System menu on the Panel, point to Administration and then click Users and Groups to display the User Manager. Alternatively, type the command system-config-users at a shell prompt.
Click the Users tab, and select the required user in the list of users.
Click Properties on the toolbar to display the User Properties dialog box (or choose Properties on the File menu).
This change means that only members of the administrative group wheel can use this program.
Groups pane illustration
Figure??2.2.??Adding users to the "wheel" group.
Note
The root user is part of the wheel group by default.
2.1.4.3.2.??The sudo Command
The sudo command offers another approach to giving users administrative access. When trusted users precede an administrative command with sudo, they are prompted for their own password. Then, when they have been authenticated and assuming that the command is permitted, the administrative command is executed as if they were the root user.
The basic format of the sudo command is as follows:
sudo <command>
In the above example, <command> would be replaced by a command normally reserved for the root user, such as mount.
Important
Users of the sudo command should take extra care to log out before walking away from their machines since sudoers can use the command again without being asked for a password within a five minute period. This setting can be altered via the configuration file, /etc/sudoers.
The sudo command allows for a high degree of flexibility. For instance, only users listed in the /etc/sudoers configuration file are allowed to use the sudo command and the command is executed in the user's shell, not a root shell. This means the root shell can be completely disabled, as shown in Section??2.1.4.2.1, ???Disabling the Root Shell???.
The sudo command also provides a comprehensive audit trail. Each successful authentication is logged to the file /var/log/messages and the command issued along with the issuer's user name is logged to the file /var/log/secure.
Another advantage of the sudo command is that an administrator can allow different users access to specific commands based on their needs.
Administrators wanting to edit the sudo configuration file, /etc/sudoers, should use the visudo command.
To give someone full administrative privileges, type visudo and add a line similar to the following in the user privilege specification section:
juan ALL=(ALL) ALL
This example states that the user, juan, can use sudo from any host and execute any command.
The example below illustrates the granularity possible when configuring sudo:
%users localhost=/sbin/shutdown -h now
This example states that any user can issue the command /sbin/shutdown -h now as long as it is issued from the console.
The man page for sudoers has a detailed listing of options for this file.
2.1.5.??Available Network Services
While user access to administrative controls is an important issue for system administrators within an organization, monitoring which network services are active is of paramount importance to anyone who administers and operates a Linux system.
Many services under Fedora behave as network servers. If a network service is running on a machine, then a server application (called a daemon), is listening for connections on one or more network ports. Each of these servers should be treated as a potential avenue of attack.
2.1.5.1.??Risks To Services
Network services can pose many risks for Linux systems. Below is a list of some of the primary issues:
Denial of Service Attacks (DoS) ??? By flooding a service with requests, a denial of service attack can render a system unusable as it tries to log and answer each request.
Script Vulnerability Attacks ??? If a server is using scripts to execute server-side actions, as Web servers commonly do, a cracker can attack improperly written scripts. These script vulnerability attacks can lead to a buffer overflow condition or allow the attacker to alter files on the system.
Buffer Overflow Attacks ??? Services that connect to ports numbered 0 through 1023 must run as an administrative user. If the application has an exploitable buffer overflow, an attacker could gain access to the system as the user running the daemon. Because exploitable buffer overflows exist, crackers use automated tools to identify systems with vulnerabilities, and once they have gained access, they use automated rootkits to maintain their access to the system.
Note
The threat of buffer overflow vulnerabilities is mitigated in Fedora by ExecShield, an executable memory segmentation and protection technology supported by x86-compatible uni- and multi-processor kernels. ExecShield reduces the risk of buffer overflow by separating virtual memory into executable and non-executable segments. Any program code that tries to execute outside of the executable segment (such as malicious code injected from a buffer overflow exploit) triggers a segmentation fault and terminates.
Execshield also includes support for No eXecute (NX) technology on AMD64 platforms and eXecute Disable (XD) technology on Itanium and Intel?? 64 systems. These technologies work in conjunction with ExecShield to prevent malicious code from running in the executable portion of virtual memory with a granularity of 4KB of executable code, lowering the risk of attack from stealthy buffer overflow exploits.
Tip
To limit exposure to attacks over the network, all services that are unused should be turned off.
2.1.5.2.??Identifying and Configuring Services
To enhance security, most network services installed with Fedora are turned off by default. There are, however, some notable exceptions:
cupsd ??? The default print server for Fedora.
lpd ??? An alternative print server.
xinetd ??? A super server that controls connections to a range of subordinate servers, such as gssftp and telnet.
sendmail ??? The Sendmail Mail Transport Agent (MTA) is enabled by default, but only listens for connections from the localhost.
sshd ??? The OpenSSH server, which is a secure replacement for Telnet.
When determining whether to leave these services running, it is best to use common sense and err on the side of caution. For example, if a printer is not available, do not leave cupsd running. The same is true for portmap. If you do not mount NFSv3 volumes or use NIS (the ypbind service), then portmap should be disabled.
Services Configuration Tool illustration
Figure??2.3.??Services Configuration Tool
If unsure of the purpose for a particular service, the Services Configuration Tool has a description field, illustrated in Figure??2.3, ???Services Configuration Tool???, that provides additional information.
Checking which network services are available to start at boot time is only part of the story. You should also check which ports are open and listening. Refer to Section??2.2.8, ???Verifying Which Ports Are Listening??? for more information.
2.1.5.3.??Insecure Services
Potentially, any network service is insecure. This is why turning off unused services is so important. Exploits for services are routinely revealed and patched, making it very important to regularly update packages associated with any network service. Refer to Section??1.5, ???Security Updates??? for more information.
Some network protocols are inherently more insecure than others. These include any services that:
Transmit Usernames and Passwords Over a Network Unencrypted ??? Many older protocols, such as Telnet and FTP, do not encrypt the authentication session and should be avoided whenever possible.
Transmit Sensitive Data Over a Network Unencrypted ??? Many protocols transmit data over the network unencrypted. These protocols include Telnet, FTP, HTTP, and SMTP. Many network file systems, such as NFS and SMB, also transmit information over the network unencrypted. It is the user's responsibility when using these protocols to limit what type of data is transmitted.
Remote memory dump services, like netdump, transmit the contents of memory over the network unencrypted. Memory dumps can contain passwords or, even worse, database entries and other sensitive information.
Other services like finger and rwhod reveal information about users of the system.
Examples of inherently insecure services include rlogin, rsh, telnet, and vsftpd.
FTP is not as inherently dangerous to the security of the system as remote shells, but FTP servers must be carefully configured and monitored to avoid problems. Refer to Section??2.2.6, ???Securing FTP??? for more information about securing FTP servers.
Services that should be carefully implemented and behind a firewall include:
finger
authd (this was called identd in previous Fedora releases.)
The next section discusses tools available to set up a simple firewall.
2.1.6.??Personal Firewalls
After the necessary network services are configured, it is important to implement a firewall.
Important
You should configure the necessary services and implement a firewall before connecting to the Internet or any other network that you do not trust.
Firewalls prevent network packets from accessing the system's network interface. If a request is made to a port that is blocked by a firewall, the request is ignored. If a service is listening on one of these blocked ports, it does not receive the packets and is effectively disabled. For this reason, care should be taken when configuring a firewall to block access to ports not in use, while not blocking access to ports used by configured services.
For most users, the best tool for configuring a simple firewall is the graphical firewall configuration tool which ships with Fedora: the Security Level Configuration Tool (system-config-securitylevel). This tool creates broad iptables rules for a general-purpose firewall using a control panel interface.
For advanced users and server administrators, manually configuring a firewall with iptables is probably a better option. Refer to Section??2.8, ???Firewalls??? for more information. Refer to Section??2.9, ???IPTables??? for a comprehensive guide to the iptables command.
2.1.7.??Security Enhanced Communication Tools
As the size and popularity of the Internet has grown, so has the threat of communication interception. Over the years, tools have been developed to encrypt communications as they are transferred over the network.
Fedora ships with two basic tools that use high-level, public-key-cryptography-based encryption algorithms to protect information as it travels over the network.
OpenSSH ??? A free implementation of the SSH protocol for encrypting network communication.
Gnu Privacy Guard (GPG) ??? A free implementation of the PGP (Pretty Good Privacy) encryption application for encrypting data.
OpenSSH is a safer way to access a remote machine and replaces older, unencrypted services like telnet and rsh. OpenSSH includes a network service called sshd and three command line client applications:
ssh ??? A secure remote console access client.
scp ??? A secure remote copy command.
sftp ??? A secure pseudo-ftp client that allows interactive file transfer sessions.
Important
Although the sshd service is inherently secure, the service must be kept up-to-date to prevent security threats. Refer to Section??1.5, ???Security Updates??? for more information.
GPG is one way to ensure private email communication. It can be used both to email sensitive data over public networks and to protect sensitive data on hard drives.
[5]
Since system BIOSes differ between manufacturers, some may not support password protection of either type, while others may support one type but not the other.
[6]
GRUB also accepts unencrypted passwords, but it is recommended that an MD5 hash be used for added security.
[7]
This access is still subject to the restrictions imposed by SELinux, if it is enabled.
Because of the increased reliance on powerful, networked computers to help run businesses and keep track of our personal information, industries have been formed around the practice of network and computer security. Enterprises have solicited the knowledge and skills of security experts to properly audit systems and tailor solutions to fit the operating requirements of the organization. Because most organizations are dynamic in nature, with workers accessing company IT resources locally and remotely, the need for secure computing environments has become more pronounced.
Unfortunately, most organizations (as well as individual users) regard security as an afterthought, a process that is overlooked in favor of increased power, productivity, and budgetary concerns. Proper security implementation is often enacted postmortem ??? after an unauthorized intrusion has already occurred. Security experts agree that the right measures taken prior to connecting a site to an untrusted network, such as the Internet, is an effective means of thwarting most attempts at intrusion.
1.1.??Introduction to Security
1.1.1.??What is Computer Security?
Computer security is a general term that covers a wide area of computing and information processing. Industries that depend on computer systems and networks to conduct daily business transactions and access crucial information regard their data as an important part of their overall assets. Several terms and metrics have entered our daily business vocabulary, such as total cost of ownership (TCO) and quality of service (QoS). In these metrics, industries calculate aspects such as data integrity and high-availability as part of their planning and process management costs. In some industries, such as electronic commerce, the availability and trustworthiness of data can be the difference between success and failure.
1.1.1.1.??How did Computer Security Come about?
Information security has evolved over the years due to the increasing reliance on public networks not to disclose personal, financial, and other restricted information. There are numerous instances such as the Mitnick and the Vladimir Levin cases that prompted organizations across all industries to rethink the way they handle information transmission and disclosure. The popularity of the Internet was one of the most important developments that prompted an intensified effort in data security.
An ever-growing number of people are using their personal computers to gain access to the resources that the Internet has to offer. From research and information retrieval to electronic mail and commerce transaction, the Internet has been regarded as one of the most important developments of the 20th century.
The Internet and its earlier protocols, however, were developed as a trust-based system. That is, the Internet Protocol was not designed to be secure in itself. There are no approved security standards built into the TCP/IP communications stack, leaving it open to potentially malicious users and processes across the network. Modern developments have made Internet communication more secure, but there are still several incidents that gain national attention and alert us to the fact that nothing is completely safe.
1.1.1.2.??Security Today
In February of 2000, a Distributed Denial of Service (DDoS) attack was unleashed on several of the most heavily-trafficked sites on the Internet. The attack rendered yahoo.com, cnn.com, amazon.com, fbi.gov, and several other sites completely unreachable to normal users, as it tied up routers for several hours with large-byte ICMP packet transfers, also called a ping flood. The attack was brought on by unknown assailants using specially created, widely available programs that scanned vulnerable network servers, installed client applications called trojans on the servers, and timed an attack with every infected server flooding the victim sites and rendering them unavailable. Many blame the attack on fundamental flaws in the way routers and the protocols used are structured to accept all incoming data, no matter where or for what purpose the packets are sent.
Currently, an estimated 945 million people use or have used the Internet worldwide (Computer Industry Almanac, 2004). At the same time:
On any given day, there are approximately 225 major incidences of security breach reported to the CERT Coordination Center at Carnegie Mellon University.[1]
In 2003, the number of CERT reported incidences jumped to 137,529 from 82,094 in 2002 and from 52,658 in 2001.[2]
The worldwide economic impact of the three most dangerous Internet Viruses of the last three years was estimated at US$13.2 Billion.[3]
Computer security has become a quantifiable and justifiable expense for all IT budgets. Organizations that require data integrity and high availability elicit the skills of system administrators, developers, and engineers to ensure 24x7 reliability of their systems, services, and information. Falling victim to malicious users, processes, or coordinated attacks is a direct threat to the success of the organization.
Unfortunately, system and network security can be a difficult proposition, requiring an intricate knowledge of how an organization regards, uses, manipulates, and transmits its information. Understanding the way an organization (and the people that make up the organization) conducts business is paramount to implementing a proper security plan.
1.1.1.3.??Standardizing Security
Enterprises in every industry rely on regulations and rules that are set by standards making bodies such as the American Medical Association (AMA) or the Institute of Electrical and Electronics Engineers (IEEE). The same ideals hold true for information security. Many security consultants and vendors agree upon the standard security model known as CIA, or Confidentiality, Integrity, and Availability. This three-tiered model is a generally accepted component to assessing risks of sensitive information and establishing security policy. The following describes the CIA model in further detail:
Confidentiality ??? Sensitive information must be available only to a set of pre-defined individuals. Unauthorized transmission and usage of information should be restricted. For example, confidentiality of information ensures that a customer's personal or financial information is not obtained by an unauthorized individual for malicious purposes such as identity theft or credit fraud.
Integrity ??? Information should not be altered in ways that render it incomplete or incorrect. Unauthorized users should be restricted from the ability to modify or destroy sensitive information.
Availability ??? Information should be accessible to authorized users any time that it is needed. Availability is a warranty that information can be obtained with an agreed-upon frequency and timeliness. This is often measured in terms of percentages and agreed to formally in Service Level Agreements (SLAs) used by network service providers and their enterprise clients.
1.1.2.??Security Controls
Computer security is often divided into three distinct master categories, commonly referred to as controls:
Physical
Technical
Administrative
These three broad categories define the main objectives of proper security implementation. Within these controls are sub-categories that further detail the controls and how to implement them.
1.1.2.1.??Physical Controls
Physical control is the implementation of security measures in a defined structure used to deter or prevent unauthorized access to sensitive material. Examples of physical controls are:
Closed-circuit surveillance cameras
Motion or thermal alarm systems
Security guards
Picture IDs
Locked and dead-bolted steel doors
Biometrics (includes fingerprint, voice, face, iris, handwriting, and other automated methods used to recognize individuals)
1.1.2.2.??Technical Controls
Technical controls use technology as a basis for controlling the access and usage of sensitive data throughout a physical structure and over a network. Technical controls are far-reaching in scope and encompass such technologies as:
Encryption
Smart cards
Network authentication
Access control lists (ACLs)
File integrity auditing software
1.1.2.3.??Administrative Controls
Administrative controls define the human factors of security. It involves all levels of personnel within an organization and determines which users have access to what resources and information by such means as:
Training and awareness
Disaster preparedness and recovery plans
Personnel recruitment and separation strategies
Personnel registration and accounting
1.1.3.??Conclusion
Now that you have learned about the origins, reasons, and aspects of security, you can determine the appropriate course of action with regard to Fedora. It is important to know what factors and conditions make up security in order to plan and implement a proper strategy. With this information in mind, the process can be formalized and the path becomes clearer as you delve deeper into the specifics of the security process.
Software maintenance is extremely important to maintaining a secure system. It is vital to patch software as soon as it becomes available in order to prevent attackers from using known holes to infiltrate your system.
6.1.??Install Minimal Software
It is best practice to install only the packages you will use because each piece of software on your computer could possibly contain a vulnerability. If you are installing from the DVD media take the opportunity to select exactly what packages you want to install during the installation. When you find you need another package, you can always add it to the system later.
Copyright ?? 2008 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0, (the latest version is presently available at http://www.opencontent.org/openpub/).
Fedora and the Fedora Infinity Design logo are trademarks or registered trademarks of Red Hat, Inc., in the U.S. and other countries.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat Inc. in the United States and other countries.
All other trademarks and copyrights referred to are the property of their respective owners.
The Linux Security Guide is designed to assist users of Linux in
learning the processes and practices of securing workstations and
servers against local and remote intrusion, exploitation, and
malicious activity. The Linux Security Guide details the planning
and the tools involved in creating a secured computing environment
for the data center, workplace, and home. With proper
administrative knowledge, vigilance, and tools, systems running
Linux can be both fully functional and secured from most common
intrusion and exploit methods.
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
1.1.??Typographic Conventions
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight key caps and key-combinations. For example:
To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context.
Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key-combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F1 to switch to the first virtual terminal. Press Ctrl+Alt+F7 to return to your X-Windows session.
The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in Mono-spaced Bold. For example:
File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialogue box text; labelled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
Choose System > Preferences > Mouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, click the Left-handed mouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
To insert a special character into a gedit file, choose Applications > Accessories > Character Map from the main menu bar. Next, choose Search > Find??? from the Character Map menu bar, type the name of the character in the Search field and click Next. The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose Edit > Paste from the <
span class="application">gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in Proportional Bold and all distinguishable by context.
Note the > shorthand used to indicate traversal through a menu and its sub-menus. This is to avoid the difficult-to-follow 'Select Mouse from the Preferences sub-menu in the System menu of the main menu bar' approach.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether Mono-spaced Bold or Proportional Bold, the addition of Italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john at example.com.
The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home.
To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release.
Note the words in bold italics above ??? username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a server-pool. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called Multi-Processing Modules (MPMs). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server.
1.2.??Pull-quote Conventions
Two, commonly multi-line, data types are set off visually from the surrounding text.
Output sent to a terminal is set in Mono-spaced Roman and presented thus:
Source-code listings are also set in Mono-spaced Roman but are presented and highlighted as follows:
package org.jboss.book.jca.ex1;
import javax.naming.InitialContext;
public class ExClient
{
public static void main(String args[])
throws Exception
{
InitialContext iniCtx = new InitialContext();
Object ref = iniCtx.lookup("EchoBean");
EchoHome home = (EchoHome) ref;
Echo echo = home.create();
System.out.println("Created Echo");
System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
}
}
1.3.??Notes and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
Note
A note is a tip or shortcut or alternative approach to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring Important boxes won't cause data loss but may cause irritation and frustration.
Warning
A Warning should not be ignored. Ignoring warnings will most likely cause data loss.
Hacking Linux Exposed by Brian Hatch, James Lee, and George Kurtz; Osbourne/McGraw-Hill ??? An excellent security resource with information about TCP Wrappers and xinetd.
Red Hat Linux Firewalls, by Bill McCarty; Red Hat Press ??? a comprehensive reference to building network and server firewalls using open source packet filtering technology such as Netfilter and iptables. It includes topics that cover analyzing firewall logs, developing firewall rules, and customizing your firewall using various graphical tools.
Linux Firewalls, by Robert Ziegler; New Riders Press ??? contains a wealth of information on building firewalls using both 2.2 kernel ipchains as well as Netfilter and iptables. Additional security topics such as remote access issues and intrusion detection systems are also covered.
http://www.netfilter.org/ ??? The home of the netfilter/iptables project. Contains assorted information about iptables, including a FAQ addressing specific problems and various helpful guides by Rusty Russell, the Linux IP firewall maintainer. The HOWTO documents on the site cover subjects such as basic networking concepts, kernel packet filtering, and NAT configurations.
ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.PS ??? The PostScript version of Kerberos: An Authentication Service for Open Network Systems by Jennifer G. Steiner, Clifford Neuman, and Jeffrey I. Schiller. This document is the original paper describing Kerberos.
http://web.mit.edu/kerberos/www/dialogue.html ??? Designing an Authentication System: a Dialogue in Four Scenes originally by Bill Bryant in 1988, modified by Theodore Ts'o in 1997. This document is a conversation between two developers who are thinking through the creation of a Kerberos-style authentication system. The conversational style of the discussion make this a good starting place for people who are completely unfamiliar with Kerberos.
http://www.kernel.org/pub/linux/libs/pam/ ??? The primary distribution website for the Linux-PAM project, containing information on various PAM modules, a FAQ, and additional PAM documentation.
Note
The documentation in the above website is for the last released upstream version of PAM and might not be 100% accurate for the PAM version included in Fedora.
Users of xinetd services can choose to use the TCP Wrappers hosts access rules, provide access control via the xinetd configuration files, or a mixture of both. Refer to Section??2.5.2, ???TCP Wrappers Configuration Files??? for more information about TCP Wrappers hosts access control files.
This section discusses using xinetd to control access to services.
Note
Unlike TCP Wrappers, changes to access control only take effect if the xinetd administrator restarts the xinetd service.
Also, unlike TCP Wrappers, access control through xinetd only affects services controlled by xinetd.
The xinetd hosts access control differs from the method used by TCP Wrappers. While TCP Wrappers places all of the access configuration within two files, /etc/hosts.allow and /etc/hosts.deny, xinetd's access control is found in each service's configuration file in the /etc/xinetd.d/ directory.
The following hosts access options are supported by xinetd:
only_from ??? Allows only the specified hosts to use the service.
no_access ??? Blocks listed hosts from using the service.
access_times ??? Specifies the time range when a particular service may be used. The time range must be stated in 24-hour format notation, HH:MM-HH:MM.
The only_from and no_access options can use a list of IP addresses or host names, or can specify an entire network. Like TCP Wrappers, combining xinetd access control with the enhanced logging configuration can increase security by blocking requests from banned hosts while verbosely recording each connection attempt.
For example, the following /etc/xinetd.d/telnet file can be used to block Telnet access from a particular network group and restrict the overall time range that even allowed users can log in:
service telnet
{
disable = no
flags = REUSE
socket_type = stream
wait = no
user = root
server = /usr/kerberos/sbin/telnetd
log_on_failure += USERID
no_access = 172.16.45.0/24
log_on_success += PID HOST EXIT
access_times = 09:45-16:15
}
In this example, when a client system from the 10.0.1.0/24 network, such as 10.0.1.2, tries to access the Telnet service, it receives the following message:
Connection closed by foreign host.
In addition, their login attempts are logged in /var/log/messages as follows:
When using TCP Wrappers in conjunction with xinetd access controls, it is important to understand the relationship between the two access control mechanisms.
The following is the sequence of events followed by xinetd when a client requests a connection:
The xinetd daemon accesses the TCP Wrappers hosts access rules using a libwrap.a library call. If a deny rule matches the client, the connection is dropped. If an allow rule matches the client, the connection is passed to xinetd.
The xinetd daemon checks its own access control rules both for the xinetd service and the requested service. If a deny rule matches the client, the connection is dropped. Otherwise, xinetd starts an instance of the requested service and passes control of the connection to that service.
Important
Care should be taken when using TCP Wrappers access controls in conjunction with xinetd access controls. Misconfiguration can cause undesirable effects.
--- NEW FILE sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html ---
2.5.4.3.3.??Binding and Redirection Options
The service configuration files for xinetd support binding the service to an IP address and redirecting incoming requests for that service to another IP address, hostname, or port.
Binding is controlled with the bind option in the service-specific configuration files and links the service to one IP address on the system. When this is configured, the bind option only allows requests to the correct IP address to access the service. You can use this method to bind different services to different network interfaces based on requirements.
This is particularly useful for systems with multiple network adapters or with multiple IP addresses. On such a system, insecure services (for example, Telnet), can be configured to listen only on the interface connected to a private network and not to the interface connected to the Internet.
The redirect option accepts an IP address or hostname followed by a port number. It configures the service to redirect any requests for this service to the specified host and port number. This feature can be used to point to another port number on the same system, redirect the request to a different IP address on the same machine, shift the request to a totally different system and port number, or any combination of these options. A user connecting to a certain service on a system may therefore be rerouted to another system without disruption.
The xinetd daemon is able to accomplish this redirection by spawning a process that stays alive for the duration of the connection between the requesting client machine and the host actually providing the service, transferring data between the two systems.
The advantages of the bind and redirect options are most clearly evident when they are used together. By binding a service to a particular IP address on a system and then redirecting requests for this service to a second machine that only the first machine can see, an internal system can be used to provide services for a totally different network. Alternatively, these options can be used to limit the exposure of a particular service on a multi-homed machine to a known IP address, as well as redirect any requests for that service to another machine especially configured for that purpose.
For example, consider a system that is used as a firewall with this setting for its Telnet service:
service telnet
{
socket_type = stream
wait = no
server = /usr/kerberos/sbin/telnetd
log_on_success += DURATION USERID
log_on_failure += USERID
bind = 123.123.123.123
redirect = 10.0.1.13 23
}
The bind and redirect options in this file ensure that the Telnet service on the machine is bound to the external IP address (123.123.123.123), the one facing the Internet. In addition, any requests for Telnet service sent to 123.123.123.123 are redirected via a second network adapter to an internal IP address (10.0.1.13) that only the firewall and internal systems can access. The firewall then sends the communication between the two systems, and the connecting system thinks it is connected to 123.123.123.123 when it is actually connected to a different machine.
This feature is particularly useful for users with broadband connections and only one fixed IP address. When using Network Address Translation (NAT), the systems behind the gateway machine, which are using internal-only IP addresses, are not available from outside the gateway system. However, when certain services controlled by xinetd are configured with the bind and redirect options, the gateway machine can act as a proxy between outside systems and a particular internal machine configured to provide the service. In addition, the various xinetd access control and logging options are also available for additional protection.
The xinetd daemon can add a basic level of protection from Denial of Service (DoS) attacks. The following is a list of directives which can aid in limiting the effectiveness of such attacks:
per_source ??? Defines the maximum number of instances for a service per source IP address. It accepts only integers as an argument and can be used in both xinetd.conf and in the service-specific configuration files in the xinetd.d/ directory.
cps ??? Defines the maximum number of connections per second. This directive takes two integer arguments separated by white space. The first argument is the maximum number of connections allowed to the service per second. The second argument is the number of seconds that xinetd must wait before re-enabling the service. It accepts only integers as arguments and can be used in either the xinetd.conf file or the service-specific configuration files in the xinetd.d/ directory.
max_load ??? Defines the CPU usage or load average threshold for a service. It accepts a floating point number argument.
The load average is a rough measure of how many processes are active at a given time. See the uptime, who, and procinfo commands for more information about load average.
There are more resource management options available for xinetd. Refer to the xinetd.conf man page for more information.
Bad practices when configuring the following aspects of a network can increase the risk of attack.
1.3.2.1.??Insecure Architectures
A misconfigured network is a primary entry point for unauthorized users. Leaving a trust-based, open local network vulnerable to the highly-insecure Internet is much like leaving a door ajar in a crime-ridden neighborhood ??? nothing may happen for an arbitrary amount of time, but eventually someone exploits the opportunity.
1.3.2.1.1.??Broadcast Networks
System administrators often fail to realize the importance of networking hardware in their security schemes. Simple hardware such as hubs and routers rely on the broadcast or non-switched principle; that is, whenever a node transmits data across the network to a recipient node, the hub or router sends a broadcast of the data packets until the recipient node receives and processes the data. This method is the most vulnerable to address resolution protocol (arp) or media access control (MAC) address spoofing by both outside intruders and unauthorized users on local hosts.
1.3.2.1.2.??Centralized Servers
Another potential networking pitfall is the use of centralized computing. A common cost-cutting measure for many businesses is to consolidate all services to a single powerful machine. This can be convenient as it is easier to manage and costs considerably less than multiple-server configurations. However, a centralized server introduces a single point of failure on the network. If the central server is compromised, it may render the network completely useless or worse, prone to data manipulation or theft. In these situations, a central server becomes an open door which allows access to the entire network.
Server security is as important as network security because servers often hold a great deal of an organization's vital information. If a server is compromised, all of its contents may become available for the cracker to steal or manipulate at will. The following sections detail some of the main issues.
1.3.3.1.??Unused Services and Open Ports
A full installation of Fedora contains 1000+ application and library packages. However, most server administrators do not opt to install every single package in the distribution, preferring instead to install a base installation of packages, including several server applications.
A common occurrence among system administrators is to install the operating system without paying attention to what programs are actually being installed. This can be problematic because unneeded services may be installed, configured with the default settings, and possibly turned on. This can cause unwanted services, such as Telnet, DHCP, or DNS, to run on a server or workstation without the administrator realizing it, which in turn can cause unwanted traffic to the server, or even, a potential pathway into the system for crackers. Refer To Section??2.2, ???Server Security??? for information on closing ports and disabling unused services.
--- NEW FILE sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html ---
1.3.4.??Threats to Workstation and Home PC Security
1.3.4.??Threats to Workstation and Home PC Security
Workstations and home PCs may not be as prone to attack as networks or servers, but since they often contain sensitive data, such as credit card information, they are targeted by system crackers. Workstations can also be co-opted without the user's knowledge and used by attackers as "slave" machines in coordinated attacks. For these reasons, knowing the vulnerabilities of a workstation can save users the headache of reinstalling the operating system, or worse, recovering from data theft.
1.3.4.1.??Bad Passwords
Bad passwords are one of the easiest ways for an attacker to gain access to a system. For more on how to avoid common pitfalls when creating a password, refer to Section??2.1.3, ???Password Security???.
To plan and implement a good security strategy, first be aware of some of the issues which determined, motivated attackers exploit to compromise systems. But before detailing these issues, the terminology used when identifying an attacker must be defined.
1.3.1.??A Quick History of Hackers
The modern meaning of the term hacker has origins dating back to the 1960s and the Massachusetts Institute of Technology (MIT) Tech Model Railroad Club, which designed train sets of large scale and intricate detail. Hacker was a name used for club members who discovered a clever trick or workaround for a problem.
The term hacker has since come to describe everything from computer buffs to gifted programmers. A common trait among most hackers is a willingness to explore in detail how computer systems and networks function with little or no outside motivation. Open source software developers often consider themselves and their colleagues to be hackers, and use the word as a term of respect.
Typically, hackers follow a form of the hacker ethic which dictates that the quest for information and expertise is essential, and that sharing this knowledge is the hackers duty to the community. During this quest for knowledge, some hackers enjoy the academic challenges of circumventing security controls on computer systems. For this reason, the press often uses the term hacker to describe those who illicitly access systems and networks with unscrupulous, malicious, or criminal intent. The more accurate term for this type of computer hacker is cracker ??? a term created by hackers in the mid-1980s to differentiate the two communities.
1.3.1.1.??Shades of Gray
Within the community of individuals who find and exploit vulnerabilities in systems and networks are several distinct groups. These groups are often described by the shade of hat that they "wear" when performing their security investigations and this shade is indicative of their intent.
The white hat hacker is one who tests networks and systems to examine their performance and determine how vulnerable they are to intrusion. Usually, white hat hackers crack their own systems or the systems of a client who has specifically employed them for the purposes of security auditing. Academic researchers and professional security consultants are two examples of white hat hackers.
A black hat hacker is synonymous with a cracker. In general, crackers are less focused on programming and the academic side of breaking into systems. They often rely on available cracking programs and exploit well known vulnerabilities in systems to uncover sensitive information for personal gain or to inflict damage on the target system or network.
The gray hat hacker, on the other hand, has the skills and intent of a white hat hacker in most situations but uses his knowledge for less than noble purposes on occasion. A gray hat hacker can be thought of as a white hat hacker who wears a black hat at times to accomplish his own agenda.
Gray hat hackers typically subscribe to another form of the hacker ethic, which says it is acceptable to break into systems as long as the hacker does not commit theft or breach confidentiality. Some would argue, however, that the act of breaking into a system is in itself unethical.
Regardless of the intent of the intruder, it is important to know the weaknesses a cracker may likely attempt to exploit. The remainder of the chapter focuses on these issues.
The firewall rules are only active if the iptables service is running. To manually start the service, use the following command:
[root at myServer ~] # service iptables restart
To ensure that iptables starts when the system is booted, use the following command:
[root at myServer ~] # chkconfig --level 345 iptables on
The ipchains service is not included in Fedora. However, if ipchains is installed (for example, an upgrade was performed and the system had ipchains previously installed), the ipchains and iptables services should not be activated simultaneously. To make sure the ipchains service is disabled and configured not to start at boot time, use the following two commands:
[root at myServer ~] # service ipchains stop
[root at myServer ~] # chkconfig --level 345 ipchains off
--- NEW FILE sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html ---
2.8.2.2.??Enabling and Disabling the Firewall
Select one of the following options for the firewall:
Disabled ??? Disabling the firewall provides complete access to your system and does no security checking. This should only be selected if you are running on a trusted network (not the Internet) or need to configure a custom firewall using the iptables command line tool.
Warning
Firewall configurations and any customized firewall rules are stored in the /etc/sysconfig/iptables file. If you choose Disabled and click OK, these configurations and firewall rules will be lost.
Enabled ??? This option configures the system to reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
If you are connecting your system to the Internet, but do not plan to run a server, this is the safest choice.
The Security Level Configuration Tool includes an Other ports section for specifying custom IP ports as being trusted by iptables. For example, to allow IRC and Internet printing protocol (IPP) to pass through the firewall, add the following to the Other ports section:
Click OK to save the changes and enable or disable the firewall. If Enable firewall was selected, the options selected are translated to iptables commands and written to the /etc/sysconfig/iptables file. The iptables service is also started so that the firewall is activated immediately after saving the selected options. If Disable firewall was selected, the /etc/sysconfig/iptables file is removed and the iptables service is stopped immediately.
The selected options are also written to the /etc/sysconfig/system-config-securitylevel file so that the settings can be restored the next time the application is started. Do not edit this file by hand.
Enabling options in the Trusted services list allows the specified service to pass through the firewall.
WWW (HTTP)
The HTTP protocol is used by Apache (and by other Web servers) to serve web pages. If you plan on making your Web server publicly available, select this check box. This option is not required for viewing pages locally or for developing web pages. This service requires that the httpd package be installed.
Enabling WWW (HTTP) will not open a port for HTTPS, the SSL version of HTTP. If this service is required, select the Secure WWW (HTTPS) check box.
FTP
The FTP protocol is used to transfer files between machines on a network. If you plan on making your FTP server publicly available, select this check box. This service requires that the vsftpd package be installed.
SSH
Secure Shell (SSH) is a suite of tools for logging into and executing commands on a remote machine. To allow remote access to the machine via ssh, select this check box. This service requires that the openssh-server package be installed.
Telnet
Telnet is a protocol for logging into remote machines. Telnet communications are unencrypted and provide no security from network snooping. Allowing incoming Telnet access is not recommended. To allow remote access to the machine via telnet, select this check box. This service requires that the telnet-server package be installed.
Mail (SMTP)
SMTP is a protocol that allows remote hosts to connect directly to your machine to deliver mail. You do not need to enable this service if you collect your mail from your ISP's server using POP3 or IMAP, or if you use a tool such as fetchmail. To allow delivery of mail to your machine, select this check box. Note that an improperly configured SMTP server can allow remote machines to use your server to send spam.
NFS4
The Network File System (NFS) is a file sharing protocol commonly used on *NIX systems. Version 4 of this protocol is more secure than its predecessors. If you want to share files or directories on your system with other network users, select this check box.
Samba
Samba is an implementation of Microsoft's proprietary SMB networking protocol. If you need to share files, directories, or locally-connected printers with Microsoft Windows machines, select this check box.
Command options instruct iptables to perform a specific action. Only one command option is allowed per iptables command. With the exception of the help command, all commands are written in upper-case characters.
The iptables commands are as follows:
-A ??? Appends the rule to the end of the specified chain. Unlike the -I option described below, it does not take an integer argument. It always appends the rule to the end of the specified chain.
-C ??? Checks a particular rule before adding it to the user-specified chain. This command can help you construct complex iptables rules by prompting you for additional parameters and options.
-D <integer> | <rule> ??? Deletes a rule in a particular chain by number (such as 5 for the fifth rule in a chain), or by rule specification. The rule specification must exactly match an existing rule.
-E ??? Renames a user-defined chain. A user-defined chain is any chain other than the default, pre-existing chains. (Refer to the -N option, below, for information on creating user-defined chains.) This is a cosmetic change and does not affect the structure of the table.
Note
If you attempt to rename one of the default chains, the system reports a Match not found error. You cannot rename the default chains.
-F ??? Flushes the selected chain, which effectively deletes every rule in the chain. If no chain is specified, this command flushes every rule from every chain.
-h ??? Provides a list of command structures, as well as a quick summary of command parameters and options.
-I [<integer>] ??? Inserts the rule in the specified chain at a point specified by a user-defined integer argument. If no argument is specified, the rule is inserted at the top of the chain.
Caution
As noted above, the order of rules in a chain determines which rules apply to which packets. This is important to remember when adding rules using either the -A or -I option.
This is especially important when adding rules using the -I with an integer argument. If you specify an existing number when adding a rule to a chain, iptables adds the new rule before (or above) the existing rule.
-L ??? Lists all of the rules in the chain specified after the command. To list all rules in all chains in the default filter table, do not specify a chain or table. Otherwise, the following syntax should be used to list the rules in a specific chain in a particular table:
iptables -L <chain-name> -t <table-name>
Additional options for the -L command option, which provide rule numbers and allow more verbose rule descriptions, are described in Section??2.9.3.6, ???Listing Options???.
-N ??? Creates a new chain with a user-specified name. The chain name must be unique, otherwise an error message is displayed.
-P ??? Sets the default policy for the specified chain, so that when packets traverse an entire chain without matching a rule, they are sent to the specified target, such as ACCEPT or DROP.
-R ??? Replaces a rule in the specified chain. The rule's number must be specified after the chain's name. The first rule in a chain corresponds to rule number one.
-X ??? Deletes a user-specified chain. You cannot delete a built-in chain.
-Z ??? Sets the byte and packet counters in all chains for a table to zero.
Different network protocols provide specialized matching options which can be configured to match a particular packet using that protocol. However, the protocol must first be specified in the iptables command. For example, -p <protocol-name> enables options for the specified protocol. Note that you can also use the protocol ID, instead of the protocol name. Refer to the following examples, each of which have the same effect:
iptables -A INPUT -p icmp --icmp-type any -j ACCEPT iptables -A INPUT -p 5813 --icmp-type any -j ACCEPT
Service definitions are provided in the /etc/services file. For readability, it is recommended that you use the service names rather than the port numbers.
Important
Secure the /etc/services file to prevent unauthorized editing. If this file is editable, crackers can use it to enable ports on your machine you have otherwise closed. To secure this file, type the following commands as root:
[root at myServer ~]# chown root.root /etc/services [root at myServer ~]# chmod 0644 /etc/services [root at myServer ~]# chattr +i /etc/services
This prevents the file from being renamed, deleted or having links made to it.
2.9.3.4.1.??TCP Protocol
These match options are available for the TCP protocol (-p tcp):
--dport ??? Sets the destination port for the packet.
To configure this option, use a network service name (such as www or smtp); a port number; or a range of port numbers.
To specify a range of port numbers, separate the two numbers with a colon (:). For example: -p tcp --dport 3000:3200. The largest acceptable valid range is 0:65535.
Use an exclamation point character (!) after the --dport option to match all packets that do not use that network service or port.
To browse the names and aliases of network services and the port numbers they use, view the /etc/services file.
The --destination-port match option is synonymous with --dport.
--sport ??? Sets the source port of the packet using the same options as --dport. The --source-port match option is synonymous with --sport.
--syn ??? Applies to all TCP packets designed to initiate communication, commonly called SYN packets. Any packets that carry a data payload are not touched.
Use an exclamation point character (!) after the --syn option to match all non-SYN packets.
--tcp-flags <tested flag list> <set flag list> ??? Allows TCP packets that have specific bits (flags) set, to match a rule.
The --tcp-flags match option accepts two parameters. The first parameter is the mask; a comma-separated list of flags to be examined in the packet. The second parameter is a comma-separated list of flags that must be set for the rule to match.
The possible flags are:
ACK
FIN
PSH
RST
SYN
URG
ALL
NONE
For example, an iptables rule that contains the following specification only matches TCP packets that have the SYN flag set and the ACK and FIN flags not set:
--tcp-flags ACK,FIN,SYN SYN
Use the exclamation point character (!) after the --tcp-flags to reverse the effect of the match option.
--tcp-option ??? Attempts to match with TCP-specific options that can be set within a particular packet. This match option can also be reversed with the exclamation point character (!).
Certain iptables commands, including those used to add, append, delete, insert, or replace rules within a particular chain, require various parameters to construct a packet filtering rule.
-c ??? Resets the counters for a particular rule. This parameter accepts the PKTS and BYTES options to specify which counter to reset.
-d ??? Sets the destination hostname, IP address, or network of a packet that matches the rule. When matching a network, the following IP address/netmask formats are supported:
N.N.N.N/M.M.M.M ??? Where N.N.N.N is the IP address range and M.M.M.M is the netmask.
N.N.N.N/M ??? Where N.N.N.N is the IP address range and M is the bitmask.
-f ??? Applies this rule only to fragmented packets.
You can use the exclamation point character (!) option after this parameter to specify that only unfragmented packets are matched.
Note
Distinguishing between fragmented and unfragmented packets is desirable, despite fragmented packets being a standard part of the IP protocol.
Originally designed to allow IP packets to travel over networks with differing frame sizes, these days fragmentation is more commonly used to generate DoS attacks using mal-formed packets. It's also worth noting that IPv6 disallows fragmentation entirely.
-i ??? Sets the incoming network interface, such as eth0 or ppp0. With iptables, this optional parameter may only be used with the INPUT and FORWARD chains when used with the filter table and the PREROUTING chain with the nat and mangle tables.
This parameter also supports the following special options:
Exclamation point character (!) ??? Reverses the directive, meaning any specified interfaces are excluded from this rule.
Plus character (+) ??? A wildcard character used to match all interfaces that match the specified string. For example, the parameter -i eth+ would apply this rule to any Ethernet interfaces but exclude any other interfaces, such as ppp0.
If the -i parameter is used but no interface is specified, then every interface is affected by the rule.
-j ??? Jumps to the specified target when a packet matches a particular rule.
The standard targets are ACCEPT, DROP, QUEUE, and RETURN.
Extended options are also available through modules loaded by default with the Fedora iptables RPM package. Valid targets in these modules include LOG, MARK, and REJECT, among others. Refer to the iptables man page for more information about these and other targets.
This option can also be used to direct a packet matching a particular rule to a user-defined chain outside of the current chain so that other rules can be applied to the packet.
If no target is specified, the packet moves past the rule with no action taken. The counter for this rule, however, increases by one.
-o ??? Sets the outgoing network interface for a rule. This option is only valid for the OUTPUT and FORWARD chains in the filter table, and the POSTROUTING chain in the nat and mangle tables. This parameter accepts the same options as the incoming network interface parameter (-i).
-p <protocol> ??? Sets the IP protocol affected by the rule. This can be either icmp, tcp, udp, or all, or it can be a numeric value, representing one of these or a different protocol. You can also use any protocols listed in the /etc/protocols file.
The "all" protocol means the rule applies to every supported protocol. If no protocol is listed with this rule, it defaults to "all".
-s ??? Sets the source for a particular packet using the same syntax as the destination (-d) parameter.
The default list command, iptables -L [<chain-name>], provides a very basic overview of the default filter table's current chains. Additional options provide more information:
-v ??? Displays verbose output, such as the number of packets and bytes each chain has processed, the number of packets and bytes each rule has matched, and which interfaces apply to a particular rule.
-x ??? Expands numbers into their exact values. On a busy system, the number of packets and bytes processed by a particular chain or rule may be abbreviated to Kilobytes, Megabytes (Megabytes) or Gigabytes. This option forces the full number to be displayed.
-n ??? Displays IP addresses and port numbers in numeric format, rather than the default hostname and network service format.
--line-numbers ??? Lists rules in each chain next to their numeric order in the chain. This option is useful when attempting to delete the specific rule in a chain or to locate where to insert a rule within a chain.
-t <table-name> ??? Specifies a table name. If omitted, defaults to the filter table.
The following examples illustrate the use of several of these options. Note the difference in the byte display by including the -x option.
When a packet has matched a particular rule, the rule can direct the packet to a number of different targets which determine the appropriate action. Each chain has a default target, which is used if none of the rules on that chain match a packet or if none of the rules which match the packet specify a target.
The following are the standard targets:
<user-defined-chain> ??? A user-defined chain within the table. User-defined chain names must be unique. This target passes the packet to the specified chain.
ACCEPT ??? Allows the packet through to its destination or to another chain.
DROP ??? Drops the packet without responding to the requester. The system that sent the packet is not notified of the failure.
QUEUE ??? The packet is queued for handling by a user-space application.
RETURN ??? Stops checking the packet against rules in the current chain. If the packet with a RETURN target matches a rule in a chain called from another chain, the packet is returned to the first chain to resume rule checking where it left off. If the RETURN rule is used on a built-in chain and the packet cannot move up to its previous chain, the default target for the current chain is used.
In addition, extensions are available which allow other targets to be specified. These extensions are called target modules or match option modules and most only apply to specific tables and situations. Refer to Section??2.9.3.4.4, ???Additional Match Option Modules??? for more information about match option modules.
Many extended target modules exist, most of which only apply to specific tables or situations. Some of the most popular target modules included by default in Fedora are:
LOG ??? Logs all packets that match this rule. Because the packets are logged by the kernel, the /etc/syslog.conf file determines where these log entries are written. By default, they are placed in the /var/log/messages file.
Additional options can be used after the LOG target to specify the way in which logging occurs:
--log-level ??? Sets the priority level of a logging event. Refer to the syslog.conf man page for a list of priority levels.
--log-ip-options ??? Logs any options set in the header of an IP packet.
--log-prefix ??? Places a string of up to 29 characters before the log line when it is written. This is useful for writing syslog filters for use in conjunction with packet logging.
Note
Due to an issue with this option, you should add a trailing space to the log-prefix value.
--log-tcp-options ??? Logs any options set in the header of a TCP packet.
--log-tcp-sequence ??? Writes the TCP sequence number for the packet in the log.
REJECT ??? Sends an error packet back to the remote system and drops the packet.
The REJECT target accepts --reject-with <type> (where <type> is the rejection type) allowing more detailed information to be returned with the error packet. The message port-unreachable is the default error type given if no other option is used. Refer to the iptables man page for a full list of <type> options.
Other target extensions, including several that are useful for IP masquerading using the nat table, or with packet alteration using the mangle table, can be found in the iptables man page.
Table??1.1, ???Common Exploits??? details some of the most common exploits and entry points used by intruders to access organizational network resources. Key to these common exploits are the explanations of how they are performed and how administrators can properly safeguard their network against such attacks.
Exploit
Description
Notes
Null or Default Passwords
Leaving administrative passwords blank or using a default password set by the product vendor. This is most common in hardware such as routers and firewalls, though some services that run on Linux can contain default administrator passwords (though Fedora 5 does not ship with them).
Commonly associated with networking hardware such as routers, firewalls, VPNs, and network attached storage (NAS) appliances.
Common in many legacy operating systems, especially OSes that bundle services (such as UNIX and Windows.)
Administrators sometimes create privileged user accounts in a rush and leave the password null, a perfect entry point for malicious users who discover the account.
Default Shared Keys
Secure services sometimes package default security keys for development or evaluation testing purposes. If these keys are left unchanged and are placed in a production environment on the Internet, all users with the same default keys have access to that shared-key resource, and any sensitive information that it contains.
Most common in wireless access points and preconfigured secure server appliances.
IP Spoofing
A remote machine acts as a node on your local network, finds vulnerabilities with your servers, and installs a backdoor program or trojan horse to gain control over your network resources.
Spoofing is quite difficult as it involves the attacker predicting TCP/IP SYN-ACK numbers to coordinate a connection to target systems, but several tools are available to assist crackers in performing such a vulnerability.
Depends on target system running services (such as rsh, telnet, FTP and others) that use source-based authentication techniques, which are not recommended when compared to PKI or other forms of encrypted authentication used in ssh or SSL/TLS.
Eavesdropping
Collecting data that passes between two active nodes on a network by eavesdropping on the connection between the two nodes.
This type of attack works mostly with plain text transmission protocols such as Telnet, FTP, and HTTP transfers.
Remote attacker must have access to a compromised system on a LAN in order to perform such an attack; usually the cracker has used an active attack (such as IP spoofing or man-in-the-middle) to compromise a system on the LAN.
Preventative measures include services with cryptographic key exchange, one-time passwords, or encrypted authentication to prevent password snooping; strong encryption during transmission is also advised.
Service Vulnerabilities
An attacker finds a flaw or loophole in a service run over the Internet; through this vulnerability, the attacker compromises the entire system and any data that it may hold, and could possibly compromise other systems on the network.
HTTP-based services such as CGI are vulnerable to remote command execution and even interactive shell access. Even if the HTTP service runs as a non-privileged user such as "nobody", information such as configuration files and network maps can be read, or the attacker can start a denial of service attack which drains system resources or renders it unavailable to other users.
Services sometimes can have vulnerabilities that go unnoticed during development and testing; these vulnerabilities (such as buffer overflows, where attackers crash a service using arbitary values that fill the memory buffer of an application, giving the attacker an interactive command prompt from which they may execute arbitrary commands) can give complete administrative control to an attacker.
Administrators should make sure that services do not run as the root user,
and should stay vigilant of patches and errata updates for applications from vendors or security organizations such as CERT and CVE.
Application Vulnerabilities
Attackers find faults in desktop and workstation applications (such as e-mail clients) and execute arbitrary code, implant trojan horses for future compromise, or crash systems. Further exploitation can occur if the compromised workstation has administrative privileges on the rest of the network.
Workstations and desktops are more prone to exploitation as workers do not have the expertise or experience to prevent or detect a compromise; it is imperative to inform individuals of the risks they are taking when they install unauthorized software or open unsolicited email attachments.
Safeguards can be implemented such that email client software does not automatically open or execute attachments. Additionally, the automatic update of workstation software via Red Hat Network or other system management services can alleviate the burdens of multi-seat security deployments.
Denial of Service (DoS) Attacks
Attacker or group of attackers coordinate against an organization's network or server resources by sending unauthorized packets to the target host (either server, router, or workstation). This forces the resource to become unavailable to legitimate users.
The most reported DoS case in the US occurred in 2000. Several highly-trafficked commercial and government sites were rendered unavailable by a coordinated ping flood attack using several compromised systems with high bandwidth connections acting as zombies, or redirected broadcast nodes.
Source packets are usually forged (as well as rebroadcasted), making investigation as to the true source of the attack difficult.
Advances in ingress filtering (IETF rfc2267) using iptables and Network IDSes such as snort assist administrators in tracking down and preventing distributed DoS attacks.
7-Zip is not shipped by default with Microsoft Windows or Mac OS X. If you need to use your 7-Zip files on those platforms you will need to install the appropriate version of 7-Zip on those computers. See the 7-Zip download page.
GNOME's File Roller application will recognize your .7z files and attempt to open them, but it will fail with the error "''An error occurred while loading the archive.''" when it attempts to do so. This is because File Roller does not currently support the extraction of encrypted 7-Zip files. A bug report ([http://bugzilla.gnome.org/show_bug.cgi?id=490732 Gnome Bug 490732]) has been submitted.
By following these instructions you are going to compress and encrypt your "Documents" directory. Your original "Documents" directory will remain unaltered. This technique can be applied to any directory or file you have access to on the filesystem.
Open a Terminal:Click ''Applications'' -> ''System Tools'' -> ''Terminal''
Compress and Encrypt: (enter a password when prompted) 7za a -mhe=on -ms=on -p Documents.7z Documents/
The "Documents" directory is now compressed and encrypted. The following instructions will move the encrypted archive somewhere new and then extract it.
Create a new directory: mkdir newplace
Move the encrypted file: mv Documents.7z newplace
Go to the new directory: cd newplace
Extract the file: (enter the password when prompted) 7za x Documents.7z
The archive is now extracted into the new location. The following instructions will clean up all the prior steps and restore your computer to its previous state.
Go up a directory: cd ..
Delete the test archive and test extraction: rm -r newplace
7-Zip is a cross-platform, next generation, file compression tool that can also use strong encryption (AES-256) to protect the contents of the archive. This is extremely useful when you need to move data between multiple computers that use varying operating systems (i.e. Linux at home, Windows at work) and you want a portable encryption solution.
3.8.1.??7-Zip Installation in Fedora
7-Zip is not a base package in Fedora, but it is available in the software repository. Once installed, the package will update alongside the rest of the software on the computer with no special attention necessary.
Full disk or partition encryption is one of the best ways of protecting your data. Not only is each file protected but also the temporary storage that may contain parts of these files is also protected. Full disk encryption will protect all of your files so you don't have to worry about selecting what you want to protect and possibly missing a file.
Fedora 9 natively supports LUKS Encryption. LUKS will bulk encrypt your hard drive partitions so that while your computer is off your data is protected. This will also protect your computer from attackers attempting to use single-user-mode to login to your computer or otherwise gain access. LUKS can be manually setup on Fedora 8.
Full disk encryption solutions like LUKS only protect the data when your computer is off. Once the computer is on and LUKS has decrypted the disk, the files on that disk are available to anyone who would normally have access to them. To protect your files when the computer is on, use full disk encryption in combination with another solution such as file based encryption. Also remember to lock your computer whenever you are away from it. A passphrase protected screen saver set to activate after a few minutes of inactivity is a good way to keep intruders out.
Depending upon your target and resources, there are many tools available. There are tools for wireless networks, Novell networks, Windows systems, Linux systems, and more. Another essential part of performing assessments may include reviewing physical security, personnel screening, or voice/PBX network assessment. New concepts, such as war walking scanning the perimeter of your enterprise's physical structures for wireless network vulnerabilities are some emerging concepts that you can investigate and, if needed, incorporate into your assessments. Imagination and exposure are the only limits of planning and conducting vulnerability assessments.
Nessus is a full-service security scanner. The plug-in architecture of Nessus allows users to customize it for their systems and networks. As with any scanner, Nessus is only as good as the signature database it relies upon. Fortunately, Nessus is frequently updated and features full reporting, host scanning, and real-time vulnerability searches. Remember that there could be false positives and false negatives, even in a tool as powerful and as frequently updated as Nessus.
Note
Nessus is not included with Fedora and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application.
For more information about Nessus, refer to the official website at the following URL:
Nikto is an excellent common gateway interface (CGI) script scanner. Nikto not only checks for CGI vulnerabilities but does so in an evasive manner, so as to elude intrusion detection systems. It comes with thorough documentation which should be carefully reviewed prior to running the program. If you have Web servers serving up CGI scripts, Nikto can be an excellent resource for checking the security of these servers.
Note
Nikto is not included with Fedora and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application.
More information about Nikto can be found at the following URL:
VLAD is a vulnerabilities scanner developed by the RAZOR team at Bindview, Inc., which checks for the SANS Top Ten list of common security issues (SNMP issues, file sharing issues, etc.). While not as full-featured as Nessus, VLAD is worth investigating.
Note
VLAD is not included with Fedora and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application.
More information about VLAD can be found on the RAZOR team website at the following URL:
You can create iptables rules to route traffic to certain machines, such as a dedicated HTTP or FTP server, in a demilitarized zone (DMZ). A DMZ is a special local subnetwork dedicated to providing services on a public carrier, such as the Internet.
For example, to set a rule for routing incoming HTTP requests to a dedicated HTTP server at 10.0.4.2 (outside of the 192.168.1.0/24 range of the LAN), NAT uses the PREROUTING table to forward the packets to the appropriate destination:
With this command, all HTTP connections to port 80 from outside of the LAN are routed to the HTTP server on a network separate from the rest of the internal network. This form of network segmentation can prove safer than allowing HTTP connections to a machine on the network.
If the HTTP server is configured to accept secure connections, then port 443 must be forwarded as well.
If you have a server on your internal network that you want make available externally, you can use the -j DNAT target of the PREROUTING chain in NAT to specify a destination IP address and port where incoming packets requesting a connection to your internal service can be forwarded.
For example, if you want to forward incoming HTTP requests to your dedicated Apache HTTP Server at 172.31.0.23, use the following command:
This rule specifies that the nat table use the built-in PREROUTING chain to forward incoming HTTP requests exclusively to the listed destination IP address of 172.31.0.23.
Note
If you have a default policy of DROP in your FORWARD chain, you must append a rule to forward all incoming HTTP requests so that destination NAT routing is possible. To do this, use the following command:
[root at myServer ~ ] # iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT
This rule forwards all incoming HTTP requests from the firewall to the intended destination; the Apache HTTP Server behind the firewall.
There are several aspects to firewalls and the Linux Netfilter subsystem that could not be covered in this chapter. For more information, refer to the following resources.
2.8.9.1.??Installed Firewall Documentation
Refer to Section??2.9, ???IPTables??? for more detailed information on the iptables command, including definitions for many command options.
The iptables man page contains a brief summary of the various options.
Just as a firewall in a building attempts to prevent a fire from spreading, a computer firewall attempts to prevent malicious software from spreading to your computer. It also helps to prevent unauthorized users from accessing your computer.
In a default Fedora installation, a firewall exists between your computer or network and any untrusted networks, for example the Internet. It determines which services on your computer remote users can access. A properly configured firewall can greatly increase the security of your system. It is recommended that you configure a firewall for any Fedora system with an Internet connection.
2.8.2.1.??Security Level Configuration Tool
During the Firewall Configuration screen of the Fedora installation, you were given the option to enable a basic firewall as well as to allow specific devices, incoming services, and ports.
After installation, you can change this preference by using the Security Level Configuration Tool.
To start this application, use the following command:
[root at myServer ~] # system-config-securitylevel
Security Level Configuration
Figure??2.15.??Security Level Configuration Tool
Note
The Security Level Configuration Tool only configures a basic firewall. If the system needs more complex rules, refer to Section??2.9, ???IPTables??? for details on configuring specific iptables rules.
Preventing remote attackers from accessing a LAN is one of the most important aspects of network security. The integrity of a LAN should be protected from malicious remote users through the use of stringent firewall rules.
However, with a default policy set to block all incoming, outgoing, and forwarded packets, it is impossible for the firewall/gateway and internal LAN users to communicate with each other or with external resources.
To allow users to perform network-related functions and to use networking applications, administrators must open certain ports for communication.
For example, to allow access to port 80 on the firewall, append the following rule:
[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
This allows users to browse websites that communicate using the standard port 80. To allow access to secure websites (for example, https://www.example.com/), you also need to provide access to port 443, as follows:
[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
Important
When creating an iptables ruleset, order is important.
If a rule specifies that any packets from the 192.168.100.0/24 subnet be dropped, and this is followed by a rule that allows packets from 192.168.100.13 (which is within the dropped subnet), then the second rule is ignored.
The rule to allow packets from 192.168.100.13 must precede the rule that drops the remainder of the subnet.
To insert a rule in a specific location in an existing chain, use the -I option. For example:
[root at myServer ~ ] # iptables -I INPUT 1 -i lo -p all -j ACCEPT
This rule is inserted as the first rule in the INPUT chain to allow local loopback device traffic.
There may be times when you require remote access to the LAN. Secure services, for example SSH, can be used for encrypted remote connection to LAN services.
Administrators with PPP-based resources (such as modem banks or bulk ISP accounts), dial-up access can be used to securely circumvent firewall barriers. Because they are direct connections, modem connections are typically behind a firewall/gateway.
For remote users with broadband connections, however, special cases can be made. You can configure iptables to accept connections from remote SSH clients. For example, the following rules allow remote SSH access:
[root at myServer ~ ] # iptables -A INPUT -p tcp --dport 22 -j ACCEPT
[root at myServer ~ ] # iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
These rules allow incoming and outbound access for an individual system, such as a single PC directly connected to the Internet or a firewall/gateway. However, they do not allow nodes behind the firewall/gateway to access these services. To allow LAN access to these services, you can use Network Address Translation (NAT) with iptables filtering rules.
Most ISPs provide only a limited number of publicly routable IP addresses to the organizations they serve.
Administrators must, therefore, find alternative ways to share access to Internet services without giving public IP addresses to every node on the LAN. Using private IP addresses is the most common way of allowing all nodes on a LAN to properly access internal and external network services.
Edge routers (such as firewalls) can receive incoming transmissions from the Internet and route the packets to the intended LAN node. At the same time, firewalls/gateways can also route outgoing requests from a LAN node to the remote Internet service.
This forwarding of network traffic can become dangerous at times, especially with the availability of modern cracking tools that can spoof internal IP addresses and make the remote attacker's machine act as a node on your LAN.
To prevent this, iptables provides routing and forwarding policies that can be implemented to prevent abnormal usage of network resources.
The FORWARD chain allows an administrator to control where packets can be routed within a LAN. For example, to allow forwarding for the entire LAN (assuming the firewall/gateway is assigned an internal IP address on eth1), use the following rules:
[root at myServer ~ ] # iptables -A FORWARD -i eth1 -j ACCEPT
[root at myServer ~ ] # iptables -A FORWARD -o eth1 -j ACCEPT
This rule gives systems behind the firewall/gateway access to the internal network. The gateway routes packets from one LAN node to its intended destination node, passing all packets through its eth1 device.
Note
By default, the IPv4 policy in Fedora kernels disables support for IP forwarding. This prevents machines that run Fedora from functioning as dedicated edge routers. To enable IP forwarding, use the following command:
[root at myServer ~ ] # sysctl -w net.ipv4.ip_forward=1
This configuration change is only valid for the current session; it does not persist beyond a reboot or network service restart. To permanently set IP forwarding, edit the /etc/sysctl.conf file as follows:
Locate the following line:
net.ipv4.ip_forward = 0
Edit it to read as follows:
net.ipv4.ip_forward = 1
Use the following command to enable the change to the sysctl.conf file:
[root at myServer ~ ] # sysctl -p /etc/sysctl.conf
2.8.5.1.??Postrouting and IP Masquerading
Accepting forwarded packets via the firewall's internal IP device allows LAN nodes to communicate with each other; however they still cannot communicate externally to the Internet.
To allow LAN nodes with private IP addresses to communicate with external public networks, configure the firewall for IP masquerading, which masks requests from LAN nodes with the IP address of the firewall's external device (in this case, eth0):
[root at myServer ~ ] # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
This rule uses the NAT packet matching table (-t nat) and specifies the built-in POSTROUTING chain for NAT (-A POSTROUTING) on the firewall's external networking device (-o eth0).
POSTROUTING allows packets to be altered as they are leaving the firewall's external device.
The -j MASQUERADE target is specified to mask the private IP address of a node with the external IP address of the firewall/gateway.
You can inspect and restrict connections to services based on their connection state. A module within iptables uses a method called connection tracking to store information about incoming connections. You can allow or deny access based on the following connection states:
NEW ??? A packet requesting a new connection, such as an HTTP request.
ESTABLISHED ??? A packet that is part of an existing connection.
RELATED ??? A packet that is requesting a new connection but is part of an existing connection. For example, FTP uses port 21 to establish a connection, but data is transferred on a different port (typically port 20).
INVALID ??? A packet that is not part of any connections in the connection tracking table.
You can use the stateful functionality of iptables connection tracking with any network protocol, even if the protocol itself is stateless (such as UDP). The following example shows a rule that uses connection tracking to forward only the packets that are associated with an established connection:
[root at myServer ~ ] # iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
The introduction of the next-generation Internet Protocol, called IPv6, expands beyond the 32-bit address limit of IPv4 (or IP). IPv6 supports 128-bit addresses, and carrier networks that are IPv6 aware are therefore able to address a larger number of routable addresses than IPv4.
Fedora supports IPv6 firewall rules using the Netfilter 6 subsystem and the ip6tables command. In Fedora 5, both IPv4 and IPv6 services are enabled by default.
The ip6tables command syntax is identical to iptables in every aspect except that it supports 128-bit addresses. For example, use the following command to enable SSH connections on an IPv6-aware network server:
[root at myServer ~ ] # ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
For more information about IPv6 networking, refer to the IPv6 Information Page at http://www.ipv6.org/.
2.8.6.??Malicious Software and Spoofed IP Addresses
More elaborate rules can be created that control access to specific subnets, or even specific nodes, within a LAN. You can also restrict certain dubious applications or programs such as trojans, worms, and other client/server viruses from contacting their server.
For example, some trojans scan networks for services on ports from 31337 to 31340 (called the elite ports in cracking terminology).
Since there are no legitimate services that communicate via these non-standard ports, blocking them can effectively diminish the chances that potentially infected nodes on your network independently communicate with their remote master servers.
The following rules drop all TCP traffic that attempts to use port 31337:
[root at myServer ~ ] # iptables -A OUTPUT -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
[root at myServer ~ ] # iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
You can also block outside connections that attempt to spoof private IP address ranges to infiltrate your LAN.
For example, if your LAN uses the 192.168.1.0/24 range, you can design a rule that instructs the Internet-facing network device (for example, eth0) to drop any packets to that device with an address in your LAN IP range.
Because it is recommended to reject forwarded packets as a default policy, any other spoofed IP address to the external-facing device (eth0) is rejected automatically.
[root at myServer ~ ] # iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP
Note
There is a distinction between the DROP and REJECT targets when dealing with appended rules.
The REJECT target denies access and returns a connection refused error to users who attempt to connect to the service. The DROP target, as the name implies, drops the packet without any warning.
Administrators can use their own discretion when using these targets. However, to avoid user confusion and attempts to continue connecting, the REJECT target is recommended.
The first step in using iptables is to start the iptables service. Use the following command to start the iptables service:
[root at myServer ~] # service iptables start
Note
The ip6tables service can be turned off if you intend to use the iptables service only. If you deactivate the ip6tables service, remember to deactivate the IPv6 network also. Never leave a network device active without the matching firewall.
To force iptables to start by default when the system is booted, use the following command:
[root at myServer ~] # chkconfig --level 345 iptables on
This forces iptables to start whenever the system is booted into runlevel 3, 4, or 5.
2.8.3.1.??IPTables Command Syntax
The following sample iptables command illustrates the basic command syntax:
[root at myServer ~ ] # iptables -A <chain> -j <target>
The -A option specifies that the rule be appended to <chain>. Each chain is comprised of one or more rules, and is therefore also known as a ruleset.
The three built-in chains are INPUT, OUTPUT, and FORWARD. These chains are permanent and cannot be deleted. The chain specifies the point at which a packet is manipulated.
The -j <target> option specifies the target of the rule; i.e., what to do if the packet matches the rule. Examples of built-in targets are ACCEPT, DROP, and REJECT.
Refer to the iptables man page for more information on the available chains, options, and targets.
Information security is commonly thought of as a process and not a product. However, standard security implementations usually employ some form of dedicated mechanism to control access privileges and restrict network resources to users who are authorized, identifiable, and traceable. Fedora includes several tools to assist administrators and security engineers with network-level access control issues.
Firewalls are one of the core components of a network security implementation. Several vendors market firewall solutions catering to all levels of the marketplace: from home users protecting one PC to data center solutions safeguarding vital enterprise information. Firewalls can be stand-alone hardware solutions, such as firewall appliances by Cisco, Nokia, and Sonicwall. Vendors such as Checkpoint, McAfee, and Symantec have also developed proprietary software firewall solutions for home and business markets.
Apart from the differences between hardware and software firewalls, there are also differences in the way firewalls function that separate one solution from another. Table??2.2, ???Firewall Types??? details three common types of firewalls and how they function:
Method
Description
Advantages
Disadvantages
NAT
Network Address Translation (NAT) places private IP subnetworks behind one or a small pool of public IP addresses, masquerading all requests to one source rather than several. The Linux kernel has built-in NAT functionality through the Netfilter kernel subsystem.
?? Can be configured transparently to machines on a LAN
?? Protection of many machines and services behind one or more external IP addresses simplifies administration duties
?? Restriction of user access to and from the LAN can be configured by opening and closing ports on the NAT firewall/gateway
?? Cannot prevent malicious activity once users connect to a service outside of the firewall
Packet Filter
A packet filtering firewall reads each data packet that passes through a LAN. It can read and process packets by header information and filters the packet based on sets of programmable rules implemented by the firewall administrator. The Linux kernel has built-in packet filtering functionality through the Netfilter kernel subsystem.
?? Customizable through the iptables front-end utility
?? Does not require any customization on the client side, as all network activity is filtered at the router level rather than the application level
?? Since packets are not transmitted through a proxy, network performance is faster due to direct connection from client to remote host
?? Cannot filter packets for content like proxy firewalls
?? Processes packets at the protocol layer, but cannot filter packets at an application layer
?? Complex network architectures can make establishing packet filtering rules difficult, especially if coupled with IP masquerading or local subnets and DMZ networks
Proxy
Proxy firewalls filter all requests of a certain protocol or type from LAN clients to a proxy machine, which then makes those requests to the Internet on behalf of the local client. A proxy machine acts as a buffer between malicious remote users and the internal network client machines.
?? Gives administrators control over what applications and protocols function outside of the LAN
?? Some proxy servers can cache frequently-accessed data locally rather than having to use the Internet connection to request it. This helps to reduce bandwidth consumption
?? Proxy services can be logged and monitored closely, allowing tighter control over resource utilization on the network
?? Proxies are often application-specific (HTTP, Telnet, etc.), or protocol-restricted (most proxies work with TCP-connected services only)
?? Application services cannot run behind a proxy, so your application servers must use a separate form of network security
?? Proxies can become a network bottleneck, as all requests and transmissions are passed through one source rather than directly from a client to a remote service
Table??2.2.??Firewall Types
2.8.1.??Netfilter and IPTables
The Linux kernel features a powerful networking subsystem called Netfilter. The Netfilter subsystem provides stateful or stateless packet filtering as well as NAT and IP masquerading services. Netfilter also has the ability to mangle IP header information for advanced routing and connection state management. Netfilter is controlled using the iptables tool.
2.8.1.1.??IPTables Overview
The power and flexibility of Netfilter is implemented using the iptables administration tool, a command line tool similar in syntax to its predecessor, ipchains.
A similar syntax does not mean similar implementation, however. ipchains requires intricate rule sets for: filtering source paths; filtering destination paths; and filtering both source and destination connection ports.
By contrast, iptables uses the Netfilter subsystem to enhance network connection, inspection, and processing. iptables features advanced logging, pre- and post-routing actions, network address translation, and port forwarding, all in one command line interface.
This section provides an overview of iptables. For more detailed information, refer to Section??2.9, ???IPTables???.
Most of the above tips are very basic. Depending on your knowledge of Linux and how comfortable you are with modifying your system, some changes could be made to help make your installation more secure. As mentioned above, the NSA has hardening guides and tips for securing Red Hat Enterprise Linux 5. Likewise, the Defense Information Systems Agency (DISA) has an Information Assurance Support Environment in which they publish checklists and tests for verifying the security of your system. The documents from the NSA are a good read for anyone familiar with Linux while the information from DISA is extremely specific and advanced knowledge of Unix/Linux would be a great benefit. Links to these documents are listed below. We will try to pull some of the larger items out of these documents and explain how to implement them in Fedora and why they are important. In addition to documentation, DISA has made available SRR
scripts that allow an administrator to check specific settings on a system quickly. The SRR scripts will provide an XML-formatted report listing any known vulnerable settings that you have on your system.
Refer to the following sources for additional information on packet filtering with iptables.
Section??2.8, ???Firewalls??? ??? Contains a chapter about the role of firewalls within an overall security strategy as well as strategies for constructing firewall rules.
2.9.7.1.??Installed IP Tables Documentation
man iptables ??? Contains a description of iptables as well as a comprehensive list of targets, options, and match extensions.
The options used with specific iptables rules must be grouped logically, based on the purpose and conditions of the overall rule, for the rule to be valid. The remainder of this section explains commonly-used options for the iptables command.
2.9.3.1.??Structure of IPTables Command Options
Many iptables commands have the following structure:
<table-name> ??? Specifies which table the rule applies to. If omitted, the filter table is used.
<command> ??? Specifies the action to perform, such as appending or deleting a rule.
<chain-name> ??? Specifies the chain to edit, create, or delete.
<parameter>-<option> pairs ??? Parameters and associated options that specify how to process a packet that matches the rule.
The length and complexity of an iptables command can change significantly, based on its purpose.
For example, a command to remove a rule from a chain can be very short:
iptables -D <chain-name> <line-number>
In contrast, a command that adds a rule which filters packets from a particular subnet using a variety of specific parameters and options can be rather long. When constructing iptables commands, it is important to remember that some parameters and options require further parameters and options to construct a valid rule. This can produce a cascading effect, with the further parameters requiring yet more parameters. Until every parameter and option that requires another set of options is satisfied, the rule is not valid.
Type iptables -h to view a comprehensive list of iptables command structures.
Both ipchains and iptables use chains of rules that operate within the Linux kernel to filter packets based on matches with specified rules or rule sets. However, iptables offers a more extensible way of filtering packets, giving the administrator greater control without building undue complexity into the system.
You should be aware of the following significant differences between ipchains and iptables:
Using iptables, each filtered packet is processed using rules from only one chain rather than multiple chains.
For example, a FORWARD packet coming into a system using ipchains would have to go through the INPUT, FORWARD, and OUTPUT chains to continue to its destination. However, iptables only sends packets to the INPUT chain if they are destined for the local system, and only sends them to the OUTPUT chain if the local system generated the packets. It is therefore important to place the rule designed to catch a particular packet within the chain that actually handles the packet.
The DENY target has been changed to DROP.
In ipchains, packets that matched a rule in a chain could be directed to the DENY target. This target must be changed to DROP in iptables.
Order matters when placing options in a rule.
In ipchains, the order of the rule options does not matter.
The iptables command has a stricter syntax. The iptables command requires that the protocol (ICMP, TCP, or UDP) be specified before the source or destination ports.
Network interfaces must be associated with the correct chains in firewall rules.
For example, incoming interfaces (-i option) can only be used in INPUT or FORWARD chains. Similarly, outgoing interfaces (-o option) can only be used in FORWARD or OUTPUT chains.
In other words, INPUT chains and incoming interfaces work together; OUTPUT chains and outgoing interfaces work together. FORWARD chains work with both incoming and outgoing interfaces.
OUTPUT chains are no longer used by incoming interfaces, and INPUT chains are not seen by packets moving through outgoing interfaces.
There are two basic methods for controlling iptables in Fedora:
Security Level Configuration Tool (system-config-securitylevel) ??? A graphical interface for creating, activating, and saving basic firewall rules. Refer to Section??2.8.2, ???Basic Firewall Configuration??? for more information.
/sbin/service iptables <option> ??? Used to manipulate various functions of iptables using its initscript. The following options are available:
start ??? If a firewall is configured (that is, /etc/sysconfig/iptables exists), all running iptables are stopped completely and then started using the /sbin/iptables-restore command. This option only works if the ipchains kernel module is not loaded. To check if this module is loaded, type the following command as root:
[root at MyServer ~]# lsmod | grep ipchains
If this command returns no output, it means the module is not loaded. If necessary, use the /sbin/rmmod command to remove the module.
stop ??? If a firewall is running, the firewall rules in memory are flushed, and all iptables modules and helpers are unloaded.
If the IPTABLES_SAVE_ON_STOP directive in the /etc/sysconfig/iptables-config configuration file is changed from its default value to yes, current rules are saved to /etc/sysconfig/iptables and any existing rules are moved to the file /etc/sysconfig/iptables.save.
restart ??? If a firewall is running, the firewall rules in memory are flushed, and the firewall is started again if it is configured in /etc/sysconfig/iptables. This option only works if the ipchains kernel module is not loaded.
If the IPTABLES_SAVE_ON_RESTART directive in the /etc/sysconfig/iptables-config configuration file is changed from its default value to yes, current rules are saved to /etc/sysconfig/iptables and any existing rules are moved to the file /etc/sysconfig/iptables.save.
status ??? Displays the status of the firewall and lists all active rules.
The default configuration for this option displays IP addresses in each rule. To display domain and hostname information, edit the /etc/sysconfig/iptables-config file and change the value of IPTABLES_STATUS_NUMERIC to no. Refer to Section??2.9.5.1, ???IPTables Control Scripts Configuration File??? for more information about the iptables-config file.
panic ??? Flushes all firewall rules. The policy of all configured tables is set to DROP.
This option could be useful if a server is known to be compromised. Rather than physically disconnecting from the network or shutting down the system, you can use this option to stop all further network traffic but leave the machine in a state ready for analysis or other forensics.
To use the same initscript commands to control netfilter for IPv6, substitute ip6tables for iptables in the /sbin/service commands listed in this section. For more information about IPv6 and netfilter, refer to Section??2.9.6, ???IPTables and IPv6???.
2.9.5.1.??IPTables Control Scripts Configuration File
The behavior of the iptables initscripts is controlled by the /etc/sysconfig/iptables-config configuration file. The following is a list of directives contained in this file:
IPTABLES_MODULES ??? Specifies a space-separated list of additional iptables modules to load when a firewall is activated. These can include connection tracking and NAT helpers.
IPTABLES_MODULES_UNLOAD ??? Unloads modules on restart and stop. This directive accepts the following values:
yes ??? The default value. This option must be set to achieve a correct state for a firewall restart or stop.
no ??? This option should only be set if there are problems unloading the netfilter modules.
IPTABLES_SAVE_ON_STOP ??? Saves current firewall rules to /etc/sysconfig/iptables when the firewall is stopped. This directive accepts the following values:
yes ??? Saves existing rules to /etc/sysconfig/iptables when the firewall is stopped, moving the previous version to the /etc/sysconfig/iptables.save file.
no ??? The default value. Does not save existing rules when the firewall is stopped.
IPTABLES_SAVE_ON_RESTART ??? Saves current firewall rules when the firewall is restarted. This directive accepts the following values:
yes ??? Saves existing rules to /etc/sysconfig/iptables when the firewall is restarted, moving the previous version to the /etc/sysconfig/iptables.save file.
no ??? The default value. Does not save existing rules when the firewall is restarted.
IPTABLES_SAVE_COUNTER ??? Saves and restores all packet and byte counters in all chains and rules. This directive accepts the following values:
yes ??? Saves the counter values.
no ??? The default value. Does not save the counter values.
IPTABLES_STATUS_NUMERIC ??? Outputs IP addresses in numeric form instead of domain or hostnames. This directive accepts the following values:
yes ??? The default value. Returns only IP addresses within a status output.
no ??? Returns domain or hostnames within a status output.
If the iptables-ipv6 package is installed, netfilter in Fedora can filter the next-generation IPv6 Internet protocol. The command used to manipulate the IPv6 netfilter is ip6tables.
Most directives for this command are identical to those used for iptables, except the nat table is not yet supported. This means that it is not yet possible to perform IPv6 network address translation tasks, such as masquerading and port forwarding.
Rules for ip6tables are saved in the /etc/sysconfig/ip6tables file. Previous rules saved by the ip6tables initscripts are saved in the /etc/sysconfig/ip6tables.save file.
Configuration options for the ip6tables init script are stored in /etc/sysconfig/ip6tables-config, and the names for each directive vary slightly from their iptables counterparts.
For example, the iptables-config directive IPTABLES_MODULES:the equivalent in the ip6tables-config file is IP6TABLES_MODULES.
Rules created with the iptables command are stored in memory. If the system is restarted before saving the iptables rule set, all rules are lost. For netfilter rules to persist through a system reboot, they need to be saved. To save netfilter rules, type the following command as root:
/sbin/service iptables save
This executes the iptables init script, which runs the /sbin/iptables-save program and writes the current iptables configuration to /etc/sysconfig/iptables. The existing /etc/sysconfig/iptables file is saved as /etc/sysconfig/iptables.save.
The next time the system boots, the iptables init script reapplies the rules saved in /etc/sysconfig/iptables by using the /sbin/iptables-restore command.
While it is always a good idea to test a new iptables rule before committing it to the /etc/sysconfig/iptables file, it is possible to copy iptables rules into this file from another system's version of this file. This provides a quick way to distribute sets of iptables rules to multiple machines.
You can also save the iptables rules to a separate file for distribution, backup or other purposes. To save your iptables rules, type the following command as root:
[root at myserver ~]# iptables-save > <filename>where <filename> is a user-defined name for your ruleset.
Important
If distributing the /etc/sysconfig/iptables file to other machines, type /sbin/service iptables restart for the new rules to take effect.
Note
Note the difference between the iptablescommand (/sbin/iptables), which is used to manipulate the tables and chains that constitute the iptables functionality, and the iptablesservice (/sbin/iptables service), which is used to enable and disable the iptables service itself.
Included with Fedora are advanced tools for network packet filtering ??? the process of controlling network packets as they enter, move through, and exit the network stack within the kernel. Kernel versions prior to 2.4 relied on ipchains for packet filtering and used lists of rules applied to packets at each step of the filtering process. The 2.4 kernel introduced iptables (also called netfilter), which is similar to ipchains but greatly expands the scope and control available for filtering network packets.
This chapter focuses on packet filtering basics, defines the differences between ipchains and iptables, explains various options available with iptables commands, and explains how filtering rules can be preserved between system reboots.
The default firewall mechanism in the 2.4 and later kernels is iptables, but iptables cannot be used if ipchains is already running. If ipchains is present at boot time, the kernel issues an error and fails to start iptables.
The functionality of ipchains is not affected by these errors.
2.9.1.??Packet Filtering
The Linux kernel uses the Netfilter facility to filter packets, allowing some of them to be received by or pass through the system while stopping others. This facility is built in to the Linux kernel, and has three built-in tables or rules lists, as follows:
filter ??? The default table for handling network packets.
nat ??? Used to alter packets that create a new connection and used for Network Address Translation (NAT).
mangle ??? Used for specific types of packet alteration.
Each table has a group of built-in chains, which correspond to the actions performed on the packet by netfilter.
The built-in chains for the filter table are as follows:
INPUT ??? Applies to network packets that are targeted for the host.
OUTPUT ??? Applies to locally-generated network packets.
FORWARD ??? Applies to network packets routed through the host.
The built-in chains for the nat table are as follows:
PREROUTING ??? Alters network packets when they arrive.
OUTPUT ??? Alters locally-generated network packets before they are sent out.
POSTROUTING ??? Alters network packets before they are sent out.
The built-in chains for the mangle table are as follows:
INPUT ??? Alters network packets targeted for the host.
OUTPUT ??? Alters locally-generated network packets before they are sent out.
FORWARD ??? Alters network packets routed through the host.
PREROUTING ??? Alters incoming network packets before they are routed.
POSTROUTING ??? Alters network packets before they are sent out.
Every network packet received by or sent from a Linux system is subject to at least one table. However, a packet may be subjected to multiple rules within each table before emerging at the end of the chain. The structure and purpose of these rules may vary, but they usually seek to identify a packet coming from or going to a particular IP address, or set of addresses, when using a particular protocol and network service.
Note
By default, firewall rules are saved in the /etc/sysconfig/iptables or /etc/sysconfig/ip6tables files.
The iptables service starts before any DNS-related services when a Linux system is booted. This means that firewall rules can only reference numeric IP addresses (for example, 192.168.0.1). Domain names (for example, host.example.com) in such rules produce errors.
Regardless of their destination, when packets match a particular rule in one of the tables, a target or action is applied to them. If the rule specifies an ACCEPT target for a matching packet, the packet skips the rest of the rule checks and is allowed to continue to its destination. If a rule specifies a DROP target, that packet is refused access to the system and nothing is sent back to the host that sent the packet. If a rule specifies a QUEUE target, the packet is passed to user-space. If a rule specifies the optional REJECT target, the packet is dropped, but an error packet is sent to the packet's originator.
Every chain has a default policy to ACCEPT, DROP, REJECT, or QUEUE. If none of the rules in the chain apply to the packet, then the packet is dealt with in accordance with the default policy.
The iptables command configures these tables, as well as sets up new tables if necessary.
Additional match options are available through modules loaded by the iptables command.
To use a match option module, load the module by name using the -m <module-name>, where <module-name> is the name of the module.
Many modules are available by default. You can also create modules to provide additional functionality.
The following is a partial list of the most commonly used modules:
limit module ??? Places limits on how many packets are matched to a particular rule.
When used in conjunction with the LOG target, the limit module can prevent a flood of matching packets from filling up the system log with repetitive messages or using up system resources.
--limit ??? Sets the maximum number of matches for a particular time period, specified as a <value>/<period> pair. For example, using --limit 5/hour allows five rule matches per hour.
Periods can be specified in seconds, minutes, hours, or days.
If a number and time modifier are not used, the default value of 3/hour is assumed.
--limit-burst ??? Sets a limit on the number of packets able to match a rule at one time.
This option is specified as an integer and should be used in conjunction with the --limit option.
If no value is specified, the default value of five (5) is assumed.
state module ??? Enables state matching.
The state module enables the following options:
--state ??? match a packet with the following connection states:
ESTABLISHED ??? The matching packet is associated with other packets in an established connection. You need to accept this state if you want to maintain a connection between a client and a server.
INVALID ??? The matching packet cannot be tied to a known connection.
NEW ??? The matching packet is either creating a new connection or is part of a two-way connection not previously seen. You need to accept this state if you want to allow new connections to a service.
RELATED ??? The matching packet is starting a new connection related in some way to an existing connection. An example of this is FTP, which uses one connection for control traffic (port 21), and a separate connection for data transfer (port 20).
These connection states can be used in combination with one another by separating them with commas, such as -m state --state INVALID,NEW.
mac module ??? Enables hardware MAC address matching.
The mac module enables the following option:
--mac-source ??? Matches a MAC address of the network interface card that sent the packet. To exclude a MAC address from a rule, place an exclamation point character (!) after the --mac-source match option.
Refer to the iptables man page for more match options available through modules.
The following match options are available for the Internet Control Message Protocol (ICMP) (-p icmp):
--icmp-type ??? Sets the name or number of the ICMP type to match with the rule. A list of valid ICMP names can be retrieved by typing the iptables -p icmp -h command.
These match options are available for the UDP protocol (-p udp):
--dport ??? Specifies the destination port of the UDP packet, using the service name, port number, or range of port numbers. The --destination-port match option is synonymous with --dport.
--sport ??? Specifies the source port of the UDP packet, using the service name, port number, or range of port numbers. The --source-port match option is synonymous with --sport.
For the --dport and --sport options, to specify a range of port numbers, separate the two numbers with a colon (:). For example: -p tcp --dport 3000:3200. The largest acceptable valid range is 0:65535.
The first step in creating a connection is to gather system and network information from each workstation. For a host-to-host connection, you need the following:
The IP address of each host
A unique name, for example, ipsec1. This is used to identify the IPsec connection and to distinguish it from other devices or connections.
A fixed encryption key or one automatically generated by racoon.
A pre-shared authentication key that is used during the initial stage of the connection and to exchange encryption keys during the session.
For example, suppose Workstation A and Workstation B want to connect to each other through an IPsec tunnel. They want to connect using a pre-shared key with the value of Key_Value01, and the users agree to let racoon automatically generate and share an authentication key between each host. Both host users decide to name their connections ipsec1.
Note
You should choose a PSK that uses a mixture of upper- and lower-case characters, numbers and punctuation. An easily-guessable PSK constitutes a security risk.
It is not necessary to use the same connection name for each host. You should choose a name that is convenient and meaningful for your installation.
The following is the IPsec configuration file for Workstation A for a host-to-host IPsec connection with Workstation B. The unique name to identify the connection in this example is ipsec1, so the resulting file is called /etc/sysconfig/network-scripts/ifcfg-ipsec1.
DST=X.X.X.XTYPE=IPSEC
ONBOOT=no
IKE_METHOD=PSK
For Workstation A, X.X.X.X is the IP address of Workstation B. For Workstation B, X.X.X.X is the IP address of Workstation A. This connection is not set to initiate on boot-up (ONBOOT=no) and it uses the pre-shared key method of authentication (IKE_METHOD=PSK).
The following is the content of the pre-shared key file (called /etc/sysconfig/network-scripts/keys-ipsec1) that both workstations need to authenticate each other. The contents of this file should be identical on both workstations, and only the root user should be able to read or write this file.
IKE_PSK=Key_Value01
Important
To change the keys-ipsec1 file so that only the root user can read or edit the file, use the following command after creating the file:
[root at myServer ~] # chmod 600 /etc/sysconfig/network-scripts/keys-ipsec1
To change the authentication key at any time, edit the keys-ipsec1 file on both workstations. Both authentication keys must be identical for proper connectivity.
The next example shows the specific configuration for the phase 1 connection to the remote host. The file is called X.X.X.X.conf, where X.X.X.X is the IP address of the remote IPsec host. Note that this file is automatically generated when the IPsec tunnel is activated and should not be edited directly.
The default phase 1 configuration file that is created when an IPsec connection is initialized contains the following statements used by the Fedora implementation of IPsec:
remote X.X.X.X
Specifies that the subsequent stanzas of this configuration file apply only to the remote node identified by the X.X.X.X IP address.
exchange_mode aggressive
The default configuration for IPsec on Fedora uses an aggressive authentication mode, which lowers the connection overhead while allowing configuration of several IPsec connections with multiple hosts.
my_identifier address
Specifies the identification method to use when authenticating nodes. Fedora uses IP addresses to identify nodes.
encryption_algorithm 3des
Specifies the encryption cipher used during authentication. By default, Triple Data Encryption Standard (3DES) is used.
hash_algorithm sha1;
Specifies the hash algorithm used during phase 1 negotiation between nodes. By default, Secure Hash Algorithm version 1 is used.
authentication_method pre_shared_key
Specifies the authentication method used during node negotiation. By default, Fedora uses pre-shared keys for authentication.
dh_group 2
Specifies the Diffie-Hellman group number for establishing dynamically-generated session keys. By default, modp1024 (group 2) is used.
2.7.6.2.1.??The Racoon Configuration File
The /etc/racoon/racoon.conf files should be identical on all IPsec nodes except for the include "/etc/racoon/X.X.X.X.conf" statement. This statement (and the file it references) is generated when the IPsec tunnel is activated. For Workstation A, the X.X.X.X in the include statement is Workstation B's IP address. The opposite is true of Workstation B. The following shows a typical racoon.conf file when the IPsec connection is activated.
# Racoon IKE daemon configuration file.
# See 'man racoon.conf' for a description of the format and entries.
path include "/etc/racoon";
path pre_shared_key "/etc/racoon/psk.txt";
path certificate "/etc/racoon/certs";
sainfo anonymous
{
pfs_group 2;
lifetime time 1 hour ;
encryption_algorithm 3des, blowfish 448, rijndael ;
authentication_algorithm hmac_sha1, hmac_md5 ;
compression_algorithm deflate ;
}
include "/etc/racoon/X.X.X.X.conf";
This default racoon.conf file includes defined paths for IPsec configuration, pre-shared key files, and certificates. The fields in sainfo anonymous describe the phase 2 SA between the IPsec nodes ??? the nature of the IPsec connection (including the supported encryption algorithms used) and the method of exchanging keys. The following list defines the fields of phase 2:
sainfo anonymous
Denotes that SA can anonymously initialize with any peer provided that the IPsec credentials match.
pfs_group 2
Defines the Diffie-Hellman key exchange protocol, which determines the method by which the IPsec nodes establish a mutual temporary session key for the second phase of IPsec connectivity. By default, the Fedora implementation of IPsec uses group 2 (or modp1024) of the Diffie-Hellman cryptographic key exchange groups. Group 2 uses a 1024-bit modular exponentiation that prevents attackers from decrypting previous IPsec transmissions even if a private key is compromised.
lifetime time 1 hour
This parameter specifies the lifetime of an SA and can be quantified either by time or by bytes of data. The default Fedora implementation of IPsec specifies a one hour lifetime.
encryption_algorithm 3des, blowfish 448, rijndael
Specifies the supported encryption ciphers for phase 2. Fedora supports 3DES, 448-bit Blowfish, and Rijndael (the cipher used in the Advanced Encryption Standard, or AES).
authentication_algorithm hmac_sha1, hmac_md5
Lists the supported hash algorithms for authentication. Supported modes are sha1 and md5 hashed message authentication codes (HMAC).
compression_algorithm deflate
Defines the Deflate compression algorithm for IP Payload Compression (IPCOMP) support, which allows for potentially faster transmission of IP datagrams over slow connections.
To start the connection, use the following command on each host:
[root at myServer ~]# /sbin/ifup <nickname>
where <nickname> is the name you specified for the IPsec connection.
To test the IPsec connection, run the tcpdump utility to view the network packets being transfered between the hosts and verify that they are encrypted via IPsec. The packet should include an AH header and should be shown as ESP packets. ESP means it is encrypted. For example:
[root at myServer ~]# tcpdump -n -i eth0 host <targetSystem>
IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f2164,seq=0xbb)
Suppose LAN A (lana.example.com) and LAN B (lanb.example.com) want to connect to each other through an IPsec tunnel. The network address for LAN A is in the 192.168.1.0/24 range, while LAN B uses the 192.168.2.0/24 range. The gateway IP address is 192.168.1.254 for LAN A and 192.168.2.254 for LAN B. The IPsec routers are separate from each LAN gateway and use two network devices: eth0 is assigned to an externally-accessible static IP address which accesses the Internet, while eth1 acts as a routing point to process and transmit LAN packets from one network node to the remote network nodes.
The IPsec connection between each network uses a pre-shared key with the value of r3dh4tl1nux, and the administrators of A and B agree to let racoon automatically generate and share an authentication key between each IPsec router. The administrator of LAN A decides to name the IPsec connection ipsec0, while the administrator of LAN B names the IPsec connection ipsec1.
The following example shows the contents of the ifcfg file for a network-to-network IPsec connection for LAN A. The unique name to identify the connection in this example is ipsec0, so the resulting file is called /etc/sysconfig/network-scripts/ifcfg-ipsec0.
The following list describes the contents of this file:
TYPE=IPSEC
Specifies the type of connection.
ONBOOT=yes
Specifies that the connection should initiate on boot-up.
IKE_METHOD=PSK
Specifies that the connection uses the pre-shared key method of authentication.
SRCGW=192.168.1.254
The IP address of the source gateway. For LAN A, this is the LAN A gateway, and for LAN B, the LAN B gateway.
DSTGW=192.168.2.254
The IP address of the destination gateway. For LAN A, this is the LAN B gateway, and for LAN B, the LAN A gateway.
SRCNET=192.168.1.0/24
Specifies the source network for the IPsec connection, which in this example is the network range for LAN A.
DSTNET=192.168.2.0/24
Specifies the destination network for the IPsec connection, which in this example is the network range for LAN B.
DST=X.X.X.X
The externally-accessible IP address of LAN B.
The following example is the content of the pre-shared key file called /etc/sysconfig/network-scripts/keys-ipsecX (where X is 0 for LAN A and 1 for LAN B) that both networks use to authenticate each other. The contents of this file should be identical and only the root user should be able to read or write this file.
IKE_PSK=r3dh4tl1nux
Important
To change the keys-ipsecX file so that only the root user can read or edit the file, use the following command after creating the file:
To change the authentication key at any time, edit the keys-ipsecX file on both IPsec routers. Both keys must be identical for proper connectivity.
The following example is the contents of the /etc/racoon/racoon.conf configuration file for the IPsec connection. Note that the include line at the bottom of the file is automatically generated and only appears if the IPsec tunnel is running.
# Racoon IKE daemon configuration file.
# See 'man racoon.conf' for a description of the format and entries.
path include "/etc/racoon";
path pre_shared_key "/etc/racoon/psk.txt";
path certificate "/etc/racoon/certs";
sainfo anonymous
{
pfs_group 2;
lifetime time 1 hour ;
encryption_algorithm 3des, blowfish 448, rijndael ;
authentication_algorithm hmac_sha1, hmac_md5 ;
compression_algorithm deflate ;
}
include "/etc/racoon/X.X.X.X.conf"
The following is the specific configuration for the connection to the remote network. The file is called X.X.X.X.conf (where X.X.X.X is the IP address of the remote IPsec router). Note that this file is automatically generated when the IPsec tunnel is activated and should not be edited directly.
Prior to starting the IPsec connection, IP forwarding should be enabled in the kernel. To enable IP forwarding:
Edit /etc/sysctl.conf and set net.ipv4.ip_forward to 1.
Use the following command to enable the change:
[root at myServer ~] # sysctl -p /etc/sysctl.conf
To start the IPsec connection, use the following command on each router:
[root at myServer ~] # /sbin/ifup ipsec0
The connections are activated, and both LAN A and LAN B are able to communicate with each other. The routes are created automatically via the initialization script called by running ifup on the IPsec connection. To show a list of routes for the network, use the following command:
[root at myServer ~] # /sbin/ip route list
To test the IPsec connection, run the tcpdump utility on the externally-routable device (eth0 in this example) to view the network packets being transfered between the hosts (or networks), and verify that they are encrypted via IPsec. For example, to check the IPsec connectivity of LAN A, use the following command:
The packet should include an AH header and should be shown as ESP packets. ESP means it is encrypted. For example (back slashes denote a continuation of one line):
For more information about Kerberos, refer to the following resources.
2.6.10.1.??Installed Kerberos Documentation
The Kerberos V5 Installation Guide and the Kerberos V5 System Administrator's Guide in PostScript and HTML formats. These can be found in the /usr/share/doc/krb5-server-<version-number>/ directory (where <version-number> is the version number of the krb5-server package installed on your system).
The Kerberos V5 UNIX User's Guide in PostScript and HTML formats. These can be found in the /usr/share/doc/krb5-workstation-<version-number>/ directory (where <version-number> is the version number of the krb5-workstation package installed on your system).
Kerberos man pages ??? There are a number of man pages for the various applications and configuration files involved with a Kerberos implementation. The following is a list of some of the more important man pages.
Client Applications
man kerberos ??? An introduction to the Kerberos system which describes how credentials work and provides recommendations for obtaining and destroying Kerberos tickets. The bottom of the man page references a number of related man pages.
man kinit ??? Describes how to use this command to obtain and cache a ticket-granting ticket.
man kdestroy ??? Describes how to use this command to destroy Kerberos credentials.
man klist ??? Describes how to use this command to list cached Kerberos credentials.
Administrative Applications
man kadmin ??? Describes how to use this command to administer the Kerberos V5 database.
man kdb5_util ??? Describes how to use this command to create and perform low-level administrative functions on the Kerberos V5 database.
Server Applications
man krb5kdc ??? Describes available command line options for the Kerberos V5 KDC.
man kadmind ??? Describes available command line options for the Kerberos V5 administration server.
Configuration Files
man krb5.conf ??? Describes the format and options available within the configuration file for the Kerberos V5 library.
man kdc.conf ??? Describes the format and options available within the configuration file for the Kerberos V5 AS and KDC.
Setting up a Kerberos 5 client is less involved than setting up a server. At a minimum, install the client packages and provide each client with a valid krb5.conf configuration file. While ssh and slogin are the preferred method of remotely logging in to client systems, Kerberized versions of rsh and rlogin are still available, though deploying them requires that a few more configuration changes be made.
Be sure that time synchronization is in place between the Kerberos client and the KDC. Refer to Section??2.6.5, ???Configuring a Kerberos 5 Server??? for more information. In addition, verify that DNS is working properly on the Kerberos client before configuring the Kerberos client programs.
Install the krb5-libs and krb5-workstation packages on all of the client machines. Supply a valid /etc/krb5.conf file for each client (usually this can be the same krb5.conf file used by the KDC).
Before a workstation in the realm can use Kerberos to authenticate users who connect using ssh or Kerberized rsh or rlogin, it must have its own host principal in the Kerberos database. The sshd, kshd, and klogind server programs all need access to the keys for the host service's principal. Additionally, in order to use the kerberized rsh and rlogin services, that workstation must have the xinetd package installed.
Using kadmin, add a host principal for the workstation on the KDC. The instance in this case is the hostname of the workstation. Use the -randkey option for the kadmin's addprinc command to create the principal and assign it a random key:
addprinc -randkey host/blah.example.com
Now that the principal has been created, keys can be extracted for the workstation by running kadminon the workstation itself, and using the ktadd command within kadmin:
ktadd -k /etc/krb5.keytab host/blah.example.com
To use other kerberized network services, they must first be started. Below is a list of some common kerberized services and instructions about enabling them:
ssh ??? OpenSSH uses GSS-API to authenticate users to servers if the client's and server's configuration both have GSSAPIAuthentication enabled. If the client also has GSSAPIDelegateCredentials enabled, the user's credentials are made available on the remote system.
rsh and rlogin ??? To use the kerberized versions of rsh and rlogin, enable klogin, eklogin, and kshell.
Telnet ??? To use kerberized Telnet, krb5-telnet must be enabled.
FTP ??? To provide FTP access, create and extract a key for the principal with a root of ftp. Be certain to set the instance to the fully qualified hostname of the FTP server, then enable gssftp.
IMAP ??? To use a kerberized IMAP server, the cyrus-imap package uses Kerberos 5 if it also has the cyrus-sasl-gssapi package installed. The cyrus-sasl-gssapi package contains the Cyrus SASL plugins which support GSS-API authentication. Cyrus IMAP should function properly with Kerberos as long as the cyrus user is able to find the proper key in /etc/krb5.keytab, and the root for the principal is set to imap (created with kadmin).
An alternative to cyrus-imap can be found in the dovecot package, which is also included in Fedora. This package contains an IMAP server but does not, to date, support GSS-API and Kerberos.
CVS ??? To use a kerberized CVS server, gserver uses a principal with a root of cvs and is otherwise identical to the CVS pserver.
When setting up Kerberos, install the KDC first. If it is necessary to set up slave servers, install the master first.
To configure the first Kerberos KDC, follow these steps:
Ensure that time synchronization and DNS are functioning correctly on all client and server machines before configuring Kerberos. Pay particular attention to time synchronization between the Kerberos server and its clients. If the time difference between the server and client is greater than five minutes (this is configurable in Kerberos 5), Kerberos clients can not authenticate to the server. This time synchronization is necessary to prevent an attacker from using an old Kerberos ticket to masquerade as a valid user.
It is advisable to set up a Network Time Protocol (NTP) compatible client/server network even if Kerberos is not being used. Fedora includes the ntp package for this purpose. Refer to /usr/share/doc/ntp-<version-number>/index.html (where <version-number> is the version number of the ntp package installed on your system) for details about how to set up Network Time Protocol servers, and http://www.ntp.org for more information about NTP.
Install the krb5-libs, krb5-server, and krb5-workstation packages on the dedicated machine which runs the KDC. This machine needs to be very secure ??? if possible, it should not run any services other than the KDC.
Edit the /etc/krb5.conf and /var/kerberos/krb5kdc/kdc.conf configuration files to reflect the realm name and domain-to-realm mappings. A simple realm can be constructed by replacing instances of EXAMPLE.COM and example.com with the correct domain name ??? being certain to keep uppercase and lowercase names in the correct format ??? and by changing the KDC from kerberos.example.com to the name of the Kerberos server. By convention, all realm names are uppercase and all DNS hostnames and domain names are lowercase. For full details about the formats of these configuration files, refer to their respective man pages.
Create the database using the kdb5_util utility from a shell prompt:
/usr/kerberos/sbin/kdb5_util create -s
The create command creates the database that stores keys for the Kerberos realm. The -s switch forces creation of a stash file in which the master server key is stored. If no stash file is present from which to read the key, the Kerberos server (krb5kdc) prompts the user for the master server password (which can be used to regenerate the key) every time it starts.
Edit the /var/kerberos/krb5kdc/kadm5.acl file. This file is used by kadmind to determine which principals have administrative access to the Kerberos database and their level of access. Most organizations can get by with a single line:
*/admin at EXAMPLE.COM????*
Most users are represented in the database by a single principal (with a NULL, or empty, instance, such as joe at EXAMPLE.COM). In this configuration, users with a second principal with an instance of admin (for example, joe/admin at EXAMPLE.COM) are able to wield full power over the realm's Kerberos database.
After kadmind has been started on the server, any user can access its services by running kadmin on any of the clients or servers in the realm. However, only users listed in the kadm5.acl file can modify the database in any way, except for changing their own passwords.
Note
The kadmin utility communicates with the kadmind server over the network, and uses Kerberos to handle authentication. Consequently, the first principal must already exist before connecting to the server over the network to administer it. Create the first principal with the kadmin.local command, which is specifically designed to be used on the same host as the KDC and does not use Kerberos for authentication.
Type the following kadmin.local command at the KDC terminal to create the first principal:
Add principals for the users using the addprinc command within kadmin. kadmin and kadmin.local are command line interfaces to the KDC. As such, many commands ??? such as addprinc ??? are available after launching the kadmin program. Refer to the kadmin man page for more information.
Verify that the KDC is issuing tickets. First, run kinit to obtain a ticket and store it in a credential cache file. Next, use klist to view the list of credentials in the cache and use kdestroy to destroy the cache and the credentials it contains.
Note
By default, kinit attempts to authenticate using the same system login username (not the Kerberos server). If that username does not correspond to a principal in the Kerberos database, kinit issues an error message. If that happens, supply kinit with the name of the correct principal as an argument on the command line (kinit <principal>).
Once these steps are completed, the Kerberos server should be up and running.
When a client attempts to access a service running on a particular server, it knows the name of the service (host) and the name of the server (foo.example.com), but because more than one realm may be deployed on your network, it must guess at the name of the realm in which the service resides.
By default, the name of the realm is taken to be the DNS domain name of the server, upper-cased.
In some configurations, this will be sufficient, but in others, the realm name which is derived will be the name of a non-existant realm. In these cases, the mapping from the server's DNS domain name to the name of its realm must be specified in the domain_realm section of the client system's krb5.conf. For example:
The above configuration specifies two mappings. The first mapping specifies that any system in the "example.com" DNS domain belongs to the EXAMPLE.COM realm. The second specifies that a system with the exact name "example.com" is also in the realm. (The distinction between a domain and a specific host is marked by the presence or lack of an initial ".".) The mapping can also be stored directly in DNS.
Kerberos differs from username/password authentication methods. Instead of authenticating each user to each network service, Kerberos uses symmetric encryption and a trusted third party (a KDC), to authenticate users to a suite of network services. When a user authenticates to the KDC, the KDC sends a ticket specific to that session back to the user's machine, and any Kerberos-aware services look for the ticket on the user's machine rather than requiring the user to authenticate using a password.
When a user on a Kerberos-aware network logs in to their workstation, their principal is sent to the KDC as part of a request for a TGT from the Authentication Server. This request can be sent by the log-in program so that it is transparent to the user, or can be sent by the kinit program after the user logs in.
The KDC then checks for the principal in its database. If the principal is found, the KDC creates a TGT, which is encrypted using the user's key and returned to that user.
The login or kinit program on the client then decrypts the TGT using the user's key, which it computes from the user's password. The user's key is used only on the client machine and is not transmitted over the network.
The TGT is set to expire after a certain period of time (usually ten to twenty-four hours) and is stored in the client machine's credentials cache. An expiration time is set so that a compromised TGT is of use to an attacker for only a short period of time. After the TGT has been issued, the user does not have to re-enter their password until the TGT expires or until they log out and log in again.
Whenever the user needs access to a network service, the client software uses the TGT to request a new ticket for that specific service from the TGS. The service ticket is then used to authenticate the user to that service transparently.
Warning
The Kerberos system can be compromised if a user on the network authenticates against a non-Kerberos aware service by transmitting a password in plain text. The use of non-Kerberos aware services is highly discouraged. Such services include Telnet and FTP. The use of other encrypted protocols, such as SSH or SSL-secured services, however, is preferred, although not ideal.
Kerberos depends on the following network services to function correctly.
Approximate clock synchronization between the machines on the network.
A clock synchronization program should be set up for the network, such as ntpd. Refer to /usr/share/doc/ntp-<version-number>/index.html for details on setting up Network Time Protocol servers (where <version-number> is the version number of the ntp package installed on your system).
Domain Name Service (DNS).
You should ensure that the DNS entries and hosts on the network are all properly configured. Refer to the Kerberos V5 System Administrator's Guide in /usr/share/doc/krb5-server-<version-number> for more information (where <version-number> is the version number of the krb5-server package installed on your system).
Kerberos has its own terminology to define various aspects of the service. Before learning how Kerberos works, it is important to learn the following terms.
authentication server (AS)
A server that issues tickets for a desired service which are in turn given to users for access to the service. The AS responds to requests from clients who do not have or do not send credentials with a request. It is usually used to gain access to the ticket-granting server (TGS) service by issuing a ticket-granting ticket (TGT). The AS usually runs on the same host as the key distribution center (KDC).
ciphertext
Encrypted data.
client
An entity on the network (a user, a host, or an application) that can receive a ticket from Kerberos.
credentials
A temporary set of electronic credentials that verify the identity of a client for a particular service. Also called a ticket.
credential cache or ticket file
A file which contains the keys for encrypting communications between a user and various network services. Kerberos 5 supports a framework for using other cache types, such as shared memory, but files are more thoroughly supported.
crypt hash
A one-way hash used to authenticate users. These are more secure than using unencrypted data, but they are still relatively easy to decrypt for an experienced cracker.
GSS-API
The Generic Security Service Application Program Interface (defined in RFC-2743 published by The Internet Engineering Task Force) is a set of functions which provide security services. This API is used by clients and services to authenticate to each other without either program having specific knowledge of the underlying mechanism. If a network service (such as cyrus-IMAP) uses GSS-API, it can authenticate using Kerberos.
hash
Also known as a hash value. A value generated by passing a string through a hash function. These values are typically used to ensure that transmitted data has not been tampered with.
hash function
A way of generating a digital "fingerprint" from input data. These functions rearrange, transpose or otherwise alter data to produce a hash value.
key
Data used when encrypting or decrypting other data. Encrypted data cannot be decrypted without the proper key or extremely good fortune on the part of the cracker.
key distribution center (KDC)
A service that issues Kerberos tickets, and which usually run on the same host as the ticket-granting server (TGS).
keytab (or key table)
A file that includes an unencrypted list of principals and their keys. Servers retrieve the keys they need from keytab files instead of using kinit. The default keytab file is /etc/krb5.keytab. The KDC administration server, /usr/kerberos/sbin/kadmind, is the only service that uses any other file (it uses /var/kerberos/krb5kdc/kadm5.keytab).
kinit
The kinit command allows a principal who has already logged in to obtain and cache the initial ticket-granting ticket (TGT). Refer to the kinit man page for more information.
principal (or principal name)
The principal is the unique name of a user or service allowed to authenticate using Kerberos. A principal follows the form root[/instance]@REALM. For a typical user, the root is the same as their login ID. The instance is optional. If the principal has an instance, it is separated from the root with a forward slash ("/"). An empty string ("") is considered a valid instance (which differs from the default NULL instance), but using it can be confusing. All principals in a realm have their own key, which for users is derived from a password or is randomly set for services.
realm
A network that uses Kerberos, composed of one or more servers called KDCs and a potentially large number of clients.
service
A program accessed over the network.
ticket
A temporary set of electronic credentials that verify the identity of a client for a particular service. Also called credentials.
ticket-granting server (TGS)
A server that issues tickets for a desired service which are in turn given to users for access to the service. The TGS usually runs on the same host as the KDC.
ticket-granting ticket (TGT)
A special ticket that allows the client to obtain additional tickets without applying for them from the KDC.
Kerberos-aware services do not currently make use of Pluggable Authentication Modules (PAM) ??? these services bypass PAM completely. However, applications that use PAM can make use of Kerberos for authentication if the pam_krb5 module (provided in the pam_krb5 package) is installed. The pam_krb5 package contains sample configuration files that allow services such as login and gdm to authenticate users as well as obtain initial credentials using their passwords. If access to network servers is always performed using Kerberos-aware services or services that use GSS-API, such as IMAP, the network can be considered reasonably safe.
Tip
Administrators should be careful not to allow users to authenticate to most network services using Kerberos passwords. Many protocols used by these services do not encrypt the password before sending it over the network, destroying the benefits of the Kerberos system. For example, users should not be allowed to authenticate to Telnet services with the same password they use for Kerberos authentication.
Cross-realm authentication is the term which is used to describe situations in which clients (typically users) of one realm use Kerberos to authenticate to services (typically server processes running on a particular server system) which belong to a realm other than their own.
For the simplest case, in order for a client of a realm named A.EXAMPLE.COM to access a service in the B.EXAMPLE.COM realm, both realms must share a key for a principal named krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM, and both keys must have the same key version number associated with them.
To accomplish this, select a very strong password or passphrase, and create an entry for the principal in both realms using kadmin.
#??kadmin??-r??A.EXAMPLE.COMkadmin:??add_principal??krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COMEnter??password??for??principal??"krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":Re-enter??password??for??principal??"krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":Principal??"krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM"??created.quit#??kadmin??-r??B.EXAMPLE.COMkadmin:??add_principal??krbtgt/B.EXAM
PLE.COM at A.EXAMPLE.COMEnter??password??for??principal??"krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":Re-enter??password??for??principal??"krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":Principal??"krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM"??created.quit
Use the get_principal command to verify that both entries have matching key version numbers (kvno values) and encryption types.
Dumping the Database Doesn't Do It
Security-conscious administrators may attempt to use the add_principal command's -randkey option to assign a random key instead of a password, dump the new entry from the database of the first realm, and import it into the second. This will not work unless the master keys for the realm databases are identical, as the keys contained in a database dump are themselves encrypted using the master key.
Clients in the A.EXAMPLE.COM realm are now able to authenticate to services in the B.EXAMPLE.COM realm. Put another way, the B.EXAMPLE.COM realm now trusts the A.EXAMPLE.COM realm, or phrased even more simply, B.EXAMPLE.COM now trustsA.EXAMPLE.COM.
This brings us to an important point: cross-realm trust is unidirectional by default. The KDC for the B.EXAMPLE.COM realm may trust clients from the A.EXAMPLE.COM to authenticate to services in the B.EXAMPLE.COM realm, but the fact that it does has no effect on whether or not clients in the B.EXAMPLE.COM realm are trusted to authenticate to services in the A.EXAMPLE.COM realm. To establish trust in the other direction, both realms would need to share keys for the krbtgt/A.EXAMPLE.COM at B.EXAMPLE.COM service (take note of the reversed in order of the two realms compared to the example above).
If direct trust relationships were the only method for providing trust between realms, networks which contain multiple realms would be very difficult to set up. Luckily, cross-realm trust is transitive. If clients from A.EXAMPLE.COM can authenticate to services in B.EXAMPLE.COM, and clients from B.EXAMPLE.COM can authenticate to services in C.EXAMPLE.COM, then clients in A.EXAMPLE.COM can also authenticate to services in C.EXAMPLE.COM, even if C.EXAMPLE.COM doesn't directly trust A.EXAMPLE.COM. This means that, on a network with multiple realms which all need to trust each other, making good choices about which trust relationships to set up can greatly reduce the amount of effort required.
Now you face the more conventional problems: the client's system must be configured so that it can properly deduce the realm to which a particular service belongs, and it must be able to determine how to obtain credentials for services in that realm.
First things first: the principal name for a service provided from a specific server system in a given realm typically looks like this:
service/server.example.com at EXAMPLE.COM
In this example, service is typically either the name of the protocol in use (other common values include ldap, imap, cvs, and HTTP) or host, server.example.com is the fully-qualified domain name of the system which runs the service, and EXAMPLE.COM is the name of the realm.
To deduce the realm to which the service belongs, clients will most often consult DNS or the domain_realm section of /etc/krb5.conf to map either a hostname (server.example.com) or a DNS domain name (.example.com) to the name of a realm (EXAMPLE.COM).
Having determined which to which realm a service belongs, a client then has to determine the set of realms which it needs to contact, and in which order it must contact them, to obtain credentials for use in authenticating to the service.
This can be done in one of two ways.
The default method, which requires no explicit configuration, is to give the realms names within a shared hierarchy. For an example, assume realms named A.EXAMPLE.COM, B.EXAMPLE.COM, and EXAMPLE.COM. When a client in the A.EXAMPLE.COM realm attempts to authenticate to a service in B.EXAMPLE.COM, it will, by default, first attempt to get credentials for the EXAMPLE.COM realm, and then to use those credentials to obtain credentials for use in the B.EXAMPLE.COM realm.
The client in this scenario treats the realm name as one might treat a DNS name. It repeatedly strips off the components of its own realm's name to generate the names of realms which are "above" it in the hierarchy until it reaches a point which is also "above" the service's realm. At that point it begins prepending components of the service's realm name until it reaches the service's realm. Each realm which is involved in the process is another "hop".
For example, using credentials in A.EXAMPLE.COM, authenticating to a service in B.EXAMPLE.COMA.EXAMPLE.COM ??? EXAMPLE.COM ??? B.EXAMPLE.COM
A.EXAMPLE.COM and EXAMPLE.COM share a key for krbtgt/EXAMPLE.COM at A.EXAMPLE.COM
EXAMPLE.COM and B.EXAMPLE.COM share a key for krbtgt/B.EXAMPLE.COM at EXAMPLE.COM
Another example, using credentials in SITE1.SALES.EXAMPLE.COM, authenticating to a service in EVERYWHERE.EXAMPLE.COMSITE1.SALES.EXAMPLE.COM ??? SALES.EXAMPLE.COM ??? EXAMPLE.COM ??? EVERYWHERE.EXAMPLE.COM
SITE1.SALES.EXAMPLE.COM and SALES.EXAMPLE.COM share a key for krbtgt/SALES.EXAMPLE.COM at SITE1.SALES.EXAMPLE.COM
SALES.EXAMPLE.COM and EXAMPLE.COM share a key for krbtgt/EXAMPLE.COM at SALES.EXAMPLE.COM
EXAMPLE.COM and EVERYWHERE.EXAMPLE.COM share a key for krbtgt/EVERYWHERE.EXAMPLE.COM at EXAMPLE.COM
Another example, this time using realm names whose names share no common suffix (DEVEL.EXAMPLE.COM and PROD.EXAMPLE.ORG DEVEL.EXAMPLE.COM ??? EXAMPLE.COM ??? COM ??? ORG ??? EXAMPLE.ORG ??? PROD.EXAMPLE.ORG
DEVEL.EXAMPLE.COM and EXAMPLE.COM share a key for krbtgt/EXAMPLE.COM at DEVEL.EXAMPLE.COM
EXAMPLE.COM and COM share a key for krbtgt/COM at EXAMPLE.COM
COM and ORG share a key for krbtgt/ORG at COM
ORG and EXAMPLE.ORG share a key for krbtgt/EXAMPLE.ORG at ORG
EXAMPLE.ORG and PROD.EXAMPLE.ORG share a key for krbtgt/PROD.EXAMPLE.ORG at EXAMPLE.ORG
The more complicated, but also more flexible, method involves configuring the capaths section of /etc/krb5.conf, so that clients which have credentials for one realm will be able to look up which realm is next in the chain which will eventually lead to the being able to authenticate to servers.
The format of the capaths section is relatively straightforward: each entry in the section is named after a realm in which a client might exist. Inside of that subsection, the set of intermediate realms from which the client must obtain credentials is listed as values of the key which corresponds to the realm in which a service might reside. If there are no intermediate realms, the value "." is used.
In this example, clients in the A.EXAMPLE.COM realm can obtain cross-realm credentials for B.EXAMPLE.COM directly from the A.EXAMPLE.COM KDC.
If those clients wish to contact a service in theC.EXAMPLE.COM realm, they will first need to obtain necessary credentials from the B.EXAMPLE.COM realm (this requires that krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM exist), and then use those credentials to obtain credentials for use in the C.EXAMPLE.COM realm (using krbtgt/C.EXAMPLE.COM at B.EXAMPLE.COM).
If those clients wish to contact a service in the D.EXAMPLE.COM realm, they will first need to obtain necessary credentials from the B.EXAMPLE.COM realm, and then credentials from the C.EXAMPLE.COM realm, before finally obtaining credentials for use with the D.EXAMPLE.COM realm.
Note
Without a capath entry indicating otherwise, Kerberos assumes that cross-realm trust relationships form a hierarchy.
Clients in the A.EXAMPLE.COM realm can obtain cross-realm credentials from B.EXAMPLE.COM realm directly. Without the "." indicating this, the client would instead attempt to use a hierarchical path, in this case:
For a number of reasons, you may choose to run multiple KDCs for a given realm. In this scenario, one KDC (the master KDC) keeps a writable copy of the realm database and runs kadmind (it is also your realm's admin server), and one or more KDCs (slave KDCs) keep read-only copies of the database and run kpropd.
The master-slave propagation procedure entails the master KDC dumping its database to a temporary dump file and then transmitting that file to each of its slaves, which then overwrite their previously-received read-only copies of the database with the contents of the dump file.
To set up a slave KDC, first ensure that the master KDC's krb5.conf and kdc.conf files are copied to the slave KDC.
Start kadmin.local from a root shell on the master KDC and use its add_principal command to create a new entry for the master KDC's host service, and then use its ktadd command to simultaneously set a random key for the service and store the random key in the master's default keytab file. This key will be used by the kprop command to authenticate to the slave servers. You will only need to do this once, regardless of how many slave servers you install.
#??kadmin.local??-r??EXAMPLE.COM??Authenticating??as??principal??root/admin at EXAMPLE.COM??with??password.??kadmin:??add_principal??-randkey??host/masterkdc.example.com??Principal??"host/host/masterkdc.example.com at EXAMPLE.COM"??created.??kadmin:??ktadd??host/masterkdc.example.com??Entry??for??principal??host/masterkdc.example.com??with??kvno??3,??encryption??type??Triple??DES??cbc??mode??with??\??HMAC/sha1??added??to??keytab??WRFILE:/etc/krb5.keytab.??Entry??for??principal??host/masterkdc.example.com??with??kvno??3,??encryption??type??ArcFour??with??HMAC/md5??\??added??to??keytab??WRFILE:/etc/krb5.keytab.??Entry??for??principal??host/masterkdc.example.com??with??kvno??3,??encryption??ty
pe??DES??with??HMAC/sha1??added??\??to??keytab??WRFILE:/etc/krb5.keytab.??Entry??for??principal??host/masterkdc.example.com??with??kvno??3,??encryption??type??DES??cbc??mode??with??RSA-MD5??\??added??to??keytab??WRFILE:/etc/krb5.keytab.??kadmin:??quit
Start kadmin from a root shell on the slave KDC and use its add_principal command to create a new entry for the slave KDC's host service, and then use kadmin's ktadd command to simultaneously set a random key for the service and store the random key in the slave's default keytab file. This key is used by the kpropd service when authenticating clients.
#??kadmin??-p??jimbo/admin at EXAMPLE.COM??-r??EXAMPLE.COM??Authenticating??as??principal??jimbo/admin at EXAMPLE.COM??with??password.??Password??for??jimbo/admin at EXAMPLE.COM:??kadmin:??add_principal??-randkey??host/slavekdc.example.com??Principal??"host/slavekdc.example.com at EXAMPLE.COM"??created.??kadmin:??ktadd??host/slavekdc.example.com at EXAMPLE.COM??Entry??for??principal??host/slavekdc.example.com??with??kvno??3,??encryption??type??Triple??DES??cbc??mode??with??\??HMAC/sha1??added??to??keytab??WRFILE:/etc/krb5.keytab.??Entry??for??principal??host/slavekdc.example.com??with??kvno??3,??encryption??type??ArcFour??with??HMAC/md5??added??\??to??keytab??WRFILE:/etc/
krb5.keytab.??Entry??for??principal??host/slavekdc.example.com??with??kvno??3,??encryption??type??DES??with??HMAC/sha1??added??\??to??keytab??WRFILE:/etc/krb5.keytab.??Entry??for??principal??host/slavekdc.example.com??with??kvno??3,??encryption??type??DES??cbc??mode??with??RSA-MD5??added??\??to??keytab??WRFILE:/etc/krb5.keytab.??kadmin:??quit
With its service key, the slave KDC could authenticate any client which would connect to it. Obviously, not all of them should be allowed to provide the slave's kprop service with a new realm database. To restrict access, the kprop service on the slave KDC will only accept updates from clients whose principal names are listed in /var/kerberos/krb5kdc/kpropd.acl. Add the master KDC's host service's name to that file.
#??echo??host/masterkdc.example.com at EXAMPLE.COM??>??/var/kerberos/krb5kdc/kpropd.acl
Once the slave KDC has obtained a copy of the database, it will also need the master key which was used to encrypt it. If your KDC database's master key is stored in a stash file on the master KDC (typically named /var/kerberos/krb5kdc/.k5.REALM, either copy it to the slave KDC using any available secure method, or create a dummy database and identical stash file on the slave KDC by running kdb5_util create -s (the dummy database will be overwritten by the first successful database propagation) and supplying the same password.
Ensure that the slave KDC's firewall allows the master KDC to contact it using TCP on port 754 (krb5_prop), and start the kprop service. Then, double-check that the kadmin service is disabled.
Now perform a manual database propagation test by dumping the realm database, on the master KDC, to the default data file which the kprop command will read (/var/kerberos/krb5kdc/slave_datatrans), and then use the kprop command to transmit its contents to the slave KDC.
Using kinit, verify that a client system whose krb5.conf lists only the slave KDC in its list of KDCs for your realm is now correctly able to obtain initial credentials from the slave KDC.
That done, simply create a script which dumps the realm database and runs the kprop command to transmit the database to each slave KDC in turn, and configure the cron service to run the script periodically.
System security and integrity within a network can be unwieldy. It can occupy the time of several administrators just to keep track of what services are being run on a network and the manner in which these services are used.
Further, authenticating users to network services can prove dangerous when the method used by the protocol is inherently insecure, as evidenced by the transfer of unencrypted passwords over a network using the traditional FTP and Telnet protocols.
Kerberos is a way to eliminate the need for protocols that allow unsafe methods of authentication, thereby enhancing overall network security.
2.6.1.??What is Kerberos?
Kerberos is a network authentication protocol created by MIT, and uses symmetric-key cryptography[8] to authenticate users to network services, which means passwords are never actually sent over the network.
Consequently, when users authenticate to network services using Kerberos, unauthorized users attempting to gather passwords by monitoring network traffic are effectively thwarted.
2.6.1.1.??Advantages of Kerberos
Most conventional network services use password-based authentication schemes. Such schemes require a user to authenticate to a given network server by supplying their username and password. Unfortunately, the transmission of authentication information for many services is unencrypted. For such a scheme to be secure, the network has to be inaccessible to outsiders, and all computers and users on the network must be trusted and trustworthy.
Even if this is the case, a network that is connected to the Internet can no longer be assumed to be secure. Any attacker who gains access to the network can use a simple packet analyzer, also known as a packet sniffer, to intercept usernames and passwords, compromising user accounts and the integrity of the entire security infrastructure.
The primary design goal of Kerberos is to eliminate the transmission of unencrypted passwords across the network. If used properly, Kerberos effectively eliminates the threat that packet sniffers would otherwise pose on a network.
2.6.1.2.??Disadvantages of Kerberos
Although Kerberos removes a common and severe security threat, it may be difficult to implement for a variety of reasons:
Migrating user passwords from a standard UNIX password database, such as /etc/passwd or /etc/shadow, to a Kerberos password database can be tedious, as there is no automated mechanism to perform this task. Refer to Question 2.23 in the online Kerberos FAQ:
Kerberos has only partial compatibility with the Pluggable Authentication Modules (PAM) system used by most Fedora servers. Refer to Section??2.6.4, ???Kerberos and PAM??? for more information about this issue.
Kerberos assumes that each user is trusted but is using an untrusted host on an untrusted network. Its primary goal is to prevent unencrypted passwords from being transmitted across that network. However, if anyone other than the proper user has access to the one host that issues tickets used for authentication ??? called the key distribution center (KDC) ??? the entire Kerberos authentication system is at risk.
For an application to use Kerberos, its source must be modified to make the appropriate calls into the Kerberos libraries. Applications modified in this way are considered to be Kerberos-aware, or kerberized. For some applications, this can be quite problematic due to the size of the application or its design. For other incompatible applications, changes must be made to the way in which the server and client communicate. Again, this may require extensive programming. Closed-source applications that do not have Kerberos support by default are often the most problematic.
Kerberos is an all-or-nothing solution. If Kerberos is used on the network, any unencrypted passwords transferred to a non-Kerberos aware service is at risk. Thus, the network gains no benefit from the use of Kerberos. To secure a network with Kerberos, one must either use Kerberos-aware versions of all client/server applications that transmit passwords unencrypted, or not use any such client/server applications at all.
[8]
A system where both the client and the server share a common key that is used to encrypt and decrypt network communication.
--- NEW FILE sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html ---
3.7.4.??What you have just accomplished.
Following this procedure will remove all data on the partition that you are encrypting. You WILL lose all your information! Make sure you backup your data to an external source before beginning this procedure!
If you are running a version of Fedora prior to Fedora 9 and want to encrypt a partition, or you want to encrypt a partition after the installation of the current version of Fedora, the following directions are for you. The below example demonstrates encrypting your /home partition but any partition can be used.
The following procedure will wipe all your existing data, so be sure to have a tested backup before you start. This also requires you to have a separate partition for /home (in my case that is /dev/VG00/LV_home). All the following must be done as root. Any of these steps failing means you must not continue until the step succeeded.
Linux Unified Key Setup-on-disk-format (or LUKS) allows you to encrypt partitions on your Linux computer. This is particularly important when it comes to mobile computers and removable media. LUKS allows multiple user keys to decrypt a master key which is used for the bulk encryption of the partition.
3.7.1.??LUKS Implementation in Fedora
Fedora 9, and later, utilizes LUKS to perform file system encryption. By default, the option to encrypt the file system is unchecked during the installation. If you select the option to encrypt you hard drive, you will be prompted for a passphrase that will be asked every time you boot the computer. This passphrase "unlocks" the bulk encryption key that is used to decrypt your partition. If you choose to modify the default partition table you can choose which partitions you want to encrypt. This is set in the partition table settings
Fedora 9's default implementation of LUKS is AES 128 with a SHA256 hashing. Ciphers that are available are:
By allowing access control on a per-rule basis, the option field allows administrators to consolidate all access rules into a single file: either hosts.allow or hosts.deny. Some administrators consider this an easier way of organizing access rules.
Expansions, when used in conjunction with the spawn and twist directives, provide information about the client, server, and processes involved.
The following is a list of supported expansions:
%a ??? Returns the client's IP address.
%A ??? Returns the server's IP address.
%c ??? Returns a variety of client information, such as the username and hostname, or the username and IP address.
%d ??? Returns the daemon process name.
%h ??? Returns the client's hostname (or IP address, if the hostname is unavailable).
%H ??? Returns the server's hostname (or IP address, if the hostname is unavailable).
%n ??? Returns the client's hostname. If unavailable, unknown is printed. If the client's hostname and host address do not match, paranoid is printed.
%N ??? Returns the server's hostname. If unavailable, unknown is printed. If the server's hostname and host address do not match, paranoid is printed.
%p ??? Returns the daemon's process ID.
%s ???Returns various types of server information, such as the daemon process and the host or IP address of the server.
%u ??? Returns the client's username. If unavailable, unknown is printed.
The following sample rule uses an expansion in conjunction with the spawn command to identify the client host in a customized log file.
When connections to the SSH daemon (sshd) are attempted from a host in the example.com domain, execute the echo command to log the attempt, including the client hostname (by using the %h expansion), to a special file:
Similarly, expansions can be used to personalize messages back to the client. In the following example, clients attempting to access FTP services from the example.com domain are informed that they have been banned from the server:
vsftpd : .example.com \
: twist /bin/echo "421 %h has been banned from this server!"
For a full explanation of available expansions, as well as additional access control options, refer to section 5 of the man pages for hosts_access (man 5 hosts_access) and the man page for hosts_options.
Option fields allow access rules to launch shell commands through the following two directives:
spawn ??? Launches a shell command as a child process. This directive can perform tasks like using /usr/sbin/safe_finger to get more information about the requesting client or create special log files using the echo command.
In the following example, clients attempting to access Telnet services from the example.com domain are quietly logged to a special file:
twist ??? Replaces the requested service with the specified command. This directive is often used to set up traps for intruders (also called "honey pots"). It can also be used to send messages to connecting clients. The twist directive must occur at the end of the rule line.
In the following example, clients attempting to access FTP services from the example.com domain are sent a message using the echo command:
vsftpd : .example.com \
: twist /bin/echo "421 This domain has been black-listed. Access denied!"
For more information about shell command options, refer to the hosts_options man page.
All PAM modules generate a success or failure result when called. Control flags tell PAM what do with the result. Modules can be stacked in a particular order, and the control flags determine how important the success or failure of a particular module is to the overall goal of authenticating the user to the service.
There are four predefined control flags:
required ??? The module result must be successful for authentication to continue. If the test fails at this point, the user is not notified until the results of all module tests that reference that interface are complete.
requisite ??? The module result must be successful for authentication to continue. However, if a test fails at this point, the user is notified immediately with a message reflecting the first failed requiredorrequisite module test.
sufficient ??? The module result is ignored if it fails. However, if the result of a module flagged sufficient is successful and no previous modules flagged required have failed, then no other results are required and the user is authenticated to the service.
optional ??? The module result is ignored. A module flagged as optional only becomes necessary for successful authentication when no other modules reference the interface.
Important
The order in which required modules are called is not critical. Only the sufficient and requisite control flags cause order to become important.
A newer control flag syntax that allows for more precise control is now available for PAM.
The pam.d man page, and the PAM documentation, located in the /usr/share/doc/pam-<version-number>/ directory, where <version-number> is the version number for PAM on your system, describe this newer syntax in detail.
PAM uses arguments to pass information to a pluggable module during authentication for some modules.
For example, the pam_userdb.so module uses information stored in a Berkeley DB file to authenticate the user. Berkeley DB is an open source database system embedded in many applications. The module takes a db argument so that Berkeley DB knows which database to use for the requested service.
The following is a typical pam_userdb.so line in a PAM configuration. The <path-to-file> is the full path to the Berkeley DB database file:
auth required pam_userdb.so db=<path-to-file>
Invalid arguments are generally ignored and do not otherwise affect the success or failure of the PAM module. Some modules, however, may fail on invalid arguments. Most modules report errors to the /var/log/secure file.
The module name provides PAM with the name of the pluggable module containing the specified module interface. In older versions of Fedora, the full path to the module was provided in the PAM configuration file. However, since the advent of multilib systems, which store 64-bit PAM modules in the /lib64/security/ directory, the directory name is omitted because the application is linked to the appropriate version of libpam, which can locate the correct version of the module.
The following resources further explain methods to use and configure PAM. In addition to these resources, read the PAM configuration files on the system to better understand how they are structured.
2.4.8.1.??Installed PAM Documentation
PAM-related man pages ??? Several man pages exist for the various applications and configuration files involved with PAM. The following is a list of some of the more important man pages.
Configuration Files
pam ??? Good introductory information on PAM, including the structure and purpose of the PAM configuration files.
Note that this man page discusses both /etc/pam.conf and individual configuration files in the /etc/pam.d/ directory. By default, Fedora uses the individual configuration files in the /etc/pam.d/ directory, ignoring /etc/pam.conf even if it exists.
pam_console ??? Describes the purpose of the pam_console.so module. It also describes the appropriate syntax for an entry within a PAM configuration file.
console.apps ??? Describes the format and options available in the /etc/security/console.apps configuration file, which defines which applications are accessible by the console user assigned by PAM.
console.perms ??? Describes the format and options available in the /etc/security/console.perms configuration file, which specifies the console user permissions assigned by PAM.
pam_timestamp ??? Describes the pam_timestamp.so module.
/usr/share/doc/pam-<version-number> ??? Contains a System Administrators' Guide, a Module Writers' Manual, and the Application Developers' Manual, as well as a copy of the PAM standard, DCE-RFC 86.0, where <version-number> is the version number of PAM.
/usr/share/doc/pam-<version-number>/txts/README.pam_timestamp ??? Contains information about the pam_timestamp.so PAM module, where <version-number> is the version number of PAM.
You can create or add new PAM modules at any time for use by PAM-aware applications.
For example, a developer might create a one-time-password creation method and write a PAM module to support it. PAM-aware programs can immediately use the new module and password method without being recompiled or otherwise modified.
This allows developers and system administrators to mix-and-match, as well as test, authentication methods for different programs without recompiling them.
Documentation on writing modules is included in the /usr/share/doc/pam-<version-number>/ directory, where <version-number> is the version number for PAM on your system.
Each of these elements is explained in the following sections.
2.4.3.1.??Module Interface
Four types of PAM module interface are currently available. Each of these corresponds to a different aspect of the authorization process:
auth ??? This module interface authenticates use. For example, it requests and verifies the validity of a password. Modules with this interface can also set credentials, such as group memberships or Kerberos tickets.
account ??? This module interface verifies that access is allowed. For example, it may check if a user account has expired or if a user is allowed to log in at a particular time of day.
password ??? This module interface is used for changing user passwords.
session ??? This module interface configures and manages user sessions. Modules with this interface can also perform additional tasks that are needed to allow access, like mounting a user's home directory and making the user's mailbox available.
Note
An individual module can provide any or all module interfaces. For instance, pam_unix.so provides all four module interfaces.
In a PAM configuration file, the module interface is the first field defined. For example, a typical line in a configuration may look like this:
auth required pam_unix.so
This instructs PAM to use the pam_unix.so module's auth interface.
2.4.3.1.1.??Stacking Module Interfaces
Module interface directives can be stacked, or placed upon one another, so that multiple modules are used together for one purpose. If a module's control flag uses the "sufficient" or "requisite" value (refer to Section??2.4.3.2, ???Control Flag??? for more information on these flags), then the order in which the modules are listed is important to the authentication process.
Stacking makes it easy for an administrator to require specific conditions to exist before allowing the user to authenticate. For example, the reboot command normally uses several stacked modules, as seen in its PAM configuration file:
[root at MyServer ~]# cat /etc/pam.d/reboot
#%PAM-1.0
auth sufficient pam_rootok.so
auth required pam_console.so
#auth include system-auth
account required pam_permit.so
The first line is a comment and is not processed.
auth sufficient pam_rootok.so ??? This line uses the pam_rootok.so module to check whether the current user is root, by verifying that their UID is 0. If this test succeeds, no other modules are consulted and the command is executed. If this test fails, the next module is consulted.
auth required pam_console.so ??? This line uses the pam_console.so module to attempt to authenticate the user. If this user is already logged in at the console, pam_console.so checks whether there is a file in the /etc/security/console.apps/ directory with the same name as the service name (reboot). If such a file exists, authentication succeeds and control is passed to the next module.
#auth include system-auth ??? This line is commented and is not processed.
account required pam_permit.so ??? This line uses the pam_permit.so module to allow the root user or anyone logged in at the console to reboot the system.
The /etc/pam.d/ directory contains the PAM configuration files for each PAM-aware application. In earlier versions of PAM, the /etc/pam.conf file was used, but this file is now deprecated and is only used if the /etc/pam.d/ directory does not exist.
2.4.2.1.??PAM Service Files
Each PAM-aware application or service has a file in the /etc/pam.d/ directory. Each file in this directory has the same name as the service to which it controls access.
The PAM-aware program is responsible for defining its service name and installing its own PAM configuration file in the /etc/pam.d/ directory. For example, the login program defines its service name as login and installs the /etc/pam.d/login PAM configuration file.
--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html ---
2.4.6.??PAM and Administrative Credential Caching
A number of graphical administrative tools in Fedora provide users with elevated privileges for up to five minutes using the pam_timestamp.so module. It is important to understand how this mechanism works, because a user who walks away from a terminal while pam_timestamp.so is in effect leaves the machine open to manipulation by anyone with physical access to the console.
In the PAM timestamp scheme, the graphical administrative application prompts the user for the root password when it is launched. When the user has been authenticated, the pam_timestamp.so module creates a timestamp file. By default, this is created in the /var/run/sudo/ directory. If the timestamp file already exists, graphical administrative programs do not prompt for a password. Instead, the pam_timestamp.so module freshens the timestamp file, reserving an extra five minutes of unchallenged administrative access for the user.
You can verify the actual state of the timestamp file by inspecting the /var/run/sudo/<user> file. For the desktop, the relevant file is unknown:root. If it is present and its timestamp is less than five minutes old, the credentials are valid.
The existence of the timestamp file is indicated by an authentication icon, which appears in the notification area of the panel.
Illustration of the authentication icon.
Figure??2.7.??The Authentication Icon
2.4.6.1.??Removing the Timestamp File
Before abandoning a console where a PAM timestamp is active, it is recommended that the timestamp file be destroyed. To do this from a graphical environment, click the authentication icon on the panel. This causes a dialog box to appear. Click the Forget Authorization button to destroy the active timestamp file.
Illustration of the authentication dismissal dialog box.
Figure??2.8.??Dismiss Authentication Dialog
You should be aware of the following with respect to the PAM timestamp file:
If logged in to the system remotely using ssh, use the /sbin/pam_timestamp_check -k root command to destroy the timestamp file.
You need to run the /sbin/pam_timestamp_check -k root command from the same terminal window from which you launched the privileged application.
You must be logged in as the user who originally invoked the pam_timestamp.so module in order to use the /sbin/pam_timestamp_check -k command. Do not log in as root to use this command.
If you want to kill the credentials on the desktop (without using the Forget Authorization action on the icon), use the following command:
In Fedora, the first user who logs in at the physical console of the machine can manipulate certain devices and perform certain tasks normally reserved for the root user. This is controlled by a PAM module called pam_console.so.
2.4.7.1.??Device Ownership
When a user logs in to a Fedora system, the pam_console.so module is called by login or the graphical login programs, gdm, kdm, and xdm. If this user is the first user to log in at the physical console ??? referred to as the console user ??? the module grants the user ownership of a variety of devices normally owned by root. The console user owns these devices until the last local session for that user ends. After this user has logged out, ownership of the devices reverts back to the root user.
The devices affected include, but are not limited to, sound cards, diskette drives, and CD-ROM drives.
This facility allows a local user to manipulate these devices without obtaining root access, thus simplifying common tasks for the console user.
You can modify the list of devices controlled by pam_console.so by editing the following files:
/etc/security/console.perms
/etc/security/console.perms.d/50-default.perms
You can change the permissions of different devices than those listed in the above files, or override the specified defaults. Rather than modify the 50-default.perms file, you should create a new file (for example, xx-name.perms) and enter the required modifications. The name of the new default file must begin with a number higher than 50 (for example, 51-default.perms). This will override the defaults in the 50-default.perms file.
Warning
If the gdm, kdm, or xdm display manager configuration file has been altered to allow remote users to log in and the host is configured to run at runlevel 5, it is advisable to change the <console> and <xconsole> directives in the /etc/security/console.perms to the following values:
This prevents remote users from gaining access to devices and restricted applications on the machine.
If the gdm, kdm, or xdm display manager configuration file has been altered to allow remote users to log in and the host is configured to run at any multiple user runlevel other than 5, it is advisable to remove the <xconsole> directive entirely and change the <console> directive to the following value:
The first line is a comment, indicated by the hash mark (#) at the beginning of the line.
Lines two through four stack three modules for login authentication.
auth required pam_securetty.so ??? This module ensures that if the user is trying to log in as root, the tty on which the user is logging in is listed in the /etc/securetty file, if that file exists.
If the tty is not listed in the file, any attempt to log in as root fails with a Login incorrect message.
auth required pam_unix.so nullok ??? This module prompts the user for a password and then checks the password using the information stored in /etc/passwd and, if it exists, /etc/shadow.
The argument nullok instructs the pam_unix.so module to allow a blank password.
auth required pam_nologin.so ??? This is the final authentication step. It checks whether the /etc/nologin file exists. If it exists and the user is not root, authentication fails.
Note
In this example, all three auth modules are checked, even if the first auth module fails. This prevents the user from knowing at what stage their authentication failed. Such knowledge in the hands of an attacker could allow them to more easily deduce how to crack the system.
account required pam_unix.so ??? This module performs any necessary account verification. For example, if shadow passwords have been enabled, the account interface of the pam_unix.so module checks to see if the account has expired or if the user has not changed the password within the allowed grace period.
password required pam_cracklib.so retry=3 ??? If a password has expired, the password component of the pam_cracklib.so module prompts for a new password. It then tests the newly created password to see whether it can easily be determined by a dictionary-based password cracking program.
The argument retry=3 specifies that if the test fails the first time, the user has two more chances to create a strong password.
password required pam_unix.so shadow nullok use_authtok ??? This line specifies that if the program changes the user's password, it should use the password interface of the pam_unix.so module to do so.
The argument shadow instructs the module to create shadow passwords when updating a user's password.
The argument nullok instructs the module to allow the user to change their password from a blank password, otherwise a null password is treated as an account lock.
The final argument on this line, use_authtok, provides a good example of the importance of order when stacking PAM modules. This argument instructs the module not to prompt the user for a new password. Instead, it accepts any password that was recorded by a previous password module. In this way, all new passwords must pass the pam_cracklib.so test for secure passwords before being accepted.
session required pam_unix.so ??? The final line instructs the session interface of the pam_unix.so module to manage the session. This module logs the user name and the service type to /var/log/secure at the beginning and end of each session. This module can be supplemented by stacking it with other session modules for additional functionality.
Programs that grant users access to a system use authentication to verify each other's identity (that is, to establish that a user is who they say they are).
Historically, each program had its own way of authenticating users. In Fedora, many programs are configured to use a centralized authentication mechanism called Pluggable Authentication Modules (PAM).
PAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in setting authentication policies for the system.
In most situations, the default PAM configuration file for a PAM-aware application is sufficient. Sometimes, however, it is necessary to edit a PAM configuration file. Because misconfiguration of PAM can compromise system security, it is important to understand the structure of these files before making any modifications. Refer to Section??2.4.3, ???PAM Configuration File Format??? for more information.
2.4.1.??Advantages of PAM
PAM offers the following advantages:
a common authentication scheme that can be used with a wide variety of applications.
significant flexibility and control over authentication for both system administrators and application developers.
a single, fully-documented library which allows developers to write programs without having to create their own authentication schemes.
Since Fedora 9, implementation of Linux Unified Key Setup-on-disk-format(LUKS) encryption has become a lot easier. During the installation process an option to encrypt your partitions will be presented to the user. The user must supply a passphrase that will be the key to unlock the bulk encryption key that will be used to secure the partition's data.
Fedora 8, however, does not have LUKS support built-in; however it is easily implemented. Step-by-step procedures are available that allow the user to implement partition encryption on their Fedora 8 installation.
The presence of the /var/ftp/ directory activates the anonymous account.
The easiest way to create this directory is to install the vsftpd package. This package establishes a directory tree for anonymous users and configures the permissions on directories to read-only for anonymous users.
By default the anonymous user cannot write to any directories.
Caution
If enabling anonymous access to an FTP server, be aware of where sensitive data is stored.
2.2.6.2.1.??Anonymous Upload
To allow anonymous users to upload files, it is recommended that a write-only directory be created within /var/ftp/pub/.
To do this, type the following command:
mkdir /var/ftp/pub/upload
Next, change the permissions so that anonymous users cannot view the contents of the directory:
chmod 730 /var/ftp/pub/upload
A long format listing of the directory should look like this:
drwx-wx--- 2 root ftp 4096 Feb 13 20:05 upload
Warning
Administrators who allow anonymous users to read and write in directories often find that their servers become a repository of stolen software.
Additionally, under vsftpd, add the following line to the /etc/vsftpd/vsftpd.conf file:
Because FTP transmits unencrypted usernames and passwords over insecure networks for authentication, it is a good idea to deny system users access to the server from their user accounts.
To disable all user accounts in vsftpd, add the following directive to /etc/vsftpd/vsftpd.conf:
local_enable=NO
2.2.6.3.1.??Restricting User Accounts
To disable FTP access for specific accounts or specific groups of accounts, such as the root user and those with sudo privileges, the easiest way is to use a PAM list file as described in Section??2.1.4.2.4, ???Disabling Root Using PAM???. The PAM configuration file for vsftpd is /etc/pam.d/vsftpd.
It is also possible to disable user accounts within each service directly.
To disable specific user accounts in vsftpd, add the username to /etc/vsftpd.ftpusers
The NFS server determines which file systems to export and which hosts to export these directories to by consulting the /etc/exports file. Be careful not to add extraneous spaces when editing this file.
For instance, the following line in the /etc/exports file shares the directory /tmp/nfs/ to the host bob.example.com with read/write permissions.
/tmp/nfs/ bob.example.com(rw)
The following line in the /etc/exports file, on the other hand, shares the same directory to the host bob.example.com with read-only permissions and shares it to the world with read/write permissions due to a single space character after the hostname.
/tmp/nfs/ bob.example.com (rw)
It is good practice to check any configured NFS shares by using the showmount command to verify what is being shared:
By default, NFS shares change the root user to the nfsnobody user, an unprivileged user account. This changes the owner of all root-created files to nfsnobody, which prevents uploading of programs with the setuid bit set.
If no_root_squash is used, remote root users are able to change any file on the shared file system and leave applications infected by trojans for other users to inadvertently execute.
2.2.3.4.??Assign Static Ports and Use iptables Rules
All of the servers related to NIS can be assigned specific ports except for rpc.yppasswdd ??? the daemon that allows users to change their login passwords. Assigning ports to the other two NIS server daemons, rpc.ypxfrd and ypserv, allows for the creation of firewall rules to further protect the NIS server daemons from intruders.
To do this, add the following lines to /etc/sysconfig/network:
YPSERV_ARGS="-p 834" YPXFRD_ARGS="-p 835"
The following iptables rules can then be used to enforce which network the server listens to for these ports:
iptables -A INPUT -p ALL -s! 192.168.0.0/24 --dport 834 -j DROP
iptables -A INPUT -p ALL -s! 192.168.0.0/24 --dport 835 -j DROP
This means that the server only allows connections to ports 834 and 835 if the requests come from the 192.168.0.0/24 network, regardless of the protocol.
If the /var/yp/securenets file is blank or does not exist (as is the case after a default installation), NIS listens to all networks. One of the first things to do is to put netmask/network pairs in the file so that ypserv only responds to requests from the appropriate network.
Below is a sample entry from a /var/yp/securenets file:
255.255.255.0 192.168.0.0
Warning
Never start an NIS server for the first time without creating the /var/yp/securenets file.
This technique does not provide protection from an IP spoofing attack, but it does at least place limits on what networks the NIS server services.
One of the issues to consider when NIS is used for authentication is that whenever a user logs into a machine, a password hash from the /etc/shadow map is sent over the network. If an intruder gains access to an NIS domain and sniffs network traffic, they can collect usernames and password hashes. With enough time, a password cracking program can guess weak passwords, and an attacker can gain access to a valid account on the network.
Since Kerberos uses secret-key cryptography, no password hashes are ever sent over the network, making the system far more secure. Refer to Section??2.6, ???Kerberos??? for more information about Kerberos.
--- NEW FILE sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html ---
2.2.3.2.??Use a Password-like NIS Domain Name and Hostname
2.2.3.2.??Use a Password-like NIS Domain Name and Hostname
Any machine within an NIS domain can use commands to extract information from the server without authentication, as long as the user knows the NIS server's DNS hostname and NIS domain name.
For instance, if someone either connects a laptop computer into the network or breaks into the network from outside (and manages to spoof an internal IP address), the following command reveals the /etc/passwd map:
ypcat -d <NIS_domain> -h <DNS_hostname> passwd
If this attacker is a root user, they can obtain the /etc/shadow file by typing the following command:
ypcat -d <NIS_domain> -h <DNS_hostname> shadow
Note
If Kerberos is used, the /etc/shadow file is not stored within an NIS map.
To make access to NIS maps harder for an attacker, create a random string for the DNS hostname, such as o7hfawtgmhwg.domain.com. Similarly, create a different randomized NIS domain name. This makes it much more difficult for an attacker to access the NIS server.
To further restrict access to the portmap service, it is a good idea to add iptables rules to the server and restrict access to specific networks.
Below are two example iptables commands. The first allows TCP connections to the port 111 (used by the portmap service) from the 192.168.0.0/24 network. The second allows TCP connections to the same port from the localhost. This is necessary for the sgi_fam service used by Nautilus. All other packets are dropped.
iptables -A INPUT -p tcp -s! 192.168.0.0/24 --dport 111 -j DROP
iptables -A INPUT -p tcp -s 127.0.0.1 --dport 111 -j ACCEPT
To similarly limit UDP traffic, use the following command.
iptables -A INPUT -p udp -s! 192.168.0.0/24 --dport 111 -j DROP
To help prevent local user exploits on the Sendmail server, it is best for mail users to only access the Sendmail server using an email program. Shell accounts on the mail server should not be allowed and all user shells in the /etc/passwd file should be set to /sbin/nologin (with the possible exception of the root user).
Never put the mail spool directory, /var/spool/mail/, on an NFS shared volume.
Because NFSv2 and NFSv3 do not maintain control over user and group IDs, two or more users can have the same UID, and receive and read each other's mail.
Note
With NFSv4 using Kerberos, this is not the case, since the SECRPC_GSS kernel module does not utilize UID-based authentication. However, it is considered good practice not to put the mail spool directory on NFS shared volumes.
--- NEW FILE sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.html ---
2.2.5.4.??Do Not Remove the IncludesNoExec Directive
2.2.5.4.??Do Not Remove the IncludesNoExec Directive
By default, the Server-Side Includes (SSI) module cannot execute commands. It is recommended that you do not change this setting unless absolutely necessary, as it could potentially enable an attacker to execute commands on the system.
--- NEW FILE sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.html ---
2.2.5.5.??Restrict Permissions for Executable Directories
The UserDir directive is disabled by default because it can confirm the presence of a user account on the system. To enable user directory browsing on the server, use the following directives:
UserDir enabled
UserDir disabled root
These directives activate user directory browsing for all user directories other than /root/. To add users to the list of disabled accounts, add a space-delimited list of users on the UserDir disabled line.
As security vulnerabilities are discovered, the affected software must be updated in order to limit any potential security risks. If the software is part of a package within a Fedora distribution that is currently supported, Fedora. is committed to releasing updated packages that fix the vulnerability as soon as possible. Often, announcements about a given security exploit are accompanied with a patch (or source code that fixes the problem). This patch is then applied to the Fedora package, tested by the Red Hat quality assurance team, and released as an errata update. However, if an announcement does not include a patch, a Red Hat developer works with the maintainer of the software to fix the problem. Once the problem is fixed, the package is tested and released as an errata update.
If an errata update is released for software used on your system, it is highly recommended that you update the effected packages as soon as possible to minimize the amount of time the system is potentially vulnerable.
1.5.1.??Updating Packages
When updating software on a system, it is important to download the update from a trusted source. An attacker can easily rebuild a package with the same version number as the one that is supposed to fix the problem but with a different security exploit and release it on the Internet. If this happens, using security measures such as verifying files against the original RPM does not detect the exploit. Thus, it is very important to only download RPMs from trusted sources, such as from Fedora. and check the signature of the package to verify its integrity.
Red Hat offers two ways to find information on errata updates:
Listed and available for download on Red Hat Network
Listed and unlinked on the Red Hat Errata website
Note
Beginning with the Fedora product line, updated packages can be downloaded only from Red Hat Network. Although the Red Hat Errata website contains updated information, it does not contain the actual packages for download.
1.5.1.1.??Using Red Hat Network
Red Hat Network allows the majority of the update process to be automated. It determines which RPM packages are necessary for the system, downloads them from a secure repository, verifies the RPM signature to make sure they have not been tampered with, and updates them. The package install can occur immediately or can be scheduled during a certain time period.
Red Hat Network requires a System Profile for each machine to be updated. The System Profile contains hardware and software information about the system. This information is kept confidential and is not given to anyone else. It is only used to determine which errata updates are applicable to each system, and, without it, Red Hat Network can not determine whether a given system needs updates. When a security errata (or any type of errata) is released, Red Hat Network sends an email with a description of the errata as well as a list of systems which are affected. To apply the update, use the Red Hat Update Agent or schedule the package to be updated through the website http://rhn.redhat.com.
Tip
Fedora includes the Red Hat Network Alert Notification Tool, a convenient panel icon that displays visible alerts when there is an update for a registered Fedora system. Refer to the following URL for more information about the applet: https://rhn.redhat.com/rhn/help/quickstart.jsp
Important
Before installing any security errata, be sure to read any special instructions contained in the errata report and execute them accordingly. Refer to Section??1.5.1.5, ???Applying the Changes??? for general instructions about applying the changes made by an errata update.
1.5.1.2.??Using the Red Hat Errata Website
When security errata reports are released, they are published on the Red Hat Errata website available at http://www.redhat.com/security/. From this page, select the product and version for your system, and then select security at the top of the page to display only Fedora Security Advisories. If the synopsis of one of the advisories describes a package used on your system, click on the synopsis for more details.
The details page describes the security exploit and any special instructions that must be performed in addition to updating the package to fix the security hole.
To download the updated package(s), click on the link to login to Red Hat Network, click the package name(s) and save to the hard drive. It is highly recommended that you create a new directory, such as /tmp/updates, and save all the downloaded packages to it.
1.5.1.3.??Verifying Signed Packages
All Fedora packages are signed with the Fedora. GPG key. GPG stands for GNU Privacy Guard, or GnuPG, a free software package used for ensuring the authenticity of distributed files. For example, a private key (secret key) held by Red Hat locks the package while the public key unlocks and verifies the package. If the public key distributed by Red Hat does not match the private key during RPM verification, the package may have been altered and therefore cannot be trusted.
The RPM utility within Fedora automatically tries to verify the GPG signature of an RPM package before installing it. If the Red Hat GPG key is not installed, install it from a secure, static location, such as an Fedora installation CD-ROM.
Assuming the CD-ROM is mounted in /mnt/cdrom, use the following command to import it into the keyring (a database of trusted keys on the system):
rpm --import /mnt/cdrom/RPM-GPG-KEY
To display a list of all keys installed for RPM verification, execute the following command:
rpm -qa gpg-pubkey*
For the Red Hat key, the output includes the following:
gpg-pubkey-db42a60e-37ea5438
To display details about a specific key, use the rpm -qi command followed by the output from the previous command, as in this example:
rpm -qi gpg-pubkey-db42a60e-37ea5438
It is extremely important to verify the signature of the RPM files before installing them to ensure that they have not been altered from the Fedora. release of the packages. To verify all the downloaded packages at once, issue the following command:
rpm -K /tmp/updates/*.rpm
For each package, if the GPG key verifies successfully, the command returns gpg OK. If it doesn't, make sure you are using the correct Red Hat public key, as well as verifying the source of the content. Packages that do not pass GPG verifications should not be installed, as they may have been altered by a third party.
After verifying the GPG key and downloading all the packages associated with the errata report, install the packages as root at a shell prompt.
1.5.1.4.??Installing Signed Packages
Installation for most packages can be done safely (except kernel packages) by issuing the following command:
rpm -Uvh /tmp/updates/*.rpm
For kernel packages use the following command:
rpm -ivh /tmp/updates/<kernel-package>
Replace <kernel-package> in the previous example with the name of the kernel RPM.
Once the machine has been safely rebooted using the new kernel, the old kernel may be removed using the following command:
rpm -e <old-kernel-package>
Replace <old-kernel-package> in the previous example with the name of the older kernel RPM.
Note
It is not a requirement that the old kernel be removed. The default boot loader, GRUB, allows for multiple kernels to be installed, then chosen from a menu at boot time.
Important
Before installing any security errata, be sure to read any special instructions contained in the errata report and execute them accordingly. Refer to Section??1.5.1.5, ???Applying the Changes??? for general instructions about applying the changes made by an errata update.
1.5.1.5.??Applying the Changes
After downloading and installing security errata via Red Hat Network or the Red Hat errata website, it is important to halt usage of the older software and begin using the new software. How this is done depends on the type of software that has been updated. The following list itemizes the general categories of software and provides instructions for using the updated versions after a package upgrade.
Note
In general, rebooting the system is the surest way to ensure that the latest version of a software package is used; however, this option is not always available to the system administrator.
Applications
User-space applications are any programs that can be initiated by a system user. Typically, such applications are used only when a user, script, or automated task utility launches them and they do not persist for long periods of time.
Once such a user-space application is updated, halt any instances of the application on the system and launch the program again to use the updated version.
Kernel
The kernel is the core software component for the Fedora operating system. It manages access to memory, the processor, and peripherals as well as schedules all tasks.
Because of its central role, the kernel cannot be restarted without also stopping the computer. Therefore, an updated version of the kernel cannot be used until the system is rebooted.
Shared Libraries
Shared libraries are units of code, such as glibc, which are used by a number of applications and services. Applications utilizing a shared library typically load the shared code when the application is initialized, so any applications using the updated library must be halted and relaunched.
To determine which running applications link against a particular library, use the lsof command as in the following example:
lsof /usr/lib/libwrap.so*
This command returns a list of all the running programs which use TCP wrappers for host access control. Therefore, any program listed must be halted and relaunched if the tcp_wrappers package is updated.
SysV Services
SysV services are persistent server programs launched during the boot process. Examples of SysV services include sshd, vsftpd, and xinetd.
Because these programs usually persist in memory as long as the machine is booted, each updated SysV service must be halted and relaunched after the package is upgraded. This can be done using the Services Configuration Tool or by logging into a root shell prompt and issuing the /sbin/service command as in the following example:
/sbin/service <service-name> restart
In the previous example, replace <service-name> with the name of the service, such as sshd.
xinetd Services
Services controlled by the xinetd super service only run when a there is an active connection. Examples of services controlled by xinetd include Telnet, IMAP, and POP3.
Because new instances of these services are launched by xinetd each time a new request is received, connections that occur after an upgrade are handled by the updated software. However, if there are active connections at the time the xinetd controlled service is upgraded, they are serviced by the older version of the software.
To kill off older instances of a particular xinetd controlled service, upgrade the package for the service then halt all processes currently running. To determine if the process is running, use the ps command and then use the kill or killall command to halt current instances of the service.
For example, if security errata imap packages are released, upgrade the packages, then type the following command as root into a shell prompt:
ps -aux | grep imap
This command returns all active IMAP sessions. Individual sessions can then be terminated by issuing the following command:
kill <PID>
If this fails to terminate the session, use the following command instead:
kill -9 <PID>
In the previous examples, replace <PID> with the process identification number (found in the second column of the ps command) for an IMAP session.
To kill all active IMAP sessions, issue the following command:
The File Transport Protocol (FTP) is an older TCP protocol designed to transfer files over a network. Because all transactions with the server, including user authentication, are unencrypted, it is considered an insecure protocol and should be carefully configured.
Fedora provides three FTP servers.
gssftpd ??? A Kerberos-aware xinetd-based FTP daemon that does not transmit authentication information over the network.
Red Hat Content Accelerator (tux) ??? A kernel-space Web server with FTP capabilities.
vsftpd ??? A standalone, security oriented implementation of the FTP service.
The following security guidelines are for setting up the vsftpd FTP service.
2.2.6.1.??FTP Greeting Banner
Before submitting a username and password, all users are presented with a greeting banner. By default, this banner includes version information useful to crackers trying to identify weaknesses in a system.
To change the greeting banner for vsftpd, add the following directive to the /etc/vsftpd/vsftpd.conf file:
ftpd_banner=<insert_greeting_here>
Replace <insert_greeting_here> in the above directive with the text of the greeting message.
For mutli-line banners, it is best to use a banner file. To simplify management of multiple banners, place all banners in a new directory called /etc/banners/. The banner file for FTP connections in this example is /etc/banners/ftp.msg. Below is an example of what such a file may look like:
######### # Hello, all activity on ftp.example.com is logged. #########
The version of NFS included in Fedora, NFSv4, no longer requires the portmap service as outlined in Section??2.2.2, ???Securing Portmap???. NFS traffic now utilizes TCP in all versions, rather than UDP, and requires it when using NFSv4. NFSv4 now includes Kerberos user and group authentication, as part of the RPCSEC_GSS kernel module. Information on portmap is still included, since Fedora supports NFSv2 and NFSv3, both of which utilize portmap.
2.2.4.1.??Carefully Plan the Network
Now that NFSv4 has the ability to pass all information encrypted using Kerberos over a network, it is important that the service be configured correctly if it is behind a firewall or on a segmented network. NFSv2 and NFSv3 still pass data insecurely, and this should be taken into consideration. Careful network design in all of these regards can help prevent security breaches.
The Network Information Service (NIS) is an RPC service, called ypserv,--> which is used in conjunction with portmap and other related services to distribute maps of usernames, passwords, and other sensitive information to any computer claiming to be within its domain.
An NIS server is comprised of several applications. They include the following:
/usr/sbin/rpc.yppasswdd ??? Also called the yppasswdd service, this daemon allows users to change their NIS passwords.
/usr/sbin/rpc.ypxfrd ??? Also called the ypxfrd service, this daemon is responsible for NIS map transfers over the network.
/usr/sbin/yppush ??? This application propagates changed NIS databases to multiple NIS servers.
/usr/sbin/ypserv ??? This is the NIS server daemon.
NIS is somewhat insecure by today's standards. It has no host authentication mechanisms and transmits all of its information over the network unencrypted, including password hashes. As a result, extreme care must be taken when setting up a network that uses NIS. This is further complicated by the fact that the default configuration of NIS is inherently insecure.
It is recommended that anyone planning to implement an NIS server first secure the portmap service as outlined in Section??2.2.2, ???Securing Portmap???, then address the following issues, such as network planning.
2.2.3.1.??Carefully Plan the Network
Because NIS transmits sensitive information unencrypted over the network, it is important the service be run behind a firewall and on a segmented and secure network. Whenever NIS information is transmitted over an insecure network, it risks being intercepted. Careful network design can help prevent severe security breaches.
The portmap service is a dynamic port assignment daemon for RPC services such as NIS and NFS. It has weak authentication mechanisms and has the ability to assign a wide range of ports for the services it controls. For these reasons, it is difficult to secure.
Note
Securing portmap only affects NFSv2 and NFSv3 implementations, since NFSv4 no longer requires it. If you plan to implement an NFSv2 or NFSv3 server, then portmap is required, and the following section applies.
If running RPC services, follow these basic rules.
2.2.2.1.??Protect portmap With TCP Wrappers
It is important to use TCP Wrappers to limit which networks or hosts have access to the portmap service since it has no built-in form of authentication.
Further, use only IP addresses when limiting access to the service. Avoid using hostnames, as they can be forged by DNS poisoning and other methods.
Sendmail is a Mail Transport Agent (MTA) that uses the Simple Mail Transport Protocol (SMTP) to deliver electronic messages between other MTAs and to email clients or delivery agents. Although many MTAs are capable of encrypting traffic between one another, most do not, so sending email over any public networks is considered an inherently insecure form of communication.
It is recommended that anyone planning to implement a Sendmail server address the following issues.
2.2.7.1.??Limiting a Denial of Service Attack
Because of the nature of email, a determined attacker can flood the server with mail fairly easily and cause a denial of service. By setting limits to the following directives in /etc/mail/sendmail.mc, the effectiveness of such attacks is limited.
confCONNECTION_RATE_THROTTLE ??? The number of connections the server can receive per second. By default, Sendmail does not limit the number of connections. If a limit is set and reached, further connections are delayed.
confMAX_DAEMON_CHILDREN ??? The maximum number of child processes that can be spawned by the server. By default, Sendmail does not assign a limit to the number of child processes. If a limit is set and reached, further connections are delayed.
confMIN_FREE_BLOCKS ??? The minimum number of free blocks which must be available for the server to accept mail. The default is 100 blocks.
confMAX_HEADERS_LENGTH ??? The maximum acceptable size (in bytes) for a message header.
confMAX_MESSAGE_SIZE ??? The maximum acceptable size (in bytes) for a single message.
The Apache HTTP Server is one of the most stable and secure services that ships with Fedora. A large number of options and techniques are available to secure the Apache HTTP Server ??? too numerous to delve into deeply here.
System Administrators should be careful when using the following configuration options:
2.2.5.1.??FollowSymLinks
This directive is enabled by default, so be sure to use caution when creating symbolic links to the document root of the Web server. For instance, it is a bad idea to provide a symbolic link to /.
After configuring network services, it is important to pay attention to which ports are actually listening on the system's network interfaces. Any open ports can be evidence of an intrusion.
There are two basic approaches for listing the ports that are listening on the network. The less reliable approach is to query the network stack using commands such as netstat -an or lsof -i. This method is less reliable since these programs do not connect to the machine from the network, but rather check to see what is running on the system. For this reason, these applications are frequent targets for replacement by attackers. Crackers attempt to cover their tracks if they open unauthorized network ports by replacing netstat and lsof with their own, modified versions.
A more reliable way to check which ports are listening on the network is to use a port scanner such as nmap.
The following command issued from the console determines which ports are listening for TCP connections from the network:
nmap -sT -O localhost
The output of this command appears as follows:
Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2004-09-24 13:49 EDT
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1653 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcbind
113/tcp open auth
631/tcp open ipp
834/tcp open unknown
2601/tcp open zebra
32774/tcp open sometimes-rpc11
Device type: general purpose
Running: Linux 2.4.X|2.5.X|2.6.X OS details: Linux 2.5.25 - 2.6.3 or Gentoo 1.2 Linux 2.4.19 rc1-rc7)
Uptime 12.857 days (since Sat Sep 11 17:16:20 2004)
Nmap run completed -- 1 IP address (1 host up) scanned in 5.190 seconds
This output shows the system is running portmap due to the presence of the sunrpc service. However, there is also a mystery service on port 834. To check if the port is associated with the official list of known services, type:
cat /etc/services | grep 834
This command returns no output. This indicates that while the port is in the reserved range (meaning 0 through 1023) and requires root access to open, it is not associated with a known service.
Next, check for information about the port using netstat or lsof. To check for port 834 using netstat, use the following command:
netstat -anp | grep 834
The command returns the following output:
tcp 0 0 0.0.0.0:834 0.0.0.0:* LISTEN 653/ypbind
The presence of the open port in netstat is reassuring because a cracker opening a port surreptitiously on a hacked system is not likely to allow it to be revealed through this command. Also, the [p] option reveals the process ID (PID) of the service that opened the port. In this case, the open port belongs to ypbind (NIS), which is an RPC service handled in conjunction with the portmap service.
The lsof command reveals similar information to netstat since it is also capable of linking open ports to services:
lsof -i | grep 834
The relevant portion of the output from this command follows:
These tools reveal a great deal about the status of the services running on a machine. These tools are flexible and can provide a wealth of information about network services and configuration. Refer to the man pages for lsof, netstat, nmap, and services for more information.
When a system is used as a server on a public network, it becomes a target for attacks. Hardening the system and locking down services is therefore of paramount importance for the system administrator.
Before delving into specific issues, review the following general tips for enhancing server security:
Keep all services current, to protect against the latest threats.
Use secure protocols whenever possible.
Serve only one type of network service per machine whenever possible.
Monitor all servers carefully for suspicious activity.
2.2.1.??Securing Services With TCP Wrappers and xinetd
TCP Wrappers provide access control to a variety of services. Most modern network services, such as SSH, Telnet, and FTP, make use of TCP Wrappers, which stand guard between an incoming request and the requested service.
The benefits offered by TCP Wrappers are enhanced when used in conjunction with xinetd, a super server that provides additional access, logging, binding, redirection, and resource utilization control.
Tip
It is a good idea to use iptables firewall rules in conjunction with TCP Wrappers and xinetd to create redundancy within service access controls. Refer to Section??2.8, ???Firewalls??? for more information about implementing firewalls with iptables commands.
The following subsections assume a basic knowledge of each topic and focus on specific security options.
2.2.1.1.??Enhancing Security With TCP Wrappers
TCP Wrappers are capable of much more than denying access to services. This section illustrates how they can be used to send connection banners, warn of attacks from particular hosts, and enhance logging functionality. Refer to the hosts_options man page for information about the TCP Wrapper functionality and control language.
2.2.1.1.1.??TCP Wrappers and Connection Banners
Displaying a suitable banner when users connect to a service is a good way to let potential attackers know that the system administrator is being vigilant. You can also control what information about the system is presented to users. To implement a TCP Wrappers banner for a service, use the banner option.
This example implements a banner for vsftpd. To begin, create a banner file. It can be anywhere on the system, but it must have same name as the daemon. For this example, the file is called /etc/banners/vsftpd and contains the following line:
220-Hello, %c 220-All activity on ftp.example.com is logged. 220-Inappropriate use will result in your access privileges being removed.
The %c token supplies a variety of client information, such as the username and hostname, or the username and IP address to make the connection even more intimidating.
For this banner to be displayed to incoming connections, add the following line to the /etc/hosts.allow file:
vsftpd : ALL : banners /etc/banners/
2.2.1.1.2.??TCP Wrappers and Attack Warnings
If a particular host or network has been detected attacking the server, TCP Wrappers can be used to warn the administrator of subsequent attacks from that host or network using the spawn directive.
In this example, assume that a cracker from the 206.182.68.0/24 network has been detected attempting to attack the server. Place the following line in the /etc/hosts.deny file to deny any connection attempts from that network, and to log the attempts to a special file:
The %d token supplies the name of the service that the attacker was trying to access.
To allow the connection and log it, place the spawn directive in the /etc/hosts.allow file.
Note
Because the spawn directive executes any shell command, create a special script to notify the administrator or execute a chain of commands in the event that a particular client attempts to connect to the server.
2.2.1.1.3.??TCP Wrappers and Enhanced Logging
If certain types of connections are of more concern than others, the log level can be elevated for that service using the severity option.
For this example, assume that anyone attempting to connect to port 23 (the Telnet port) on an FTP server is a cracker. To denote this, place an emerg flag in the log files instead of the default flag, info, and deny the connection.
To do this, place the following line in /etc/hosts.deny:
in.telnetd : ALL : severity emerg
This uses the default authpriv logging facility, but elevates the priority from the default value of info to emerg, which posts log messages directly to the console.
2.2.1.2.??Enhancing Security With xinetd
This section focuses on using xinetd to set a trap service and using it to control resource levels available to any given xinetd service. Setting resource limits for services can help thwart Denial of Service (DoS) attacks. Refer to the man pages for xinetd and xinetd.conf for a list of available options.
2.2.1.2.1.??Setting a Trap
One important feature of xinetd is its ability to add hosts to a global no_access list. Hosts on this list are denied subsequent connections to services managed by xinetd for a specified period or until xinetd is restarted. You can do this using the SENSOR attribute. This is an easy way to block hosts attempting to scan the ports on the server.
The first step in setting up a SENSOR is to choose a service you do not plan on using. For this example, Telnet is used.
Edit the file /etc/xinetd.d/telnet and change the flags line to read:
flags = SENSOR
Add the following line:
deny_time = 30
This denies any further connection attempts to that port by that host for 30 minutes. Other acceptable values for the deny_time attribute are FOREVER, which keeps the ban in effect until xinetd is restarted, and NEVER, which allows the connection and logs it.
Finally, the last line should read:
disable = no
This enables the trap itself.
While using SENSOR is a good way to detect and stop connections from undesirable hosts, it has two drawbacks:
It does not work against stealth scans.
An attacker who knows that a SENSOR is running can mount a Denial of Service attack against particular hosts by forging their IP addresses and connecting to the forbidden port.
2.2.1.2.2.??Controlling Server Resources
Another important feature of xinetd is its ability to set resource limits for services under its control.
It does this using the following directives:
cps = <number_of_connections> <wait_period> ??? Limits the rate of incoming connections. This directive takes two arguments:
<number_of_connections> ??? The number of connections per second to handle. If the rate of incoming connections is higher than this, the service is temporarily disabled. The default value is fifty (50).
<wait_period> ??? The number of seconds to wait before re-enabling the service after it has been disabled. The default interval is ten (10) seconds.
instances = <number_of_connections> ??? Specifies the total number of connections allowed to a service. This directive accepts either an integer value or UNLIMITED.
per_source = <number_of_connections> ??? Specifies the number of connections allowed to a service by each host. This directive accepts either an integer value or UNLIMITED.
rlimit_as = <number[K|M]> ??? Specifies the amount of memory address space the service can occupy in kilobytes or megabytes. This directive accepts either an integer value or UNLIMITED.
rlimit_cpu = <number_of_seconds> ??? Specifies the amount of time in seconds that a service may occupy the CPU. This directive accepts either an integer value or UNLIMITED.
Using these directives can help prevent any single xinetd service from overwhelming the system, resulting in a denial of service.
--- NEW FILE sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html ---
2.3.5.??Configuring Firefox to use Kerberos for SSO
2.3.5.??Configuring Firefox to use Kerberos for SSO
You can configure Firefox to use Kerberos for Single Sign-on. In order for this functionality to work correctly, you need to configure your web browser to send your Kerberos credentials to the appropriate KDC.The following section describes the configuration changes and other requirements to achieve this.
In the address bar of Firefox, type about:config to display the list of current configuration options.
In the Filter field, type negotiate to restrict the list of options.
Double-click the network.negotiate-auth.trusted-uris entry to display the Enter string value dialog box.
Enter the name of the domain against which you want to authenticate, for example, .example.com.
Repeat the above procedure for the network.negotiate-auth.delegation-uris entry, using the same domain.
Note
You can leave this value blank, as it allows Kerberos ticket passing, which is not required.
If you do not see these two configuration options listed, your version of Firefox may be too old to support Negotiate authentication, and you should consider upgrading.
Configuring Firefox to use Kerberos for SSO.
Figure??2.6.??Configuring Firefox for SSO with Kerberos
You now need to ensure that you have Kerberos tickets. In a command shell, type kinit to retrieve Kerberos tickets. To display the list of available tickets, type klist. The following shows an example output from these commands:
[user at host ~] $ kinit
Password for user at EXAMPLE.COM:
[user at host ~] $ klist
Ticket cache: FILE:/tmp/krb5cc_10920
Default principal: user at EXAMPLE.COM
Valid starting Expires Service principal
10/26/06 23:47:54 10/27/06 09:47:54 krbtgt/USER.COM at USER.COM
renew until 10/26/06 23:47:54
Kerberos 4 ticket cache: /tmp/tkt10920
klist: You have no tickets cached
2.3.5.1.??Troubleshooting
If you have followed the configuration steps above and Negotiate authentication is not working, you can turn on verbose logging of the authentication process. This could help you find the cause of the problem. To enable verbose logging, use the following procedure:
Close all instances of Firefox.
Open a command shell, and enter the following commands:
Restart Firefox from that shell, and visit the website you were unable to authenticate to earlier. Information will be logged to /tmp/moz.log, and may give a clue to the problem. For example:
-1208550944[90039d0]: entering nsNegotiateAuth::GetNextToken()
-1208550944[90039d0]: gss_init_sec_context() failed: Miscellaneous failure
No credentials cache found
This indicates that you do not have Kerberos tickets, and need to run kinit.
If you are able to run kinit successfully from your machine but you are unable to authenticate, you might see something like this in the log file:
-1208994096[8d683d8]: entering nsAuthGSSAPI::GetNextToken()
-1208994096[8d683d8]: gss_init_sec_context() failed: Miscellaneous failure
Server not found in Kerberos database
This generally indicates a Kerberos configuration problem. Make sure that you have the correct entries in the [domain_realm] section of the /etc/krb5.conf file. For example:
If nothing appears in the log it is possible that you are behind a proxy, and that proxy is stripping off the HTTP headers required for Negotiate authentication. As a workaround, you can try to connect to the server using HTTPS instead, which allows the request to pass through unmodified. Then proceed to debug using the log file, as described above.
Before you can use your smart card to log in to your system and take advantage of the increased security options this technology provides, you need to perform some basic installation and configuration steps. These are described below.
Note
This section provides a high-level view of getting started with your smart card. More detailed information is available in the Red Hat Certificate System Enterprise Security Client Guide.
Log in with your Kerberos name and password
Make sure you have the nss-tools package loaded.
Download and install your corporate-specific root certificates. Use the following command to install the root CA certificate:
certutil -A -d /etc/pki/nssdb -n "root ca cert" -t "CT,C,C" -i ./ca_cert_in_base64_format.crt
Verify that you have the following RPMs installed on your system: esc, pam_pkcs11, coolkey, ifd-egate, ccid, gdm, authconfig, and authconfig-gtk.
Enable Smart Card Login Support
On the Gnome Title Bar, select System->Administration->Authentication.
Type your machine's root password if necessary.
In the Authentication Configuration dialog, click the Authentication tab.
Select the Enable Smart Card Support check box.
Click the Configure Smart Card... button to display the Smartcard Settings dialog, and specify the required settings:
Require smart card for login ??? Clear this check box. After you have successfully logged in with the smart card you can select this option to prevent users from logging in without a smart card.
Card Removal Action ??? This controls what happens when you remove the smart card after you have logged in. The available options are:
Lock ??? Removing the smart card locks the X screen.
Ignore ??? Removing the smart card has no effect.
If you need to enable the Online Certificate Status Protocol (OCSP), open the /etc/pam_pkcs11/pam_pkcs11.conf file, and locate the following line:
enable_ocsp = false;
Change this value to true, as follows:
enable_ocsp = true;
Enroll your smart card
If you are using a CAC card, you also need to perform the following steps:
Change to the root account and create a file called /etc/pam_pkcs11/cn_map.
Add the following entry to the cn_map file:
MY.CAC_CN.123454 -> myloginid
where MY.CAC_CN.123454 is the Common Name on your CAC and myloginid is your UNIX login ID.
Logout
2.3.2.1.??Troubleshooting
If you have trouble getting your smart card to work, try using the following command to locate the source of the problem:
pklogin_finder debug
If you run the pklogin_finder tool in debug mode while an enrolled smart card is plugged in, it attempts to output information about the validity of certificates, and if it is successful in attempting to map a login ID from the certificates that are on the card.
Smart cards are said to be enrolled when they have received an appropriate certificate signed by a valid Certificate Authority (CA). This involves several steps, described below:
The user inserts their smart card into the smart card reader on their workstation. This event is recognized by the Enterprise Security Client (ESC).
The enrollment page is displayed on the user's desktop. The user completes the required details and the user's system then connects to the Token Processing System (TPS) and the CA.
The TPS enrolls the smart card using a certificate signed by the CA.
This section provides a brief overview of the process of logging in using a smart card.
When the user inserts their smart card into the smart card reader, this event is recognized by the PAM facility, which prompts for the user's PIN.
The system then looks up the user's current certificates and verifies their validity. The certificate is then mapped to the user's UID.
This is validated against the KDC and login granted.
How Smart Card Login Works.
Figure??2.5.??How Smart Card Login Works
Note
You cannot log in with a card that has not been enrolled, even if it has been formatted. You need to log in with a formatted, enrolled card, or not using a smart card, before you can enroll a new card.
The Fedora SSO functionality reduces the number of times Fedora desktop users have to enter their passwords. Several major applications leverage the same underlying authentication and authorization mechanisms so that users can log in to Fedora from the log-in screen, and then not need to re-enter their passwords. These applications are detailed below.
In addition, users can log in to their machines even when there is no network (offline mode) or where network connectivity is unreliable, for example, wireless access. In the latter case, services will degrade gracefully.
2.3.1.1.??Supported Applications
The following applications are currently supported by the unified log-in scheme in Fedora:
Login
Screensaver
Firefox and Thunderbird
2.3.1.2.??Supported Authentication Mechanisms
Fedora currently supports the following authentication mechanisms:
Kerberos name/password login
Smart card/PIN login
2.3.1.3.??Supported Smart Cards
Fedora has been tested with the Cyberflex e-gate card and reader, but any card that complies with both Java card 2.1.1 and Global Platform 2.0.1 specifications should operate correctly, as should any reader that is supported by PCSC-lite.
Fedora has also been tested with Common Access Cards (CAC). The supported reader for CAC is the SCM SCR 331 USB Reader.
As of Fedora 5.2, Gemalto smart cards (Cyberflex Access 64k v2, standard with DER SHA1 value configured as in PKCSI v2.1) are now supported. These smart cards now use readers compliant with Chip/Smart Card Interface Devices (CCID).
2.3.1.4.??Advantages of Fedora Single Sign-on
Numerous security mechanisms currently exist that utilize a large number of protocols and credential stores. Examples include SSL, SSH, IPsec, and Kerberos. Fedora SSO aims to unify these schemes to support the requirements listed above. This does not mean replacing Kerberos with X.509v3 certificates, but rather uniting them to reduce the burden on both system users and the administrators who manage them.
To achieve this goal, Fedora:
Provides a single, shared instance of the NSS crypto libraries on each operating system.
Ships the Certificate System's Enterprise Security Client (ESC) with the base operating system. The ESC application monitors smart card insertion events. If it detects that the user has inserted a smart card that was designed to be used with the Fedora Certificate System server product, it displays a user interface instructing the user how to enroll that smart card.
Unifies Kerberos and NSS so that users who log in to the operating system using a smart card also obtain a Kerberos credential (which allows them to log in to file servers, etc.)
--- NEW FILE sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html ---
6.4.??Install Signed Packages from Well Known Repositories
6.4.??Install Signed Packages from Well Known Repositories
Software packages are published through repositories. All well known repositories support package signing. Package signing uses public key technology to prove that the package that was published by the repository has not been changed since the signature was applied. This provides some protection against installing software that may have been maliciously altered after the package was created but before you downloaded it.
Using too many repositories, untrustworthy repositories, or repositories with unsigned packages has a higher risk of introducing malicious or vulnerable code into your system. Use caution when adding repositories to yum/software update.
Fedora 9 is configured to apply all updates on a daily schedule. If you want to change the how your system installs updates you must do so via '''Software Update Preferences'''. You can change the schedule, the type of updates to apply or to notify you of available updates.
In Gnome, you can find controls for your updates at: System -> Preferences -> System -> Software Updates. In KDE it is located at: Applications -> Settings -> Software Updates.
All software contains bugs. Often, these bugs can result in a vulnerability that can expose your system to malicious users. Unpatched systems are a common cause of computer intrusions. You should have a plan to install security patches in a timely manner to close those vulnerabilities so they can not be exploited.
For home users, security updates should be installed as soon as possible. Configuring automatic installation of security updates is one way to avoid having to remember, but does carry a slight risk that something can cause a conflict with your configuration or with other software on the system.
For business or advanced home users, security updates should be tested and schedule for installation. Additional controls will need to be used to protect the system during the time between the patch release and its installation on the system. These controls would depend on the exact vulnerability, but could include additional firewall rules, the use of external firewalls, or changes in software settings.
In addition to basic rules that allow and deny access, the Fedora implementation of TCP Wrappers supports extensions to the access control language through option fields. By using option fields in hosts access rules, administrators can accomplish a variety of tasks such as altering log behavior, consolidating access control, and launching shell commands.
2.5.2.2.1.??Logging
Option fields let administrators easily change the log facility and priority level for a rule by using the severity directive.
In the following example, connections to the SSH daemon from any host in the example.com domain are logged to the default authprivsyslog facility (because no facility value is specified) with a priority of emerg:
sshd : .example.com : severity emerg
It is also possible to specify a facility using the severity option. The following example logs any SSH connection attempts by hosts from the example.com domain to the local0 facility with a priority of alert:
sshd : .example.com : severity local0.alert
Note
In practice, this example does not work until the syslog daemon (syslogd) is configured to log to the local0 facility. Refer to the syslog.conf man page for information about configuring custom log facilities.
More information about TCP Wrappers and xinetd is available from system documentation and on the Internet.
2.5.5.1.??Installed TCP Wrappers Documentation
The documentation on your system is a good place to start looking for additional configuration options for TCP Wrappers, xinetd, and access control.
/usr/share/doc/tcp_wrappers-<version>/ ??? This directory contains a README file that discusses how TCP Wrappers work and the various hostname and host address spoofing risks that exist.
/usr/share/doc/xinetd-<version>/ ??? This directory contains a README file that discusses aspects of access control and a sample.conf file with various ideas for modifying service-specific configuration files in the /etc/xinetd.d/ directory.
TCP Wrappers and xinetd-related man pages ??? A number of man pages exist for the various applications and configuration files involved with TCP Wrappers and xinetd. The following are some of the more important man pages:
Server Applications
man xinetd ??? The man page for xinetd.
Configuration Files
man 5 hosts_access ??? The man page for the TCP Wrappers hosts access control files.
man hosts_options ??? The man page for the TCP Wrappers options fields.
man xinetd.conf ??? The man page listing xinetd configuration options.
To determine if a client is allowed to connect to a service, TCP Wrappers reference the following two files, which are commonly referred to as hosts access files:
/etc/hosts.allow
/etc/hosts.deny
When a TCP-wrapped service receives a client request, it performs the following steps:
It references /etc/hosts.allow. ??? The TCP-wrapped service sequentially parses the /etc/hosts.allow file and applies the first rule specified for that service. If it finds a matching rule, it allows the connection. If not, it moves on to the next step.
It references /etc/hosts.deny. ??? The TCP-wrapped service sequentially parses the /etc/hosts.deny file. If it finds a matching rule, it denies the connection. If not, it grants access to the service.
The following are important points to consider when using TCP Wrappers to protect network services:
Because access rules in hosts.allow are applied first, they take precedence over rules specified in hosts.deny. Therefore, if access to a service is allowed in hosts.allow, a rule denying access to that same service in hosts.deny is ignored.
The rules in each file are read from the top down and the first matching rule for a given service is the only one applied. The order of the rules is extremely important.
If no rules for the service are found in either file, or if neither file exists, access to the service is granted.
TCP-wrapped services do not cache the rules from the hosts access files, so any changes to hosts.allow or hosts.deny take effect immediately, without restarting network services.
Warning
If the last line of a hosts access file is not a newline character (created by pressing the Enter key), the last rule in the file fails and an error is logged to either /var/log/messages or /var/log/secure. This is also the case for a rule that spans multiple lines without using the backslash character. The following example illustrates the relevant portion of a log message for a rule failure due to either of these circumstances:
warning: /etc/hosts.allow, line 20: missing newline or line too long
2.5.2.1.??Formatting Access Rules
The format for both /etc/hosts.allow and /etc/hosts.deny is identical. Each rule must be on its own line. Blank lines or lines that start with a hash (#) are ignored.
Each rule uses the following basic format to control access to network services:
<daemon list> ??? A comma-separated list of process names (not service names) or the ALL wildcard. The daemon list also accepts operators (refer to Section??2.5.2.1.4, ???Operators???) to allow greater flexibility.
<client list> ??? A comma-separated list of hostnames, host IP addresses, special patterns, or wildcards which identify the hosts affected by the rule. The client list also accepts operators listed in Section??2.5.2.1.4, ???Operators??? to allow greater flexibility.
<option> ??? An optional action or colon-separated list of actions performed when the rule is triggered. Option fields support expansions, launch shell commands, allow or deny access, and alter logging behavior.
Note
More information on the specialist terms above can be found elsewhere in this Guide:
The following is a basic sample hosts access rule:
vsftpd : .example.com
This rule instructs TCP Wrappers to watch for connections to the FTP daemon (vsftpd) from any host in the example.com domain. If this rule appears in hosts.allow, the connection is accepted. If this rule appears in hosts.deny, the connection is rejected.
The next sample hosts access rule is more complex and uses two option fields:
Note that each option field is preceded by the backslash (\). Use of the backslash prevents failure of the rule due to length.
This sample rule states that if a connection to the SSH daemon (sshd) is attempted from a host in the example.com domain, execute the echo command to append the attempt to a special log file, and deny the connection. Because the optional deny directive is used, this line denies access even if it appears in the hosts.allow file. Refer to Section??2.5.2.2, ???Option Fields??? for a more detailed look at available options.
2.5.2.1.1.??Wildcards
Wildcards allow TCP Wrappers to more easily match groups of daemons or hosts. They are used most frequently in the client list field of access rules.
The following wildcards are available:
ALL ??? Matches everything. It can be used for both the daemon list and the client list.
LOCAL ??? Matches any host that does not contain a period (.), such as localhost.
KNOWN ??? Matches any host where the hostname and host address are known or where the user is known.
UNKNOWN ??? Matches any host where the hostname or host address are unknown or where the user is unknown.
PARANOID ??? Matches any host where the hostname does not match the host address.
Caution
The KNOWN, UNKNOWN, and PARANOID wildcards should be used with care, because they rely on functioning DNS server for correct operation. Any disruption to name resolution may prevent legitimate users from gaining access to a service.
2.5.2.1.2.??Patterns
Patterns can be used in the client field of access rules to more precisely specify groups of client hosts.
The following is a list of common patterns for entries in the client field:
Hostname beginning with a period (.) ??? Placing a period at the beginning of a hostname matches all hosts sharing the listed components of the name. The following example applies to any host within the example.com domain:
ALL : .example.com
IP address ending with a period (.) ??? Placing a period at the end of an IP address matches all hosts sharing the initial numeric groups of an IP address. The following example applies to any host within the 192.168.x.x network:
ALL : 192.168.
IP address/netmask pair ??? Netmask expressions can also be used as a pattern to control access to a particular group of IP addresses. The following example applies to any host with an address range of 192.168.0.0 through 192.168.1.255:
ALL : 192.168.0.0/255.255.254.0
Important
When working in the IPv4 address space, the address/prefix length (prefixlen) pair declarations (CIDR notation) are not supported. Only IPv6 rules can use this format.
[IPv6 address]/prefixlen pair ??? [net]/prefixlen pairs can also be used as a pattern to control access to a particular group of IPv6 addresses. The following example would apply to any host with an address range of 3ffe:505:2:1:: through 3ffe:505:2:1:ffff:ffff:ffff:ffff:
ALL : [3ffe:505:2:1::]/64
The asterisk (*) ??? Asterisks can be used to match entire groups of hostnames or IP addresses, as long as they are not mixed in a client list containing other types of patterns. The following example would apply to any host within the example.com domain:
ALL : *.example.com
The slash (/) ??? If a client list begins with a slash, it is treated as a file name. This is useful if rules specifying large numbers of hosts are necessary. The following example refers TCP Wrappers to the /etc/telnet.hosts file for all Telnet connections:
in.telnetd : /etc/telnet.hosts
Other, lesser used, patterns are also accepted by TCP Wrappers. Refer to the hosts_access man 5 page for more information.
Warning
Be very careful when using hostnames and domain names. Attackers can use a variety of tricks to circumvent accurate name resolution. In addition, disruption to DNS service prevents even authorized users from using network services. It is, therefore, best to use IP addresses whenever possible.
2.5.2.1.3.??Portmap and TCP Wrappers
Portmap's implementation of TCP Wrappers does not support host look-ups, which means portmap can not use hostnames to identify hosts. Consequently, access control rules for portmap in hosts.allow or hosts.deny must use IP addresses, or the keyword ALL, for specifying hosts.
Changes to portmap access control rules may not take effect immediately. You may need to restart the portmap service.
Widely used services, such as NIS and NFS, depend on portmap to operate, so be aware of these limitations.
2.5.2.1.4.??Operators
At present, access control rules accept one operator, EXCEPT. It can be used in both the daemon list and the client list of a rule.
The EXCEPT operator allows specific exceptions to broader matches within the same rule.
In the following example from a hosts.allow file, all example.com hosts are allowed to connect to all services except cracker.example.com:
ALL: .example.com EXCEPT cracker.example.com
In another example from a hosts.allow file, clients from the 192.168.0.x network can use all services except for FTP:
ALL EXCEPT vsftpd: 192.168.0.
Note
Organizationally, it is often easier to avoid using EXCEPT operators. This allows other administrators to quickly scan the appropriate files to see what hosts are allowed or denied access to services, without having to sort through EXCEPT operators.
The xinetd daemon is a TCP-wrapped super service which controls access to a subset of popular network services, including FTP, IMAP, and Telnet. It also provides service-specific configuration options for access control, enhanced logging, binding, redirection, and resource utilization control.
When a client attempts to connect to a network service controlled by xinetd, the super service receives the request and checks for any TCP Wrappers access control rules.
If access is allowed, xinetd verifies that the connection is allowed under its own access rules for that service. It also checks that the service can have more resources allotted to it and that it is not in breach of any defined rules.
If all these conditions are met (that is, access is allowed to the service; the service has not reached its resource limit; and the service is not in breach of any defined rule), xinetd then starts an instance of the requested service and passes control of the connection to it. After the connection has been established, xinetd takes no further part in the communication between the client and the server.
The configuration files for xinetd are as follows:
/etc/xinetd.conf ??? The global xinetd configuration file.
/etc/xinetd.d/ ??? The directory containing all service-specific files.
2.5.4.1.??The /etc/xinetd.conf File
The /etc/xinetd.conf file contains general configuration settings which affect every service under xinetd's control. It is read when the xinetd service is first started, so for configuration changes to take effect, you need to restart the xinetd service. The following is a sample /etc/xinetd.conf file:
These lines control the following aspects of xinetd:
instances ??? Specifies the maximum number of simultaneous requests that xinetd can process.
log_type ??? Configures xinetd to use the authpriv log facility, which writes log entries to the /var/log/secure file. Adding a directive such as FILE /var/log/xinetdlog would create a custom log file called xinetdlog in the /var/log/ directory.
log_on_success ??? Configures xinetd to log successful connection attempts. By default, the remote host's IP address and the process ID of the server processing the request are recorded.
log_on_failure ??? Configures xinetd to log failed connection attempts or if the connection was denied.
cps ??? Configures xinetd to allow no more than 25 connections per second to any given service. If this limit is exceeded, the service is retired for 30 seconds.
includedir/etc/xinetd.d/ ??? Includes options declared in the service-specific configuration files located in the /etc/xinetd.d/ directory. Refer to Section??2.5.4.2, ???The /etc/xinetd.d/ Directory??? for more information.
Note
Often, both the log_on_success and log_on_failure settings in /etc/xinetd.conf are further modified in the service-specific configuration files. More information may therefore appear in a given service's log file than the /etc/xinetd.conf file may indicate. Refer to Section??2.5.4.3.1, ???Logging Options??? for further information.
Controlling access to network services is one of the most important security tasks facing a server administrator. Fedora provides several tools for this purpose. For example, an iptables-based firewall filters out unwelcome network packets within the kernel's network stack. For network services that utilize it, TCP Wrappers add an additional layer of protection by defining which hosts are or are not allowed to connect to "wrapped" network services. One such wrapped network service is the xinetdsuper server. This service is called a super server because it controls connections to a subset of network services and further refines access control.
Exhibit A: Access Control to Network Services Flowchart
Figure??2.9.??Access Control to Network Services
This chapter focuses on the role of TCP Wrappers and xinetd in controlling access to network services and reviews how these tools can be used to enhance both logging and utilization management. Refer to Section??2.9, ???IPTables??? for information about using firewalls with iptables.
2.5.1.??TCP Wrappers
The TCP Wrappers package (tcp_wrappers) is installed by default and provides host-based access control to network services. The most important component within the package is the /usr/lib/libwrap.a library. In general terms, a TCP-wrapped service is one that has been compiled against the libwrap.a library.
When a connection attempt is made to a TCP-wrapped service, the service first references the host's access files (/etc/hosts.allow and /etc/hosts.deny) to determine whether or not the client is allowed to connect. In most cases, it then uses the syslog daemon (syslogd) to write the name of the requesting client and the requested service to /var/log/secure or /var/log/messages.
If a client is allowed to connect, TCP Wrappers release control of the connection to the requested service and take no further part in the communication between the client and the server.
In addition to access control and logging, TCP Wrappers can execute commands to interact with the client before denying or releasing control of the connection to the requested network service.
Because TCP Wrappers are a valuable addition to any server administrator's arsenal of security tools, most network services within Fedora are linked to the libwrap.a library. Some such applications include /usr/sbin/sshd, /usr/sbin/sendmail, and /usr/sbin/xinetd.
Note
To determine if a network service binary is linked to libwrap.a, type the following command as the root user:
ldd <binary-name> | grep libwrap
Replace <binary-name> with the name of the network service binary.
If the command returns straight to the prompt with no output, then the network service is not linked to libwrap.a.
The following example indicates that /usr/sbin/sshd is linked to libwrap.a:
[root at myserver ~]# ldd /usr/sbin/sshd | grep libwrap
libwrap.so.0 => /usr/lib/libwrap.so.0 (0x00655000)
[root at myserver ~]#
2.5.1.1.??Advantages of TCP Wrappers
TCP Wrappers provide the following advantages over other network service control techniques:
Transparency to both the client and the wrapped network service ??? Both the connecting client and the wrapped network service are unaware that TCP Wrappers are in use. Legitimate users are logged and connected to the requested service while connections from banned clients fail.
Centralized management of multiple protocols ??? TCP Wrappers operate separately from the network services they protect, allowing many server applications to share a common set of access control configuration files, making for simpler management.
Administrators who fail to patch their systems are one of the greatest threats to server security. According to the System Administration Network and Security Institute (SANS), the primary cause of computer security vulnerability is to "assign untrained people to maintain security and provide neither the training nor the time to make it possible to do the job."[4] This applies as much to inexperienced administrators as it does to overconfident or amotivated administrators.
Some administrators fail to patch their servers and workstations, while others fail to watch log messages from the system kernel or network traffic. Another common error is when default passwords or keys to services are left unchanged. For example, some databases have default administration passwords because the database developers assume that the system administrator changes these passwords immediately after installation. If a database administrator fails to change this password, even an inexperienced cracker can use a widely-known default password to gain administrative privileges to the database. These are only a few examples of how inattentive administration can lead to compromised servers.
Even the most vigilant organization can fall victim to vulnerabilities if the network services they choose are inherently insecure. For instance, there are many services developed under the assumption that they are used over trusted networks; however, this assumption fails as soon as the service becomes available over the Internet ??? which is itself inherently untrusted.
One category of insecure network services are those that require unencrypted usernames and passwords for authentication. Telnet and FTP are two such services. If packet sniffing software is monitoring traffic between the remote user and such a service usernames and passwords can be easily intercepted.
Inherently, such services can also more easily fall prey to what the security industry terms the man-in-the-middle attack. In this type of attack, a cracker redirects network traffic by tricking a cracked name server on the network to point to his machine instead of the intended server. Once someone opens a remote session to the server, the attacker's machine acts as an invisible conduit, sitting quietly between the remote service and the unsuspecting user capturing information. In this way a cracker can gather administrative passwords and raw data without the server or the user realizing it.
Another category of insecure services include network file systems and information services such as NFS or NIS, which are developed explicitly for LAN usage but are, unfortunately, extended to include WANs (for remote users). NFS does not, by default, have any authentication or security mechanisms configured to prevent a cracker from mounting the NFS share and accessing anything contained therein. NIS, as well, has vital information that must be known by every computer on a network, including passwords and file permissions, within a plain text ASCII or DBM (ASCII-derived) database. A cracker who gains access to this database can then access every user account on a network, including the administrator's account.
By default, Fedora is released with all such services turned off. However, since administrators often find themselves forced to use these services, careful configuration is critical. Refer to Section??2.2, ???Server Security??? for more information about setting up services in a safe manner.
Most server applications that are included in a default installation are solid, thoroughly tested pieces of software. Having been in use in production environments for many years, their code has been thoroughly refined and many of the bugs have been found and fixed.
However, there is no such thing as perfect software and there is always room for further refinement. Moreover, newer software is often not as rigorously tested as one might expect, because of its recent arrival to production environments or because it may not be as popular as other server software.
Developers and system administrators often find exploitable bugs in server applications and publish the information on bug tracking and security-related websites such as the Bugtraq mailing list (http://www.securityfocus.com) or the Computer Emergency Response Team (CERT) website (http://www.cert.org). Although these mechanisms are an effective way of alerting the community to security vulnerabilities, it is up to system administrators to patch their systems promptly. This is particularly true because crackers have access to these same vulnerability tracking services and will use the information to crack unpatched systems whenever they can. Good system administration requires vigilance, constant bug tracking, and proper system maintenance to ensure a more secure computing environment.
Although an administrator may have a fully secure and patched server, that does not mean remote users are secure when accessing it. For instance, if the server offers Telnet or FTP services over a public network, an attacker can capture the plain text usernames and passwords as they pass over the network, and then use the account information to access the remote user's workstation.
Even when using secure protocols, such as SSH, a remote user may be vulnerable to certain attacks if they do not keep their client applications updated. For instance, v.1 SSH clients are vulnerable to an X-forwarding attack from malicious SSH servers. Once connected to the server, the attacker can quietly capture any keystrokes and mouse clicks made by the client over the network. This problem was fixed in the v.2 SSH protocol, but it is up to the user to keep track of what applications have such vulnerabilities and update them as necessary.
Section??2.1, ???Workstation Security??? discusses in more detail what steps administrators and home users should take to limit the vulnerability of computer workstations.
Establishing basic firewall policies creates a foundation for building more detailed, user-defined rules.
Each iptables chain is comprised of a default policy, and zero or more rules which work in concert with the default policy to define the overall ruleset for the firewall.
The default policy for a chain can be either DROP or ACCEPT. Security-minded administrators typically implement a default policy of DROP, and only allow specific packets on a case-by-case basis. For example, the following policies block all incoming and outgoing packets on a network gateway:
[root at myServer ~ ] # iptables -P INPUT DROP
[root at myServer ~ ] # iptables -P OUTPUT DROP
It is also recommended that any forwarded packets ??? network traffic that is to be routed from the firewall to its destination node ??? be denied as well, to restrict internal clients from inadvertent exposure to the Internet. To do this, use the following rule:
[root at myServer ~ ] # iptables -P FORWARD DROP
When you have established the default policies for each chain, you can create and save further rules for your particular network and security requirements.
The following sections describe how to save iptables rules and outline some of the rules you might implement in the course of building your iptables firewall.
Changes to iptables are transitory; if the system is rebooted or if the iptables service is restarted, the rules are automatically flushed and reset. To save the rules so that they are loaded when the iptables service is started, use the following command:
[root at myServer ~ ] # service iptables save
The rules are stored in the file /etc/sysconfig/iptables and are applied whenever the service is started or the machine is rebooted.
An IPsec connection is split into two logical phases. In phase 1, an IPsec node initializes the connection with the remote node or network. The remote node or network checks the requesting node's credentials and both parties negotiate the authentication method for the connection.
On Fedora systems, an IPsec connection uses the pre-shared key method of IPsec node authentication. In a pre-shared key IPsec connection, both hosts must use the same key in order to move to Phase 2 of the IPsec connection.
Phase 2 of the IPsec connection is where the Security Association (SA) is created between IPsec nodes. This phase establishes an SA database with configuration information, such as the encryption method, secret session key exchange parameters, and more. This phase manages the actual IPsec connection between remote nodes and networks.
The Fedora implementation of IPsec uses IKE for sharing keys between hosts across the Internet. The racoon keying daemon handles the IKE key distribution and exchange. Refer to the racoon man page for more information about this daemon.
Fedora supports IPsec for connecting remote hosts and networks to each other using a secure tunnel on a common carrier network such as the Internet. IPsec can be implemented using a host-to-host (one computer workstation to another) or network-to-network (one LAN/WAN to another) configuration.
The IPsec implementation in Fedora uses Internet Key Exchange (IKE), a protocol implemented by the Internet Engineering Task Force (IETF), used for mutual authentication and secure associations between connecting systems.
IPsec can be configured to connect one desktop or workstation (host) to another using a host-to-host connection. This type of connection uses the network to which each host is connected to create a secure tunnel between each host. The requirements of a host-to-host connection are minimal, as is the configuration of IPsec on each host. The hosts need only a dedicated connection to a carrier network (such as the Internet) and Fedora to create the IPsec connection.
2.7.6.1.??Host-to-Host Connection
A host-to-host IPsec connection is an encrypted connection between two systems, both running IPsec with the same authentication key. With the IPsec connection active, any network traffic between the two hosts is encrypted.
To configure a host-to-host IPsec connection, use the following steps for each host:
Note
You should perform the following procedures on the actual machine that you are configuring. Avoid attempting to configure and establish IPsec connections remotely.
In a command shell, type system-config-network to start the Network Administration Tool.
On the IPsec tab, click New to start the IPsec configuration wizard.
Click Forward to start configuring a host-to-host IPsec connection.
Enter a unique name for the connection, for example, ipsec0. If required, select the check box to automatically activate the connection when the computer starts. Click Forward to continue.
Select Host to Host encryption as the connection type, and then click Forward.
Select the type of encryption to use: manual or automatic.
If you select manual encryption, an encryption key must be provided later in the process. If you select automatic encryption, the racoon daemon manages the encryption key. The ipsec-tools package must be installed if you want to use automatic encryption.
Click Forward to continue.
Enter the IP address of the remote host.
To determine the IP address of the remote host, use the following command on the remote host:
[root at myServer ~] # /sbin/ifconfig <device>
where <device> is the Ethernet device that you want to use for the VPN connection.
If only one Ethernet card exists in the system, the device name is typically eth0. The following example shows the relevant information from this command (note that this is an example output only):
eth0 Link encap:Ethernet HWaddr 00:0C:6E:E8:98:1D
inet addr:172.16.44.192 Bcast:172.16.45.255 Mask:255.255.254.0
The IP address is the number following the inet addr: label.
Note
For host-to-host connections, both hosts should have a public, routable address. Alternatively, both hosts can have a private, non-routable address (for example, from the 10.x.x.x or 192.168.x.x ranges) as long as they are on the sam LAN.
If manual encryption was selected in step 6, specify the encryption key to use, or click Generate to create one.
Specify an authentication key or click Generate to generate one. It can be any combination of numbers and letters.
Click Forward to continue.
Verify the information on the IPsec ??? Summary page, and then click Apply.
Click File => Save to save the configuration.
You may need to restart the network for the changes to take effect. To restart the network, use the following command:
[root at myServer ~]# service network restart
Select the IPsec connection from the list and click the Activate button.
Repeat the entire procedure for the other host. It is essential that the same keys from step 8 be used on the other hosts. Otherwise, IPsec will not work.
Implementing IPsec requires that the ipsec-tools RPM package be installed on all IPsec hosts (if using a host-to-host configuration) or routers (if using a network-to-network configuration). The RPM package contains essential libraries, daemons, and configuration files for setting up the IPsec connection, including:
/sbin/setkey ??? manipulates the key management and security attributes of IPsec in the kernel. This executable is controlled by the racoon key management daemon. Refer to the setkey(8) man page for more information.
/sbin/racoon ??? the IKE key management daemon, used to manage and control security associations and key sharing between IPsec-connected systems.
/etc/racoon/racoon.conf ??? the racoon daemon configuration file used to configure various aspects of the IPsec connection, including authentication methods and encryption algorithms used in the connection. Refer to the racoon.conf(5) man page for a complete listing of available directives.
To configure IPsec on Fedora, you can use the Network Administration Tool, or manually edit the networking and IPsec configuration files.
IPsec can also be configured to connect an entire network (such as a LAN or WAN) to a remote network using a network-to-network connection. A network-to-network connection requires the setup of IPsec routers on each side of the connecting networks to transparently process and route information from one node on a LAN to a node on a remote LAN. Figure??2.11, ???A network-to-network IPsec tunneled connection??? shows a network-to-network IPsec tunneled connection.
This diagram shows two separate LANs separated by the Internet. These LANs use IPsec routers to authenticate and initiate a connection using a secure tunnel through the Internet. Packets that are intercepted in transit would require brute-force decryption in order to crack the cipher protecting the packets between these LANs. The process of communicating from one node in the 192.168.1.0/24 IP range to another in the 192.168.2.0/24 range is completely transparent to the nodes as the processing, encryption/decryption, and routing of the IPsec packets are completely handled by the IPsec router.
The information needed for a network-to-network connection include:
The externally-accessible IP addresses of the dedicated IPsec routers
The network address ranges of the LAN/WAN served by the IPsec routers (such as 192.168.1.0/24 or 10.0.1.0/24)
The IP addresses of the gateway devices that route the data from the network nodes to the Internet
A unique name, for example, ipsec1. This is used to identify the IPsec connection and to distinguish it from other devices or connections.
A fixed encryption key or one automatically generated by racoon
A pre-shared authentication key that is used during the initial stage of the connection and to exchange encryption keys during the session.
2.7.7.1.??Network-to-Network (VPN) Connection
A network-to-network IPsec connection uses two IPsec routers, one for each network, through which the network traffic for the private subnets is routed.
For example, as shown in Figure??2.12, ???Network-to-Network IPsec???, if the 192.168.1.0/24 private network sends network traffic to the 192.168.2.0/24 private network, the packets go through gateway0, to ipsec0, through the Internet, to ipsec1, to gateway1, and to the 192.168.2.0/24 subnet.
IPsec routers require publicly addressable IP addresses and a second Ethernet device connected to their respective private networks. Traffic only travels through an IPsec router if it is intended for another IPsec router with which it has an encrypted connection.
Network-to-Network IPsec
Figure??2.12.??Network-to-Network IPsec
Alternate network configuration options include a firewall between each IP router and the Internet, and an intranet firewall between each IPsec router and subnet gateway. The IPsec router and the gateway for the subnet can be one system with two Ethernet devices: one with a public IP address that acts as the IPsec router; and one with a private IP address that acts as the gateway for the private subnet. Each IPsec router can use the gateway for its private network or a public gateway to send the packets to the other IPsec router.
Use the following procedure to configure a network-to-network IPsec connection:
In a command shell, type system-config-network to start the Network Administration Tool.
On the IPsec tab, click New to start the IPsec configuration wizard.
Click Forward to start configuring a network-to-network IPsec connection.
Enter a unique nickname for the connection, for example, ipsec0. If required, select the check box to automatically activate the connection when the computer starts. Click Forward to continue.
Select Network to Network encryption (VPN) as the connection type, and then click Forward.
Select the type of encryption to use: manual or automatic.
If you select manual encryption, an encryption key must be provided later in the process. If you select automatic encryption, the racoon daemon manages the encryption key. The ipsec-tools package must be installed if you want to use automatic encryption.
Click Forward to continue.
On the Local Network page, enter the following information:
Local Network Address ??? The IP address of the device on the IPsec router connected to the private network.
Local Subnet Mask ??? The subnet mask of the local network IP address.
Local Network Gateway ??? The gateway for the private subnet.
Click Forward to continue.
Local Network Information
Figure??2.13.??Local Network Information
On the Remote Network page, enter the following information:
Remote IP Address ??? The publicly addressable IP address of the IPsec router for the other private network. In our example, for ipsec0, enter the publicly addressable IP address of ipsec1, and vice versa.
Remote Network Address ??? The network address of the private subnet behind the other IPsec router. In our example, enter 192.168.1.0 if configuring ipsec1, and enter 192.168.2.0 if configuring ipsec0.
Remote Subnet Mask ??? The subnet mask of the remote IP address.
Remote Network Gateway ??? The IP address of the gateway for the remote network address.
If manual encryption was selected in step 6, specify the encryption key to use or click Generate to create one.
Specify an authentication key or click Generate to generate one. This key can be any combination of numbers and letters.
Click Forward to continue.
Remote Network Information
Figure??2.14.??Remote Network Information
Verify the information on the IPsec ??? Summary page, and then click Apply.
Select File => Save to save the configuration.
Select the IPsec connection from the list, and then click Activate to activate the connection.
Enable IP forwarding:
Edit /etc/sysctl.conf and set net.ipv4.ip_forward to 1.
Use the following command to enable the change:
[root at myServer ~]# /sbin/sysctl -p /etc/sysctl.conf
The network script to activate the IPsec connection automatically creates network routes to send packets through the IPsec router if necessary.
--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html ---
2.7.8.??Starting and Stopping an IPsec Connection
Fedora provides various options in terms of implementing a software solution to securely connect to a WAN. Internet Protocol Security (IPsec) is the supported VPN implementation for Fedora, and sufficiently addresses the usability needs of organizations with branch offices or remote users.
Organizations with several satellite offices often connect to each other with dedicated lines for efficiency and protection of sensitive data in transit. For example, many businesses use frame relay or Asynchronous Transfer Mode (ATM) lines as an end-to-end networking solution to link one office with others. This can be an expensive proposition, especially for small to medium sized businesses (SMBs) that want to expand without paying the high costs associated with enterprise-level, dedicated digital circuits.
To address this need, Virtual Private Networks (VPNs) were developed. Following the same functional principles as dedicated circuits, VPNs allow for secured digital communication between two parties (or networks), creating a Wide Area Network (WAN) from existing Local Area Networks (LANs). Where it differs from frame relay or ATM is in its transport medium. VPNs transmit over IP using datagrams as the transport layer, making it a secure conduit through the Internet to an intended destination. Most free software VPN implementations incorporate open standard encryption methods to further mask data in transit.
Some organizations employ hardware VPN solutions to augment security, while others use software or protocol-based implementations. Several vendors provide hardware VPN solutions, such as Cisco, Nortel, IBM, and Checkpoint. There is a free software-based VPN solution for Linux called FreeS/Wan that utilizes a standardized Internet Protocol Security (IPsec) implementation. These VPN solutions, irrespective of whether they are hardware or software based, act as specialized routers that exist between the IP connection from one office to another.
2.7.1.??How Does a VPN Work?
When a packet is transmitted from a client, it sends it through the VPN router or gateway, which adds an Authentication Header (AH) for routing and authentication. The data is then encrypted and, finally, enclosed with an Encapsulating Security Payload (ESP). This latter constitutes the decryption and handling instructions.
The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption/decryption process in a network-to-network VPN connection is transparent to a local node.
With such a heightened level of security, an attacker must not only intercept a packet, but decrypt the packet as well. Intruders who employ a man-in-the-middle attack between a server and client must also have access to at least one of the private keys for authenticating sessions. Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
Vulnerability assessments may be broken down into one of two types: Outside looking in and inside looking around.
When performing an outside looking in vulnerability assessment, you are attempting to compromise your systems from the outside. Being external to your company provides you with the cracker's viewpoint. You see what a cracker sees ??? publicly-routable IP addresses, systems on your DMZ, external interfaces of your firewall, and more. DMZ stands for "demilitarized zone", which corresponds to a computer or small subnetwork that sits between a trusted internal network, such as a corporate private LAN, and an untrusted external network, such as the public Internet. Typically, the DMZ contains devices accessible to Internet traffic, such as Web (HTTP ) servers, FTP servers, SMTP (e-mail) servers and DNS servers.
When you perform an inside looking around vulnerability assessment, you are somewhat at an advantage since you are internal and your status is elevated to trusted. This is the viewpoint you and your co-workers have once logged on to your systems. You see print servers, file servers, databases, and other resources.
There are striking distinctions between these two types of vulnerability assessments. Being internal to your company gives you elevated privileges more so than any outsider. Still today in most organizations, security is configured in such a manner as to keep intruders out. Very little is done to secure the internals of the organization (such as departmental firewalls, user-level access controls, authentication procedures for internal resources, and more). Typically, there are many more resources when looking around inside as most systems are internal to a company. Once you set yourself outside of the company, you immediately are given an untrusted status. The systems and resources available to you externally are usually very limited.
Consider the difference between vulnerability assessments and penetration tests. Think of a vulnerability assessment as the first step to a penetration test. The information gleaned from the assessment is used for testing. Whereas, the assessment is checking for holes and potential vulnerabilities, the penetration testing actually attempts to exploit the findings.
Assessing network infrastructure is a dynamic process. Security, both information and physical, is dynamic. Performing an assessment shows an overview, which can turn up false positives and false negatives.
Security administrators are only as good as the tools they use and the knowledge they retain. Take any of the assessment tools currently available, run them against your system, and it is almost a guarantee that there are some false positives. Whether by program fault or user error, the result is the same. The tool may find vulnerabilities which in reality do not exist (false positive); or, even worse, the tool may not find vulnerabilities that actually do exist (false negative).
Now that the difference between a vulnerability assessment and a penetration test is defined, take the findings of the assessment and review them carefully before conducting a penetration test as part of your new best practices approach.
Warning
Attempting to exploit vulnerabilities on production resources can have adverse effects to the productivity and efficiency of your systems and network.
The following list examines some of the benefits to performing vulnerability assessments.
Creates proactive focus on information security
Finds potential exploits before crackers find them
Results in systems being kept up to date and patched
Promotes growth and aids in developing staff expertise
Abates Financial loss and negative publicity
1.2.2.1.??Establishing a Methodology
To aid in the selection of tools for a vulnerability assessment, it is helpful to establish a vulnerability assessment methodology. Unfortunately, there is no predefined or industry approved methodology at this time; however, common sense and best practices can act as a sufficient guide.
What is the target? Are we looking at one server, or are we looking at our entire network and everything within the network? Are we external or internal to the company? The answers to these questions are important as they help determine not only which tools to select but also the manner in which they are used.
To learn more about establishing methodologies, refer to the following websites:
An assessment can start by using some form of an information gathering tool. When assessing the entire network, map the layout first to find the hosts that are running. Once located, examine each host individually. Focusing on these hosts requires another set of tools. Knowing which tools to use may be the most crucial step in finding vulnerabilities.
Just as in any aspect of everyday life, there are many different tools that perform the same job. This concept applies to performing vulnerability assessments as well. There are tools specific to operating systems, applications, and even networks (based on the protocols used). Some tools are free; others are not. Some tools are intuitive and easy to use, while others are cryptic and poorly documented but have features that other tools do not.
Finding the right tools may be a daunting task and in the end, experience counts. If possible, set up a test lab and try out as many tools as you can, noting the strengths and weaknesses of each. Review the README file or man page for the tool. Additionally, look to the Internet for more information, such as articles, step-by-step guides, or even mailing lists specific to a tool.
The tools discussed below are just a small sampling of the available tools.
1.2.3.1.??Scanning Hosts with Nmap
Nmap is a popular tool included in Fedora that can be used to determine the layout of a network. Nmap has been available for many years and is probably the most often used tool when gathering information. An excellent man page is included that provides a detailed description of its options and usage. Administrators can use Nmap on a network to find host systems and open ports on those systems.
Nmap is a competent first step in vulnerability assessment. You can map out all the hosts within your network and even pass an option that allows Nmap to attempt to identify the operating system running on a particular host. Nmap is a good foundation for establishing a policy of using secure services and stopping unused services.
1.2.3.1.1.??Using Nmap
Nmap can be run from a shell prompt by typing the nmap command followed by the hostname or IP address of the machine to scan.
nmap foo.example.com
The results of the scan (which could take up to a few minutes, depending on where the host is located) should look similar to the following:
Starting nmap V. 3.50 ( www.insecure.org/nmap/ ) Interesting ports on localhost.localdomain (127.0.0.1): (The 1591 ports scanned but not shown below are in state: closed) Port State Service 22/tcp open ssh 25/tcp open smtp 111/tcp open sunrpc 443/tcp open https 515/tcp open printer 950/tcp open oftep-rpc 6000/tcp open X11 Nmap run completed -- 1 IP address (1 host up) scanned in 71.825 seconds
Nmap tests the most common network communication ports for listening or waiting services. This knowledge can be helpful to an administrator who wants to close down unnecessary or unused services.
For more information about using Nmap, refer to the official homepage at the following URL:
Given time, resources, and motivation, a cracker can break into nearly any system. At the end of the day, all of the security procedures and technologies currently available cannot guarantee that any systems are safe from intrusion. Routers help secure gateways to the Internet. Firewalls help secure the edge of the network. Virtual Private Networks safely pass data in an encrypted stream. Intrusion detection systems warn you of malicious activity. However, the success of each of these technologies is dependent upon a number of variables, including:
The expertise of the staff responsible for configuring, monitoring, and maintaining the technologies.
The ability to patch and update services and kernels quickly and efficiently.
The ability of those responsible to keep constant vigilance over the network.
Given the dynamic state of data systems and technologies, securing corporate resources can be quite complex. Due to this complexity, it is often difficult to find expert resources for all of your systems. While it is possible to have personnel knowledgeable in many areas of information security at a high level, it is difficult to retain staff who are experts in more than a few subject areas. This is mainly because each subject area of information security requires constant attention and focus. Information security does not stand still.
1.2.1.??Thinking Like the Enemy
Suppose that you administer an enterprise network. Such networks are commonly comprised of operating systems, applications, servers, network monitors, firewalls, intrusion detection systems, and more. Now imagine trying to keep current with each of these. Given the complexity of today's software and networking environments, exploits and bugs are a certainty. Keeping current with patches and updates for an entire network can prove to be a daunting task in a large organization with heterogeneous systems.
Combine the expertise requirements with the task of keeping current, and it is inevitable that adverse incidents occur, systems are breached, data is corrupted, and service is interrupted.
To augment security technologies and aid in protecting systems, networks, and data, you must think like a cracker and gauge the security of your systems by checking for weaknesses. Preventative vulnerability assessments against your own systems and network resources can reveal potential issues that can be addressed before a cracker exploits it.
A vulnerability assessment is an internal audit of your network and system security; the results of which indicate the confidentiality, integrity, and availability of your network (as explained in Section??1.1.1.3, ???Standardizing Security???). Typically, vulnerability assessment starts with a reconnaissance phase, during which important data regarding the target systems and resources is gathered. This phase leads to the system readiness phase, whereby the target is essentially checked for all known vulnerabilities. The readiness phase culminates in the reporting phase, where the findings are classified into categories of high, medium, and low risk; and methods for improving the security (or mitigating the risk of vulnerability) of the target are discussed.
If you were to perform a vulnerability assessment of your home, you would likely check each door to your home to see if they are closed and locked. You would also check every window, making sure that they closed completely and latch correctly. This same concept applies to systems, networks, and electronic data. Malicious users are the thieves and vandals of your data. Focus on their tools, mentality, and motivations, and you can then react swiftly to their actions.
A range of directives is available for services protected by xinetd. This section highlights some of the more commonly used options.
2.5.4.3.1.??Logging Options
The following logging options are available for both /etc/xinetd.conf and the service-specific configuration files within the /etc/xinetd.d/ directory.
The following is a list of some of the more commonly used logging options:
ATTEMPT ??? Logs the fact that a failed attempt was made (log_on_failure).
DURATION ??? Logs the length of time the service is used by a remote system (log_on_success).
EXIT ??? Logs the exit status or termination signal of the service (log_on_success).
HOST ??? Logs the remote host's IP address (log_on_failure and log_on_success).
PID ??? Logs the process ID of the server receiving the request (log_on_success).
USERID ??? Logs the remote user using the method defined in RFC 1413 for all multi-threaded stream services (log_on_failure andlog_on_success).
For a complete list of logging options, refer to the xinetd.conf man page.
The /etc/xinetd.d/ directory contains the configuration files for each service managed by xinetd and the names of the files correlate to the service. As with xinetd.conf, this directory is read only when the xinetd service is started. For any changes to take effect, the administrator must restart the xinetd service.
The format of files in the /etc/xinetd.d/ directory use the same conventions as /etc/xinetd.conf. The primary reason the configuration for each service is stored in a separate file is to make customization easier and less likely to affect other services.
To gain an understanding of how these files are structured, consider the /etc/xinetd.d/krb5-telnet file:
service telnet
{
flags = REUSE
socket_type = stream
wait = no
user = root
server = /usr/kerberos/sbin/telnetd
log_on_failure += USERID
disable = yes
}
These lines control various aspects of the telnet service:
service ??? Specifies the service name, usually one of those listed in the /etc/services file.
flags ??? Sets any of a number of attributes for the connection. REUSE instructs xinetd to reuse the socket for a Telnet connection.
Note
The REUSE flag is deprecated. All services now implicitly use the REUSE flag.
socket_type ??? Sets the network socket type to stream.
wait ??? Specifies whether the service is single-threaded (yes) or multi-threaded (no).
user ??? Specifies which user ID the process runs under.
server ??? Specifies which binary executable to launch.
log_on_failure ??? Specifies logging parameters for log_on_failure in addition to those already defined in xinetd.conf.
disable ??? Specifies whether the service is disabled (yes) or enabled (no).
Refer to the xinetd.conf man page for more information about these options and their usage.
From ricky at fedoraproject.org Mon Dec 22 19:06:52 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 22 Dec 2008 14:06:52 -0500
Subject: Meeting Reminder - 2008-12-22
Message-ID: <20081222190628.GA23943@sphe>
This is just a reminder that there'll be a websites meeting in
#fedora-meeting in about an hour (20:00 UTC)
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 22 19:12:46 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 22 Dec 2008 14:12:46 -0500
Subject: Hello! Need help here.
In-Reply-To:
References:
Message-ID: <20081222191246.GB23943@sphe>
On 2008-12-15 02:07:30 PM, Adam Watts wrote:
> Hi there Web Maser of the Fedora project.
>
> I have created a new account with you and i see on my
>
> Todo queue:
>
> ? You have not submitted an SSH key, some Fedora resources require an SSH
> key. Please submit yours by editing My Account
>
> Download a client-side certificate [icon]
>
> Can you tell me what this is, and do i need to do it ?
You can probably ignore these unless you are planning on becoming a
packager or doing anything that involves SSH access to Fedora servers.
The client-side certificate is also for packagers who use it to
authenticate to the buildsystem.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 22 19:16:13 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 22 Dec 2008 14:16:13 -0500
Subject: Self Introduction
In-Reply-To:
References:
Message-ID: <20081222191613.GC23943@sphe>
On 2008-12-15 11:34:04 PM, Jeffrey Ravenhorst wrote:
> My name is Jeffrey Ravenhorst, and i'm interested in contributing to the fedora
> websites project.
>
> I've been doing web programming/design for about 6 years now (i guess that's
> not a really long time, but i'm only 21), and its pretty much my favorite thing
> to do as far as computing goes. I'm currently a senior at Longwood University
> in virginia, usa, working on a BS in computer science (they really don't do
> much web stuff there, but i do a lot on my own and for work). Anyways, i hope i
> can help out... here are some of the things i consider myself useful for:
Hey, welcome! We have weekly meetings on Mondays (although we've missed
a few this month), so if you can make it, we have one in about 45
minutes in #fedora-meeting on irc.freenode.net.
Hopefully we'll be able to work out some tasks for people to work on in
the meeting.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From kwade at redhat.com Mon Dec 22 19:21:37 2008
From: kwade at redhat.com (Karsten Wade)
Date: Mon, 22 Dec 2008 11:21:37 -0800
Subject: moved docs.fp.org commits (/cvs/fedora/web/docs)
Message-ID: <20081222192137.GB24919@calliope.phig.org>
I just moved the address for commits to /cvs/fedora/web to go to
fedora-docs-commits, as those commits are only for
http://docs.fedoraproject.org. Thus, the security-guide content is
the last of those commit messages that go to this list. For future
commit messages, use:
http://redhat.com/mailman/listinfo/fedora-docs-commits
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 22 21:02:48 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 22 Dec 2008 16:02:48 -0500
Subject: Meeting Log - 2008-12-22
Message-ID: <20081222210248.GD23943@sphe>
20:00 -!- ricky changed the topic of #fedora-meeting to: Fedora Websites Meeting
20:00 * ianweller
20:00 * ricky
20:00 < ianweller> er wait, new format.
20:00 < ianweller> [[User:ianweller|Ian Weller]]
20:00 < ricky> Ha.
20:00 < ianweller> ricky: hey latest release of supybot-fedora has it so you can type '.wikiuser ianweller' and it'll spit that back
20:01 < ricky> Nice
20:01 -!- Sonar_Guy [n=Baconz at fedora/sonarguy] has quit "Xchat destroyed by Operating System"
20:01 < ricky> Aanybody else around?
20:02 < ianweller> rsc: ping?
20:02 -!- bassel [n=bassel at 82.137.249.90] has joined #fedora-meeting
20:02 * ricky notices that FergatROn was asking about the websites meeting
20:02 < FergatROn> i'm around but i'm not part of thr team yet.
20:02 < ianweller> FergatROn: doesn't matter, join in :)
20:02 < ricky> Ah, welcome then
20:03 < FergatROn> cool, i'm babysitting my kids so i have one hand to type with
20:03 < ricky> By the way, we hang out in #fedora-websites as well (but this is the meeting channel)
20:03 < ricky> Heh
20:03 < ricky> OK, so it's probably time to go through and clean up the tasks list again
20:03 < ricky> http://fedoraproject.org/wiki/Websites/Tasks
20:03 < FergatROn> cool i marked it
20:03 < rsc> ianweller: pong.
20:03 < rsc> [[User:robert|Robert Scheck]]
20:04 < ricky> Heh
20:04 < ricky> Aw, mizmo-out's out :-/
20:04 < ianweller> she's on vacation iirc
20:05 < ricky> Any idea what's going on with usability testing?
20:05 < ricky> Feedback on get-fedora was good, but I noticed some questions about join-fedora come up recently as well
20:05 -!- LetoTo [n=paul at CPE00d0cf047bfd-CM001225d87d3c.cpe.net.cable.rogers.com] has left #fedora-meeting []
20:05 -!- petreu| [n=peter at p3EE3E286.dip.t-dialin.net] has joined #fedora-meeting
20:05 -!- cassmodiah [n=cass at fedora/cassmodiah] has joined #fedora-meeting
20:06 < ricky> So this goes back to the question of how we want people to get started with Fedora
20:06 < ricky> For example, right now, http://fedoraproject.org/join-fedora has a huge banner telling people to sign up for an account
20:07 < ricky> Is that what we want the first step to be?
20:07 < ricky> (This would be a design decision both for the website and for FAS)
20:08 -!- bassel [n=bassel at 82.137.249.90] has quit "Leaving"
20:08 < ricky> Another question is - are we trying to generalize the tasks too much? Somebody was confused about "OS Developer" on the list recently
20:10 < ricky> So we've improved get-fedora a lot - let's try to make join-fedora our next page to fix up
20:10 < ianweller> i saw that
20:10 < ianweller> yeah, agreed.
20:10 < ianweller> i would say "perhaps a hackfest at FUDCon would help" but it seems like there's gonna be enough hackfests for everyone to be forced into two places at once
20:11 < ianweller> :P
20:11 < ricky> Unfortunately, FUDCon is a pretty hard place to find non-Fedora contributors to do usability testing or anything :-)
20:12 < ricky> So what do you think we should show somebody who wants to get involved with Fedora?
20:13 < ricky> I think it might be good to make it more task-based
20:13 < ricky> That way, people will be able to see an item and say "I can do that"
20:14 < FergatROn> so there's two questions posted and we're talking about the first one?
20:14 < ianweller> crap, i gotta go
20:15 * ianweller exits
20:15 < ricky> ianweller: See you
20:15 < ricky> FergatROn: Yeah
20:15 < FergatROn> isn't that how join-fedora is setup now?
20:15 < FergatROn> i see the tasks... or groups.
20:15 < ricky> By the way, input from new contributors is especially useful for stuff like this :-)
20:15 < FergatROn> sweet XD
20:16 < ricky> I guess it's kind of a mix right now.
20:16 < ricky> Designer is a pretty clear task, but something like "OS Developer" and "Content Writer" leads to a lot of teams
20:18 < FergatROn> how many teams are you looking to manage?
20:18 * ricky doesn't even know how many groups and teams we have all together
20:19 < ricky> Perhaps all we need to do is kind of an audit of all of the team pages off of join-fedora
20:20 < onekopakaa> sorry to come in mid-meeting
20:20 < ricky> I think it'd just be nicer to turn it into a step-by-step process or something easier/clearer
20:21 < ricky> Just curious: Do you think join-fedora was pretty clear?
20:21 < onekopakaa> yeah OS developer seems very general..
20:22 < FergatROn> If i recall, the sign up process was 1) show the groups, 2) sign up for an account...
20:22 < ricky> For example, how long did it take to find the websites mailing list?
20:22 < FergatROn> Not long for the mailing list... that's only because i'm tech savvy. Regular users might not find it.
20:23 < FergatROn> i would suggest a bigger support or community link on the home page.
20:23 < FergatROn> from there they can find it.
20:23 < ricky> Is there anything else that could have been useful on join-fedora?
20:24 < ricky> My main goal in getting people involved is first to get them to talk on mailing lists and IRC channels.
20:24 < FergatROn> I do have an issue.. with the login system. I'm trying to log into it and i forgot my username. I looked in my inbox and I don't see anything about the username. I'm trying to reset thepassword, but it needs the username. :(
20:24 < ricky> Ah, we need to add usernames to those emails then
20:24 < ricky> What's your email address?
20:25 < FergatROn> marc at fergytech.net
20:25 < ricky> .fas marc at fergytech.net
20:25 < zodbot> ricky: fergatron 'Marc Ferguson'
20:25 -!- ezq [n=ezq at 200-127-101-170.cab.prima.net.ar] has joined #fedora-meeting
20:25 < ricky> OK, that's your username :-)
20:25 < FergatROn> is it case sensitive cause I did that! ??
20:25 < ricky> Usernames are always all lowercase
20:26 < FergatROn> ok i'm in... lower case. gotta remember that.
20:26 < ricky> Cool
20:28 < FergatROn> so.. making it easier...
20:28 < FergatROn> do you want folks to join first or join a mailing list first?
20:28 < ricky> What I'd like to do is contact a few other teams to see how they want people to get involved with them
20:29 < ricky> The way I see it, joining a mailing list and talking to people on the team is usually the first step before an account is needed
20:29 < ricky> I'm not sure how other teams see things though
20:30 < ricky> So would anybody be interested in emailing around and getting a feel for what other teams need?
20:30 < onekopakaa> i have to shower so i hopefully will be back in time
20:30 < onekopakaa> ricky: i could do that.
20:30 -!- DemonJester [n=DemonJes at fedora/DemonJester] has quit "leaving"
20:30 < ricky> It'd be nice to streamline join-fedora so that we can have a single process for getting involved with all teams
20:31 < onekopakaa> auto subscribe script?
20:31 < FergatROn> If anything I think the "Group List" needs to be more user-friendly. It might need to be done at the wiki level or if it can be done with the join application. Show things by interest instead of listing all the groups. I don't know where to start.
20:31 < ricky> So I guess just asking for suggestions of how people should join those teams and how join-fedora can be improved to help that
20:31 < ricky> FergatROn: Do you mean the group list in FAS?
20:31 < ricky> FAS = https://admin.fedoraproject.org/accounts/
20:31 < FergatROn> yes
20:31 < ricky> Ahh, that's the thing
20:31 < ricky> That group list isn't meant to be the way to find things to get involved in
20:32 < ricky> That's what join-fedora and http://fedoraproject.org/wiki/Join are supposed to be for
20:32 -!- Pikachu_2014 [n=Pikachu_ at 81-66-20-24.rev.numericable.fr] has joined #fedora-meeting
20:32 < FergatROn> hmm, that is something.
20:32 < ricky> Which is why it might be confusing that the first thing we do is tell people to create an account
20:33 < FergatROn> i see now.. yes that is a bit out of order. I guess show the user all the possible groups (that might interest them) then have them create an account.
20:33 < ricky> onekopakaa: If you're feeling like it, sure :-) There are a bunch of IRC channels that might be good to ask in as well
20:34 -!- baig [n=baig at 202.143.112.106] has joined #fedora-meeting
20:34 < FergatROn> it kind of does that now, but there's not action on the join wiki page... after i select designer... i don't knwo what to do after that.
20:34 < ricky> FergatROn: Exactly. Groups in FAS are basically for access or tracking purposes, but teams in Fedora are what we want people to join
20:34 -!- warren [n=warren at redhat/wombat/warren] has quit "Leaving"
20:35 < FergatROn> ok, silly question then. How do I join a team?
20:35 < ricky> Ah, so maybe we need to give more instructions on the join page
20:35 < ricky> And make sure there's some page users can get to with step-by-step instructions on how to join a team
20:36 < FergatROn> yes, that would be very helpful. I think dumb it down as much as possible - to get users to understand.
20:36 < ricky> The way it is now, stuff like that is usually about 4 clicks away from our main page, so we should strive to decrease tht
20:36 -!- warren [n=warren at redhat/wombat/warren] has joined #fedora-meeting
20:37 < FergatROn> indeedy!
20:37 -!- ezq [n=ezq at 200-127-101-170.cab.prima.net.ar] has quit "Ex-Chat"
20:38 < ricky> So I'm thinking about what the first step would be..
20:38 < ricky> I guess it goes back to the teams. What I'd like to see is some sort of step-by-step process for getting involved with each team.
20:39 < ricky> For most teams, it's probably something like: subscribe to mailing list, send intro email, make account/apply to group
20:39 < FergatROn> I'm looking at http://fedoraproject.org/wiki/DocsProject/Join to get an idea... and the instructions is buried in there.
20:39 < ricky> The other teams like package maintainers, it's waaay longer than that
20:40 < ricky> So improving the join process has to take place in FAS as well
20:40 < ricky> How do you think FAS can be fixed to make things easier?
20:40 < FergatROn> yah it's: 1) join the mailing list, 2) register to bugzilla, 3) create an account in FAS... but then in FAS there's otehr steps right?
20:40 < ricky> Do you think we should hide the group list more, since it tends to be confusing and useless to users?
20:41 < FergatROn> yes, new users (like me) - still don't know how to sign up after doing all 3 things.
20:41 < ricky> In FAS, it's pretty much: make account, check email, fill in personal info, sign CLA, ...
20:41 < onekopakaa> back
20:41 < FergatROn> I'd like to be apart of the web team, but I haven't figured it out yet. :)
20:41 < ricky> FergatROn: Being on the mailing list and coming to meetings is definitely the right track :-)
20:41 < FergatROn> haha
20:42 < ricky> I've been thinking of two approaches to changing FAS
20:42 < ricky> One way is to detach FAS from everything else as much as possible - keep it strictly an account management tool
20:43 < ricky> The othe way is the try and integrate FAS into the process as much as possible, maybe even make it the central starting point
20:43 < ricky> Right now, we're in the middle of the road abou this
20:44 < FergatROn> wow that's two intense directions...
20:45 < ricky> Well, what are the advantages and disadvantages of either way?
20:45 -!- Pikachu_2014 [n=Pikachu_ at 81-66-20-24.rev.numericable.fr] has quit Read error: 60 (Operation timed out)
20:45 < onekopakaa> integration means adding more code
20:45 < onekopakaa> seperation means taking away code.
20:45 < FergatROn> I think the Wiki should be where all the instructions are laid out... and the FAS be the action platform.
20:46 < onekopakaa> FergatROn: makes sense
20:46 < FergatROn> I see, now, in FAS that the "web" group... i can apply to.
20:46 -!- Pikachu_2014 [n=Pikachu_ at 81-66-20-24.rev.numericable.fr] has joined #fedora-meeting
20:46 < onekopakaa> why isn't that IP masked?
20:46 < FergatROn> If we get the users to a step by step and a listing (by interest) of the groups. Then we can also show them how to use the FAS to join a group.
20:47 < ricky> Yeah. One thing is that getting data on the wiki is a lot easier than getting data on FAS
20:47 < onekopakaa> and in the Wiki, changes are easier to make
20:47 < onekopakaa> oh
20:47 < onekopakaa> but the page should be protected, assuming the Wiki uses MediaWiki's standard permissions
20:48 < ricky> Well, the wiki is currently only writable by people that have signed the CLA, so we're not too worried about vandalism
20:48 * onekopakaa rereads the CLA
20:50 * FergatROn joined the web group, quick someone approve him.
20:50 < FergatROn> haha
20:51 < onekopakaa> i'm thinking vandals won't sign the CLA
20:51 < FergatROn> what's a CLA?
20:52 < ricky> It's the contributor license agreement
20:52 < onekopakaa> FergatROn: contributor License agreement
20:52 < onekopakaa> http://fedoraproject.org/wiki/Legal/Licenses/CLA
20:52 < ricky> It's part of the process for some groups, so it's another thing that we need to make clearer in our join process
20:53 < onekopakaa> yeah
20:53 < FergatROn> oh yah... i didn't read it :(
20:53 < ricky> So some tasks to take away:
20:53 < ricky> We should email various teams to see what the process for getting involved is and how join-fedora can be changed to make it easier
20:54 < ricky> If anybody's interested, it'd be nice to come up with some drafts for how http://fedoraproject.org/wiki/Join can be improved
20:54 < ricky> Another thing that could be useful is a wiki template for a join page that teams can use
20:54 < FergatROn> good idea
20:54 < FergatROn> get us all on the same page
20:55 < onekopakaa> i'm good with MW templates
20:55 < ricky> Excellent :-)
20:55 < onekopakaa> considering I manged my wiki
20:55 < ricky> So you can make test pages under at /wiki/User:username/whatever and such
20:56 < onekopakaa> if freenode would release onekopaka
20:56 < onekopakaa> ..
20:56 < ricky> What's that?
20:56 < onekopakaa> onekopaka is my nick on other IRC networks
20:56 -!- ezq [n=ezq at 200-127-101-170.cab.prima.net.ar] has joined #fedora-meeting
20:56 < ricky> Ah, heh
20:57 < onekopakaa> i forgot the password to my nick
20:57 < ricky> You should be able to ask in #freenode, it hasn't been used for a year
20:57 < ricky> Er, 3 years
20:57 < onekopakaa> 3 years?
20:57 < ricky> Yeah
20:57 < onekopakaa> i dunno that it's been 3 years.
20:57 < ricky> /msg nickserv info onekopaka
20:58 < onekopakaa> 3 years 3 weeks
20:58 < onekopakaa> wow
20:58 < ricky> FergatROn, onekopakaa: So could you guys work on contacting groups and making those wiki templates?
20:58 < ricky> Don't forget to mail any progress to the list :-)
20:58 < onekopakaa> okay
20:59 < FergatROn> ricky, i can contact folks - just need to know who? ;)
21:00 < ricky> Ah, great - I'll get a list of some IRC channels and mailing lists together. It'll actually be a cool way for you to meet some people around the community
21:00 -!- onekopakaa is now known as onekopaka
21:01 < ricky> Ah, we're at the hour mark, so let's close the meeting
21:01 < ricky> Thanks for coming, everybody
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From kwade at fedoraproject.org Mon Dec 22 18:39:00 2008
From: kwade at fedoraproject.org (Karsten Wade)
Date: Mon, 22 Dec 2008 18:39:00 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US
Security_Guide-Encryption-Data_in_Motion-Secure_Shell.php, 1.1, NONE
Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.php,
1.1, NONE Security_Guide-Encryption-Data_in_Motion.php, 1.1, NONE
Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.php,
1.1, NONE We_Need_Feedback.php, 1.1,
NONE chap-Security_Guide-Encryption.php, 1.1, NONE
chap-Security_Guide-General_Principles_of_Information_Security.php,
1.1, NONE chap-Security_Guide-LUKS_Disk_Encryption.php, 1.1,
NONE chap-Security_Guide-References.php, 1.1,
NONE chap-Security_Guide-Secure_Installation.php, 1.1,
NONE chap-Security_Guide-Securing_Your_Network.php, 1.1,
NONE chap-Security_Guide-Security_Overview.php, 1.1,
NONE chap-Security_Guide-Software_Maintenance.php, 1.1,
NONE index.php, 1.1, NONE pref-Security_Guide-Preface.php, 1.1,
NONE sect-Security_Guide-Additional_Resources-Related_Books.php, 1.1,
NONE
sect-Security_Guide-Additional_Resources-Related_Documentation.php,
1.1, NONE
sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.php,
1.1, NONE
sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.php,
1.1, NONE
sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.php,
1.1,
NONE sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.php,
1.1, NONE
sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.php,
1.1, NONE
sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.php,
1.1, NONE
sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.php,
1.1, NONE
sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.php,
1.1, NONE
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.php,
1.1, NONE
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.php,
1.1, NONE
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.php,
1.1, NONE sect-Security_Guide-Attackers_and_Vulnerabilities.php, 1.1,
NONE
sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.php,
1.1, NONE
sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.php,
1.1,
NONE sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.php,
1.1, NONE
sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.php,
1.1, NONE
sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.php,
1.1, NONE
sect-Security_Guide-Command_Options_for_IPTables-Command_Options.php,
1.1, NONE
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.php,
1.1, NONE
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.php,
1.1, NONE
sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.php,
1.1, NONE
sect-Security_Guide-Command_Options_for_IPTables-Target_Options.php,
1.1, NONE sect-Security_Guide-Common_Exploits_and_Attacks.php, 1.1,
NONE
sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.php,
1.1, NONE
sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.php,
1.1, NONE sect-Security_Guide-Evaluating_the_Tools-Nessus.php,
1.1, NONE sect-Security_Guide-Evaluating_the_Tools-Nikto.php, 1.1,
NONE sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.php,
1.1,
NONE sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.php,
1.1, NONE sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.php,
1.1, NONE sect-Security_Guide-Firewalls-Additional_Resources.php, 1.1,
NONE sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.php,
1.1, NONE sect-Security_Guide-Firewalls-Common_IPTables_Filtering.php,
1.1, NONE sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.php,
1.1, NONE
sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.php,
1.1, NONE sect-Security_Guide-Firewalls-IPv6.php, 1.1, NONE
sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.php,
1.1, NONE sect-Security_Guide-Firewalls-Using_IPTables.php, 1.1,
NONE sect-Security_Guide-Firewalls.php, 1.1, NONE
sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.php,
1.1, NONE
sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.php,
1.1, NONE
sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.php,
1.1, NONE sect-Security_Guide-IPTables-Additional_Resources.php, 1.1,
NONE sect-Security_Guide-IPTables-Command_Options_for_IPTables.php,
1.1, NONE
sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.php,
1.1, NONE sect-Security_Guide-IPTables-IPTables_Control_Scripts.php,
1.1, NONE sect-Security_Guide-IPTables-IPTables_and_IPv6.php,
1.1, NONE sect-Security_Guide-IPTables-Saving_IPTables_Rules.php,
1.1, NONE sect-Security_Guide-IPTables.php, 1.1, NONE
sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.php,
1.1,
NONE sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.php,
1.1, NONE sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.php,
1.1, NONE
sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.php,
1.1, NONE
sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.php,
1.1, NONE sect-Security_Guide-Kerberos-Additional_Resources.php, 1.1,
NONE sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.php,
1.1,
NONE sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.php,
1.1, NONE sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.php,
1.1, NONE sect-Security_Guide-Kerberos-How_Kerberos_Works.php,
1.1, NONE sect-Security_Guide-Kerberos-Kerberos_Terminology.php,
1.1, NONE sect-Security_Guide-Kerberos-Kerberos_and_PAM.php, 1.1, NONE
sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.php,
1.1, NONE sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.php,
1.1, NONE sect-Security_Guide-Kerberos.php, 1.1,
NONE sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.php,
1.1, NONE
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.php,
1.1, NONE
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.php,
1.1, NONE
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.php,
1.1, NONE sect-Security_Guide-Option_Fields-Access_Control.php,
1.1, NONE sect-Security_Guide-Option_Fields-Expansions.php, 1.1,
NONE sect-Security_Guide-Option_Fields-Shell_Commands.php, 1.1, NONE
sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.php,
1.1, NONE
sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.php,
1.1, NONE
sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.php,
1.1, NONE
sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.php,
1.1, NONE
sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.php,
1.1, NONE
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.php,
1.1,
NONE sect-Security_Guide-Pluggable_Authentication_Modules_PAM.php,
1.1, NONE
sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.php,
1.1, NONE sect-Security_Guide-Securing_FTP-Anonymous_Access.php, 1.1,
NONE
sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.php,
1.1, NONE sect-Security_Guide-Securing_FTP-User_Accounts.php, 1.1,
NONE sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.php,
1.1, NONE
sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.php,
1.1, NONE
sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.php,
1.1, NONE
sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.php,
1.1,
NONE sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.php,
1.1, NONE
sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.php,
1.1, NONE
sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.php,
1.1, NONE sect-Security_Guide-Securing_Sendmail-Mail_only_Users.php,
1.1, NONE sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.php,
1.1, NONE
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.php,
1.1, NONE
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.php,
1.1, NONE
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.php,
1.1, NONE
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.php,
1.1, NONE sect-Security_Guide-Security_Updates.php, 1.1,
NONE sect-Security_Guide-Server_Security-Securing_FTP.php, 1.1,
NONE sect-Security_Guide-Server_Security-Securing_NFS.php, 1.1,
NONE sect-Security_Guide-Server_Security-Securing_NIS.php, 1.1,
NONE sect-Security_Guide-Server_Security-Securing_Portmap.php, 1.1,
NONE sect-Security_Guide-Server_Security-Securing_Sendmail.php, 1.1,
NONE
sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.php,
1.1, NONE
sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.php,
1.1, NONE sect-Security_Guide-Server_Security.php, 1.1, NONE
sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.php,
1.1, NONE
sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.php,
1.1, NONE
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.php,
1.1, NONE
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.php,
1.1, NONE sect-Security_Guide-Single_Sign_on_SSO.php, 1.1, NONE
sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.php,
1.1, NONE
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.php,
1.1, NONE
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.php,
1.1, NONE
sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.php,
1.1, NONE
sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.php,
1.1, NONE
sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.php,
1.1, NONE sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.php, 1.1,
NONE
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.php,
1.1, NONE sect-Security_Guide-TCP_Wrappers_and_xinetd.php, 1.1, NONE
sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.php,
1.1, NONE
sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.php,
1.1, NONE
sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.php,
1.1, NONE
sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.php,
1.1,
NONE sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.php,
1.1, NONE
sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.php,
1.1, NONE
sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.php,
1.1, NONE sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.php,
1.1, NONE
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.php,
1.1, NONE
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.php,
1.1, NONE
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.php,
1.1, NONE
sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.php,
1.1, NONE
sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.php,
1.1, NONE sect-Security_Guide-Virtual_Private_Networks_VPNs.php, 1.1,
NONE
sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.php,
1.1, NONE
sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.php,
1.1, NONE sect-Security_Guide-Vulnerability_Assessment.php, 1.1, NONE
sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.php,
1.1, NONE
sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.php,
1.1, NONE
Message-ID: <20081222183900.C887870130@cvs1.fedora.phx.redhat.com>
Author: kwade
Update of /cvs/fedora/web/html/docs/security-guide/en_US
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv26290
Removed Files:
Security_Guide-Encryption-Data_in_Motion-Secure_Shell.php
Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.php
Security_Guide-Encryption-Data_in_Motion.php
Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.php
We_Need_Feedback.php chap-Security_Guide-Encryption.php
chap-Security_Guide-General_Principles_of_Information_Security.php
chap-Security_Guide-LUKS_Disk_Encryption.php
chap-Security_Guide-References.php
chap-Security_Guide-Secure_Installation.php
chap-Security_Guide-Securing_Your_Network.php
chap-Security_Guide-Security_Overview.php
chap-Security_Guide-Software_Maintenance.php index.php
pref-Security_Guide-Preface.php
sect-Security_Guide-Additional_Resources-Related_Books.php
sect-Security_Guide-Additional_Resources-Related_Documentation.php
sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.php
sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.php
sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.php
sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.php
sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.php
sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.php
sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.php
sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.php
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.php
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.php
sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.php
sect-Security_Guide-Attackers_and_Vulnerabilities.php
sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.php
sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.php
sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.php
sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.php
sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.php
sect-Security_Guide-Command_Options_for_IPTables-Command_Options.php
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.php
sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.php
sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.php
sect-Security_Guide-Command_Options_for_IPTables-Target_Options.php
sect-Security_Guide-Common_Exploits_and_Attacks.php
sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.php
sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.php
sect-Security_Guide-Evaluating_the_Tools-Nessus.php
sect-Security_Guide-Evaluating_the_Tools-Nikto.php
sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.php
sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.php
sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.php
sect-Security_Guide-Firewalls-Additional_Resources.php
sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.php
sect-Security_Guide-Firewalls-Common_IPTables_Filtering.php
sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.php
sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.php
sect-Security_Guide-Firewalls-IPv6.php
sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.php
sect-Security_Guide-Firewalls-Using_IPTables.php
sect-Security_Guide-Firewalls.php
sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.php
sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.php
sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.php
sect-Security_Guide-IPTables-Additional_Resources.php
sect-Security_Guide-IPTables-Command_Options_for_IPTables.php
sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.php
sect-Security_Guide-IPTables-IPTables_Control_Scripts.php
sect-Security_Guide-IPTables-IPTables_and_IPv6.php
sect-Security_Guide-IPTables-Saving_IPTables_Rules.php
sect-Security_Guide-IPTables.php
sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.php
sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.php
sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.php
sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.php
sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.php
sect-Security_Guide-Kerberos-Additional_Resources.php
sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.php
sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.php
sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.php
sect-Security_Guide-Kerberos-How_Kerberos_Works.php
sect-Security_Guide-Kerberos-Kerberos_Terminology.php
sect-Security_Guide-Kerberos-Kerberos_and_PAM.php
sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.php
sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.php
sect-Security_Guide-Kerberos.php
sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.php
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.php
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.php
sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.php
sect-Security_Guide-Option_Fields-Access_Control.php
sect-Security_Guide-Option_Fields-Expansions.php
sect-Security_Guide-Option_Fields-Shell_Commands.php
sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.php
sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.php
sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.php
sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.php
sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.php
sect-Security_Guide-Pluggable_Authentication_Modules_PAM.php
sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.php
sect-Security_Guide-Securing_FTP-Anonymous_Access.php
sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.php
sect-Security_Guide-Securing_FTP-User_Accounts.php
sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.php
sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.php
sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.php
sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.php
sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.php
sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.php
sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.php
sect-Security_Guide-Securing_Sendmail-Mail_only_Users.php
sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.php
sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.php
sect-Security_Guide-Security_Updates.php
sect-Security_Guide-Server_Security-Securing_FTP.php
sect-Security_Guide-Server_Security-Securing_NFS.php
sect-Security_Guide-Server_Security-Securing_NIS.php
sect-Security_Guide-Server_Security-Securing_Portmap.php
sect-Security_Guide-Server_Security-Securing_Sendmail.php
sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.php
sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.php
sect-Security_Guide-Server_Security.php
sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.php
sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.php
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.php
sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.php
sect-Security_Guide-Single_Sign_on_SSO.php
sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.php
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.php
sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.php
sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.php
sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.php
sect-Security_Guide-TCP_Wrappers_and_xinetd.php
sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.php
sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.php
sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.php
sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.php
sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.php
sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.php
sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.php
sect-Security_Guide-Virtual_Private_Networks_VPNs.php
sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.php
sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.php
sect-Security_Guide-Vulnerability_Assessment.php
sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.php
sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.php
Log Message:
removing the PHP files so we are only using the HTML and not confusing the web server :)
--- Security_Guide-Encryption-Data_in_Motion-Secure_Shell.php DELETED ---
--- Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.php DELETED ---
--- Security_Guide-Encryption-Data_in_Motion.php DELETED ---
--- Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.php DELETED ---
--- We_Need_Feedback.php DELETED ---
--- chap-Security_Guide-Encryption.php DELETED ---
--- chap-Security_Guide-General_Principles_of_Information_Security.php DELETED ---
--- chap-Security_Guide-LUKS_Disk_Encryption.php DELETED ---
--- chap-Security_Guide-References.php DELETED ---
--- chap-Security_Guide-Secure_Installation.php DELETED ---
--- chap-Security_Guide-Securing_Your_Network.php DELETED ---
--- chap-Security_Guide-Security_Overview.php DELETED ---
--- chap-Security_Guide-Software_Maintenance.php DELETED ---
--- index.php DELETED ---
--- pref-Security_Guide-Preface.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Related_Books.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Related_Documentation.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.php DELETED ---
--- sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.php DELETED ---
--- sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.php DELETED ---
--- sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.php DELETED ---
--- sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.php DELETED ---
--- sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.php DELETED ---
--- sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.php DELETED ---
--- sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.php DELETED ---
--- sect-Security_Guide-Attackers_and_Vulnerabilities.php DELETED ---
--- sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.php DELETED ---
--- sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.php DELETED ---
--- sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.php DELETED ---
--- sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.php DELETED ---
--- sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.php DELETED ---
--- sect-Security_Guide-Command_Options_for_IPTables-Command_Options.php DELETED ---
--- sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.php DELETED ---
--- sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.php DELETED ---
--- sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.php DELETED ---
--- sect-Security_Guide-Command_Options_for_IPTables-Target_Options.php DELETED ---
--- sect-Security_Guide-Common_Exploits_and_Attacks.php DELETED ---
--- sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.php DELETED ---
--- sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.php DELETED ---
--- sect-Security_Guide-Evaluating_the_Tools-Nessus.php DELETED ---
--- sect-Security_Guide-Evaluating_the_Tools-Nikto.php DELETED ---
--- sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.php DELETED ---
--- sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.php DELETED ---
--- sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.php DELETED ---
--- sect-Security_Guide-Firewalls-Additional_Resources.php DELETED ---
--- sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.php DELETED ---
--- sect-Security_Guide-Firewalls-Common_IPTables_Filtering.php DELETED ---
--- sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.php DELETED ---
--- sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.php DELETED ---
--- sect-Security_Guide-Firewalls-IPv6.php DELETED ---
--- sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.php DELETED ---
--- sect-Security_Guide-Firewalls-Using_IPTables.php DELETED ---
--- sect-Security_Guide-Firewalls.php DELETED ---
--- sect-Security_Guide-General_Principles_of_Information_Security-DISA_IASE_Documents.php DELETED ---
--- sect-Security_Guide-General_Principles_of_Information_Security-NSA_Documents.php DELETED ---
--- sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools.php DELETED ---
--- sect-Security_Guide-IPTables-Additional_Resources.php DELETED ---
--- sect-Security_Guide-IPTables-Command_Options_for_IPTables.php DELETED ---
--- sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.php DELETED ---
--- sect-Security_Guide-IPTables-IPTables_Control_Scripts.php DELETED ---
--- sect-Security_Guide-IPTables-IPTables_and_IPv6.php DELETED ---
--- sect-Security_Guide-IPTables-Saving_IPTables_Rules.php DELETED ---
--- sect-Security_Guide-IPTables.php DELETED ---
--- sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.php DELETED ---
--- sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.php DELETED ---
--- sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.php DELETED ---
--- sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.php DELETED ---
--- sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.php DELETED ---
--- sect-Security_Guide-Kerberos-Additional_Resources.php DELETED ---
--- sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.php DELETED ---
--- sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.php DELETED ---
--- sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.php DELETED ---
--- sect-Security_Guide-Kerberos-How_Kerberos_Works.php DELETED ---
--- sect-Security_Guide-Kerberos-Kerberos_Terminology.php DELETED ---
--- sect-Security_Guide-Kerberos-Kerberos_and_PAM.php DELETED ---
--- sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.php DELETED ---
--- sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.php DELETED ---
--- sect-Security_Guide-Kerberos.php DELETED ---
--- sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.php DELETED ---
--- sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.php DELETED ---
--- sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.php DELETED ---
--- sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.php DELETED ---
--- sect-Security_Guide-Option_Fields-Access_Control.php DELETED ---
--- sect-Security_Guide-Option_Fields-Expansions.php DELETED ---
--- sect-Security_Guide-Option_Fields-Shell_Commands.php DELETED ---
--- sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.php DELETED ---
--- sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.php DELETED ---
--- sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.php DELETED ---
--- sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.php DELETED ---
--- sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.php DELETED ---
--- sect-Security_Guide-Pluggable_Authentication_Modules_PAM.php DELETED ---
--- sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.php DELETED ---
--- sect-Security_Guide-Securing_FTP-Anonymous_Access.php DELETED ---
--- sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.php DELETED ---
--- sect-Security_Guide-Securing_FTP-User_Accounts.php DELETED ---
--- sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.php DELETED ---
--- sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.php DELETED ---
--- sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.php DELETED ---
--- sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.php DELETED ---
--- sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.php DELETED ---
--- sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.php DELETED ---
--- sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.php DELETED ---
--- sect-Security_Guide-Securing_Sendmail-Mail_only_Users.php DELETED ---
--- sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.php DELETED ---
--- sect-Security_Guide-Securing_the_Apache_HTTP_Server-Do_Not_Remove_the_IncludesNoExec_Directive.php DELETED ---
--- sect-Security_Guide-Securing_the_Apache_HTTP_Server-Restrict_Permissions_for_Executable_Directories.php DELETED ---
--- sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_Indexes_Directive.php DELETED ---
--- sect-Security_Guide-Securing_the_Apache_HTTP_Server-The_UserDir_Directive.php DELETED ---
--- sect-Security_Guide-Security_Updates.php DELETED ---
--- sect-Security_Guide-Server_Security-Securing_FTP.php DELETED ---
--- sect-Security_Guide-Server_Security-Securing_NFS.php DELETED ---
--- sect-Security_Guide-Server_Security-Securing_NIS.php DELETED ---
--- sect-Security_Guide-Server_Security-Securing_Portmap.php DELETED ---
--- sect-Security_Guide-Server_Security-Securing_Sendmail.php DELETED ---
--- sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.php DELETED ---
--- sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.php DELETED ---
--- sect-Security_Guide-Server_Security.php DELETED ---
--- sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.php DELETED ---
--- sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.php DELETED ---
--- sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.php DELETED ---
--- sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.php DELETED ---
--- sect-Security_Guide-Single_Sign_on_SSO.php DELETED ---
--- sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.php DELETED ---
--- sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.php DELETED ---
--- sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.php DELETED ---
--- sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.php DELETED ---
--- sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.php DELETED ---
--- sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.php DELETED ---
--- sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.php DELETED ---
--- sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.php DELETED ---
--- sect-Security_Guide-TCP_Wrappers_and_xinetd.php DELETED ---
--- sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.php DELETED ---
--- sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.php DELETED ---
--- sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.php DELETED ---
--- sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.php DELETED ---
--- sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.php DELETED ---
--- sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.php DELETED ---
--- sect-Security_Guide-Virtual_Private_Networks_VPNs.php DELETED ---
--- sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.php DELETED ---
--- sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.php DELETED ---
--- sect-Security_Guide-Vulnerability_Assessment.php DELETED ---
--- sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.php DELETED ---
--- sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.php DELETED ---
From sparks at fedoraproject.org Mon Dec 22 18:41:38 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 18:41:38 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/Common_Content - New directory
Message-ID: <20081222184138.EC80A70130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv27320/Common_Content
Log Message:
Directory /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content added to the repository
From sparks at fedoraproject.org Mon Dec 22 18:41:56 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 18:41:56 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/images - New directory
Message-ID: <20081222184156.E984A70130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/images
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv27427/images
Log Message:
Directory /cvs/fedora/web/html/docs/security-guide/en_US/images added to the repository
From sparks at fedoraproject.org Mon Dec 22 18:49:21 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 18:49:21 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/Common_Content/css - New
directory
Message-ID: <20081222184921.65C7E70130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content/css
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv29170/css
Log Message:
Directory /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content/css added to the repository
From sparks at fedoraproject.org Mon Dec 22 18:49:29 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 18:49:29 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/Common_Content/images - New
directory
Message-ID: <20081222184929.EFC8770130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content/images
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv29215/images
Log Message:
Directory /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content/images added to the repository
From sparks at fedoraproject.org Mon Dec 22 19:10:00 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 19:10:00 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/Common_Content/css common.css,
NONE, 1.1 default.css, NONE, 1.1 overrides.css, NONE, 1.1
Message-ID: <20081222191000.A797870130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content/css
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv4312/Common_Content/css
Added Files:
common.css default.css overrides.css
Log Message:
Adding Common_Content and image directories
--- NEW FILE common.css ---
body, h1, h2, h3, h4, h5, h6, pre, li, div {
line-height: 1.29em;
}
body {
background-color: white;
margin:0 auto;
font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
font-size:12px;
max-width:55em;
color:black;
}
body.toc_embeded {
/*for web hosting system only*/
margin-left: 300px;
}
object.toc {
/*for web hosting system only*/
border-style:none;
position:fixed;
width:290px;
height:99.99%;
top:0;
left:0;
z-index: 100;
border-style:none;
border-right:1px solid #999;
}
/* desktop styles */
body.desktop {
margin-left: 24em;
}
body.desktop .book > .toc {
display:block;
width:24em;
height:99%;
position:fixed;
overflow:auto;
top:0px;
left:0px;
padding-left:1em;
background-color:#EEEEEE;
font-size: 0.8em;
}
.toc {
line-height:1.35em;
}
.toc .chapter, .toc .appendix, .toc .glossary {
margin-top:1em;
}
.toc .part {
margin-top:1em;
display:block;
}
span.appendix, span.glossary {
display:block;
margin-top:0.5em;
}
div {
padding-top:0px;
}
div.section {
padding-top:1em;
}
p {
padding-top:0px;
margin-top:0.3em;
padding-bottom:0px;
margin-bottom:1em;
}
/*Links*/
a:link {
text-decoration:none;
border-bottom: 1px dotted ;
color:#3366cc;
}
a:visited {
text-decoration:none;
border-bottom: 1px dotted ;
color:#003366;
}
div.longdesc-link {
float:right;
color:#999;
}
.toc a {
font-weight:normal;
}
/*headings*/
h1, h2, h3, h4, h5, h6 {
color: #336699;
margin-top: 0em;
margin-bottom: 0em;
background-color: transparent;
}
h1 {
font-size:2.0em;
}
.titlepage h1.title {
font-size: 3.0em;
padding-top: 1em;
text-align:left;
}
.book > .titlepage h1.title {
text-align:center;
}
.article > .titlepage h1.title {
text-align:center;
}
.producttitle {
margin-top: 0em;
margin-bottom: 0em;
font-size: 3.0em;
font-weight: bold;
background: #336699 url(../images/h1-bg.png) top left repeat;
color: white;
text-align: center;
padding: 0.7em;
}
.titlepage .corpauthor {
margin-top: 1em;
text-align: center;
}
.section h1.title {
font-size: 1.6em;
padding: 0em;
color: #336699;
text-align: left;
background: white;
}
h2 {
font-size:1.6em;
}
h2.subtitle, h3.subtitle {
margin-top: 1em;
margin-bottom: 1em;
font-size: 1.4em;
text-align: center;
}
.preface > div > div > div > h2.title {
margin-top: 1em;
font-size: 2.0em;
}
.appendix h2 {
margin-top: 1em;
font-size: 2.0em;
}
h3 {
font-size:1.3em;
padding-top:0em;
padding-bottom:0em;
}
h4 {
font-size:1.1em;
padding-top:0em;
padding-bottom:0em;
}
h5 {
font-size:1em;
}
h6 {
font-size:1em;
}
h5.formalpara {
font-size:1em;
margin-top:2em;
margin-bottom:.8em;
}
.abstract h6 {
margin-top:1em;
margin-bottom:.5em;
font-size:2em;
}
/*element rules*/
hr {
border-collapse: collapse;
border-style:none;
border-top: 1px dotted #ccc;
width:100%;
margin-top: 3em;
}
sup {
color:#999;
}
/* web site rules */
ul.languages, .languages li {
display:inline;
padding:0em;
}
.languages li a {
padding:0em .5em;
text-decoration: none;
}
.languages li p {
display:inline;
}
.languages li a:link, .languages li a:visited {
color:#444;
}
.languages li a:hover, .languages li a:focus, .languages li a:active {
color:black;
}
ul.languages {
display:block;
background-color:#eee;
padding:.5em;
}
/*supporting stylesheets*/
/*unique to the webpage only*/
.article ul {
margin:0em;
padding-left:2em;
}
.article li {
margin:0em;
padding-left:0em;
list-style: disc;
}
.books {
position:relative;
}
.versions li {
width:100%;
clear:both;
display:block;
}
a.version {
font-size:2em;
text-decoration:none;
width:100%;
display:block;
padding:1em 0em .2em 0em;
clear:both;
}
a.version:before {
content:"Version";
font-size:smaller;
}
a.version:visited, a.version:link {
color:#666;
}
a.version:focus, a.version:hover {
color:black;
}
.books {
display:block;
position:relative;
clear:both;
width:100%;
}
.books li {
display:block;
width:200px;
float:left;
position:relative;
clear: none ;
}
.books .html {
width:170px;
display:block;
}
.books .pdf {
position:absolute;
left:170px;
top:0px;
font-size:smaller;
}
.books .pdf:link, .books .pdf:visited {
color:#555;
}
.books .pdf:hover, .books .pdf:focus {
color:#000;
}
.books li a {
text-decoration:none;
}
.books li a:hover {
color:black;
}
/*products*/
.products li {
display: block;
width:300px;
float:left;
}
.products li a {
width:300px;
padding:.5em 0em;
}
.products ul {
clear:both;
}
/*revision history*/
.revhistory {
display:block;
}
.revhistory table {
background-color:transparent;
border-color:#fff;
padding:0em;
margin: 0;
border-collapse:collapse;
border-style:none;
}
.revhistory td {
text-align:right;
padding:0em;
border-top: 1px solid #fff;
}
.revhistory tr td:first-child {
text-align:left;
}
.revhistory tr td p {
text-align:left;
font-weight:bold;
display:block;
margin:0em;
padding:0em;
padding-bottom:0.7em;
border-bottom:1px solid #eee;
}
.revhistory table th {
background-color:transparent;
color:#336699;
font-size:2em;
padding: 1em 0em;
border-bottom:1px solid #eee;
}
/*credits*/
.authorgroup div {
clear:both;
text-align: center;
}
h3.author {
margin: 0em;
padding: 0em;
padding-top: 1em;
}
.authorgroup h4 {
padding: 0em;
margin: 0em;
padding-top: 1em;
}
.author,
.editor,
.translator,
.othercredit {
display:block;
}
.othercredit h3 {
padding-top:1em;
}
.othercredit {
margin:0em;
padding:0em;
}
.releaseinfo {
clear: both;
}
.copyright {
margin-top: 1em;
}
/* qanda sets */
.answer {
padding-bottom:1em;
border-bottom:1px dotted #ccc;
}
.qandaset .toc {
border-bottom:1px dotted #ccc;
}
.question {
font-weight:bold;
}
.answer .data, .question .data {
padding-left: 2.6em;
}
.answer label, .question label {
float:left;
font-weight:bold;
}
.package {
font-style:italic;
}
/* inline syntax highlighting */
.hl-keyword {
color: #002F5D;
}
.hl-string {
color: #00774B;
}
.hl-comment {
color: #FF00FF;
}
.hl-tag {
color: #002F5D;
}
.hl-attribute {
color: #a70000;
}
.hl-value {
color: #4E376B;
}
.hl-html {
color:#002F5D;
}
.hl-xslt {
color: #00774B;
}
.hl-section {
color: #00774B;
}
.hl-directive {
color: #002F5D;
}
.hl-doctype {
color: #002F5D;
}
/*Lists*/
ul {
padding-left:1.6em;
list-style-image:url(../images/dot.png);
list-style-type: circle;
}
ul ul {
list-style-image:url(../images/dot2.png);
list-style-type: circle;
}
ol {
list-style-image:none;
list-style-type: decimal;
}
ol.loweralpha {
list-style-type: lower-alpha;
}
ol.lowerroman {
list-style-type: lower-roman;
}
ol.upperalpha {
list-style-type: upper-alpha;
}
ol.upperroman {
list-style-type: upper-roman;
}
dt {
font-weight:bold;
margin-bottom:0em;
padding-bottom:0em;
}
dd {
margin:0em;
margin-left:2em;
padding-top:0em;
}
li {
padding-top:0px;
margin-top:0em;
padding-bottom:0px;
margin-bottom:0.4em;
}
li p {
padding-top:0px;
margin-top:0em;
padding-bottom:0px;
margin-bottom:0.3em;
}
/*images*/
img {
display:block;
margin:2em 0;
}
.inlinemediaobject, .inlinemediaobject img {
display:inline;
margin:0em;
}
.figure img {
display:block;
margin:0;
}
.figure .title {
margin:0em;
margin-bottom:2em;
padding:0px;
}
/*document modes*/
.confidential {
background-color:#900;
color:White;
padding:.5em .5em;
text-transform:uppercase;
text-align:center;
}
.longdesc-link {
display:none;
}
.longdesc {
display:none;
}
.prompt {
background-color:#ede7c8;
padding:0em .3em;
}
/*user interface styles*/
.screen .replaceable {
color:#444;
}
pre, code, .guibutton, .keycap, .guilabel {
font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
}
.guibutton, .keycap, .guilabel {
font-weight:bold;
white-space:nowrap;
}
.example {
background-color:#dc9f2e;
padding:5px;
margin-bottom:10px;
}
/*terminal/console text*/
.computeroutput,
.citetitle,
.replaceable,
.option {
font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
}
.replaceable {
font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
font-style: italic;
}
.command, .filename, .keycap, .classname, .literal {
font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
font-weight:bold;
}
pre {
font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
display:block;
background-color:#eeeeee;
margin-bottom: 0.3em;
padding:.5em 1em;
white-space: pre-wrap; /* css-3 */
white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
white-space: -pre-wrap; /* Opera 4-6 */
white-space: -o-pre-wrap; /* Opera 7 */
word-wrap: break-word; /* Internet Explorer 5.5+ */
}
pre .replaceable,
pre .keycap {
color:white;
}
code {
white-space: nowrap;
}
/*Notifications*/
div.note, div.important, div.warning {
padding:1em;
padding-bottom:20px;
margin-top:.5em;
margin-bottom:1.5em;
background-repeat:no-repeat;
background-position:1em 1em;
}
div.note pre, div.important pre, div.warning pre {
background-color:#333;
color:white;
}
div.note {
background-image:url(../images/note.png);
background-color:#8e9f00;
color:white;
}
div.important {
background-color:#d08e13;
color:white;
background-image:url(../images/important.png);
}
div.warning {
background-color:#9e292b;
color:white;
background-image:url(../images/warning.png);
}
/* Admonition Headings */
div.note h2, div.important h2, div.warning h2 {
height:32px;
font-size:1.3em;
}
div.note h2, div.important h2, div.warning h2 {
color:white;
}
/* Admonition Inlines */
div.note .replaceable, div.important .replaceable, div.warning .replaceable {
color:#e3dcc0;
}
pre .replaceable, tt .replaceable {
color:#444;
}
div.note .guilabel, div.important .guilabel, div.warning .guilabel {
color:#e3dcc0;
}
/* Admonition Lists ... really? */
div.note li, div.warning li, div.important li {
padding-left:10px;
margin:0em;
}
div.note ul, div.warning ul, div.important ul {
padding-left:40px;
margin:0em;
}
/* Admonition links in verbatim ... *really* */
div.note pre pre a:visited, div.important pre pre a:visited,
div.warning pre pre a:visited, div.note pre a:link, div.important pre a:link, div.warning pre a:link {
color:#0066cc;
}
/* Admonition links */
div.note a:visited, div.important a:visited, div.warning a:visited, div.note a:link , div.important a:link , div.warning a:link {
color:#f7f2d0;
}
/*notification icons*/
div.note h2, div.note p, div.warning h2, div.warning p, div.important h2, .important p {
padding:0em;
margin:0em;
padding-left:56px;
}
/*Page Title*/
#title strong {
display:none;
}
#title a {
border:none;
display:block;
height:45px;
width:110px;
padding-left:200px;
background:transparent url(../images/image_left.png) top left no-repeat;
}
#title {
display:block;
height:45px;
background:transparent url(../images/image_right.png) top right no-repeat;
padding-bottom:1em;
}
/*Table*/
table {
border:1px solid #6c614b;
width:100%;
border-collapse:collapse;
}
table th {
text-align:left;
background-color:#6699cc;
padding:.3em .5em;
color:white;
}
table td {
padding:.15em .5em;
}
table tr.even td {
background-color:#f5f5f5;
}
table th p:first-child, table td p:first-child, table li p:first-child {
margin-top:0em;
padding-top:0em;
display:inline;
}
th, td {
border-style:none;
vertical-align: top;
}
table table td {
border-bottom:1px dotted #aaa;
background-color:white;
padding:.6em 0em;
}
table table {
border:1px solid white;
}
td.remarkval {
color:#444;
}
td.fieldval {
font-weight:bold;
}
.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
color:white;
font-weight:bold;
background-color:#999;
width:120px;
}
td.remarkval {
width:230px;
}
td.tname {
font-weight:bold;
}
th.dbfield {
width:120px;
}
th.dbtype {
width:70px;
}
th.dbdefault {
width:70px;
}
th.dbnul {
width:70px;
}
th.dbkey {
width:70px;
}
span.book {
margin-top:4em;
display:block;
}
span.chapter {
display:block;
margin-top:0.5em;
}
/*Breadcrumbs*/
#breadcrumbs ul li.first:before {
content:" ";
}
#breadcrumbs {
color:#900;
padding:3px;
margin-bottom:25px;
}
#breadcrumbs ul {
margin-left:0;
padding-left:0;
display:inline;
border:none;
}
#breadcrumbs ul li {
margin-left:0;
padding-left:2px;
border:none;
list-style:none;
display:inline;
}
#breadcrumbs ul li:before {
content:"\0020 \0020 \0020 \00BB \0020";
color:#333;
}
/*status*/
.alpha1 {
background: white url(../images/watermark-alpha1.png) top left repeat;
}
.alpha2 {
background: white url(../images/watermark-alpha2.png) top left repeat;
}
.beta1 {
background: white url(../images/watermark-beta1.png) top left repeat;
}
.beta2 {
background: white url(../images/watermark-beta2.png) top left repeat;
}
.pre-release-candidate {
background: white url(../images/watermark-pre-release-candidate.png) top left repeat;
}
.release-candidate {
background: white url(../images/watermark-release-candidate.png) top left repeat;
}
/*index*/
.glossary h3,
.index h3 {
font-size: 2em;
color:#aaa;
margin:0em;
}
.indexdiv {
margin-bottom:1em;
}
.glossary dt, .index dt {
color:#444;
padding-top:.5em;
}
.glossary dl dl dt,
.index dl dl dt {
color:#777;
font-weight:normal;
padding-top:0em;
}
.index dl dl dt:before {
content:"- ";
color:#ccc;
}
/*changes*/
.footnote {
padding:.2em 1em;
background-color:#c8c5ac;
font-size: .7em;
margin:0em;
margin-bottom:.5em;
color:#222;
}
table .footnote {
margin:1em .5em;
}
sup {
padding:0em .3em;
padding-left:0em;
}
.footnote {
position:relative;
}
.footnote sup {
color:#e3dcc0;
position:absolute;
left: .4em;
}
.footnote sup a:link,
.footnote sup a:visited {
color:#92917d;
text-decoration:none;
}
.footnote:hover sup a {
color:#fff;
text-decoration:none;
}
.footnote p {
padding-left:5em;
}
.footnote a:link,
.footnote a:visited {
color:#00537c;
}
.footnote a:hover {
color:white;
}
/**/
div.chapter {
margin-top:3em;
}
div.section {
margin-top:1em;
}
div.note .replaceable,
div.important .replaceable,
div.warning .replaceable,
div.note .keycap,
div.important .keycap,
div.warning .keycap
{
color:white;
}
.authorgroup h4 {
padding:0em;
margin:0em;
margin-top:1em;
}
.author, .editor, .translator, .othercredit {
display:block;
}
ul li p:last-child {
margin-bottom:0em;
padding-bottom:0em;
}
/*document navigation*/
.docnav a, .docnav strong {
border:none;
text-decoration:none;
font-weight:normal;
}
.docnav {
list-style:none;
margin:0em;
padding:0em;
position:relative;
width:100%;
padding-bottom:2em;
padding-top:1em;
border-top:1px dotted #ccc;
}
.docnav li {
list-style:none;
margin:0em;
padding:0em;
display:inline;
font-size:.8em;
}
.docnav li:before {
content:" ";
}
.docnav li.previous, .docnav li.next {
position:absolute;
top:1em;
}
.docnav li.up, .docnav li.home {
margin:0em 1.5em;
}
.docnav li.previous {
left:0px;
text-align:left;
}
.docnav li.next {
right:0px;
text-align:right;
}
.docnav li.previous strong, .docnav li.next strong {
display:block;
height:22px;
}
.docnav {
margin:0 auto;
text-align:center;
}
.docnav li.next a strong {
background: url(../images/stock-go-forward.png) top right no-repeat;
padding-top:3px;
padding-right:28px;
font-size:1.2em;
}
.docnav li.previous a strong {
background: url(../images/stock-go-back.png) top left no-repeat;
padding-top:3px;
padding-left:28px;
font-size:1.2em;
}
.docnav li.home a strong {
background: url(../images/stock-home.png) top left no-repeat;
padding:5px;
padding-left:28px;
font-size:1.2em;
}
.docnav li.up a strong {
background: url(../images/stock-go-up.png) top left no-repeat;
padding:5px;
padding-left:28px;
font-size:1.2em;
}
.docnav a:link, .docnav a:visited {
color:#666;
}
.docnav a:hover, .docnav a:focus, .docnav a:active {
color:black;
}
.docnav a {
max-width: 10em;
overflow:hidden;
}
.docnav a:link strong {
text-decoration:none;
}
.docnav {
margin:0 auto;
text-align:center;
}
ul.docnav {
margin-bottom: 1em;
}
/* Reports */
.reports ul {
list-style:none;
margin:0em;
padding:0em;
}
.reports li{
margin:0em;
padding:0em;
}
.reports li.odd {
background-color: #eeeeee;
margin:0em;
padding:0em;
}
.reports dl {
display:inline;
margin:0em;
padding:0em;
float:right;
margin-right: 17em;
margin-top:-1.3em;
}
.reports dt {
display:inline;
margin:0em;
padding:0em;
}
.reports dd {
display:inline;
margin:0em;
padding:0em;
padding-right:.5em;
}
.reports h2, .reports h3{
display:inline;
padding-right:.5em;
font-size:10pt;
font-weight:normal;
}
.reports div.progress {
display:inline;
float:right;
width:16em;
background:#c00 url(../images/shine.png) top left repeat-x;
margin:0em;
margin-top:-1.3em;
padding:0em;
border:none;
}
/*uniform*/
body.results, body.reports {
max-width:57em ;
padding:0em;
}
/*Progress Bar*/
div.progress {
display:block;
float:left;
width:16em;
background:#c00 url(../images/shine.png) top left repeat-x;
height:1em;
}
div.progress span {
height:1em;
float:left;
}
div.progress span.translated {
background:#6c3 url(../images/shine.png) top left repeat-x;
}
div.progress span.fuzzy {
background:#ff9f00 url(../images/shine.png) top left repeat-x;
}
/*Results*/
.results ul {
list-style:none;
margin:0em;
padding:0em;
}
.results li{
margin:0em;
padding:0em;
}
.results li.odd {
background-color: #eeeeee;
margin:0em;
padding:0em;
}
.results dl {
display:inline;
margin:0em;
padding:0em;
float:right;
margin-right: 17em;
margin-top:-1.3em;
}
.results dt {
display:inline;
margin:0em;
padding:0em;
}
.results dd {
display:inline;
margin:0em;
padding:0em;
padding-right:.5em;
}
.results h2, .results h3{
display:inline;
padding-right:.5em;
font-size:10pt;
font-weight:normal;
}
.results div.progress {
display:inline;
float:right;
width:16em;
background:#c00 url(../images/shine.png) top left repeat-x;
margin:0em;
margin-top:-1.3em;
padding:0em;
border:none;
}
/* Dirty EVIL Mozilla hack for round corners */
pre {
-moz-border-radius:11px;
}
.example {
-moz-border-radius:15px;
}
.term{
color:#336699;
}
.package {
font-style: italic;
}
.edition {
color: #336699;
background-color: transparent;
margin-top: 1em;
margin-bottom: 1em;
font-size: 1.4em;
font-weight: bold;
text-align: center;
}
span.remark{
background-color: #ffff00;
}
--- NEW FILE default.css ---
@import url("common.css");
@import url("overrides.css");
--- NEW FILE overrides.css ---
a:link {
color:#0066cc;
}
a:hover, a:active {
color:#003366;
}
a:visited {
color:#6699cc;
}
h1 {
color:#3c6eb4
}
.producttitle {
background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
}
.section h1.title {
color:#3c6eb4;
}
h2,h3,h4,h5,h6 {
color:#3c6eb4;
}
table {
border:1px solid #3c6eb4;
}
table th {
background-color:#3c6eb4;
}
table tr.even td {
background-color:#f5f5f5;
}
.term{
color:#3c6eb4
}
.revhistory table th {
color:#3c6eb4;
}
.edition {
color: #3c6eb4;
}
From sparks at fedoraproject.org Mon Dec 22 19:10:01 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 19:10:01 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/images
FirefoxWithKerberosSSO.png,
NONE, 1.1 SCLogin.png, NONE, 1.1 SCLoginEnrollment.png, NONE,
1.1 auth-panel.png, NONE, 1.1 authicon.png, NONE,
1.1 n-t-n-ipsec-diagram.png, NONE, 1.1 n-to-n-ipsec-local.png,
NONE, 1.1 n-to-n-ipsec-remote.png, NONE,
1.1 rh-securitylevel.png, NONE, 1.1 sec-ipsec-host2host.png,
NONE, 1.1 serv-config.png, NONE, 1.1 tcp_wrap_diagram.png, NONE,
1.1 user_pass_groups.png, NONE, 1.1 user_pass_info.png, NONE, 1.1
Message-ID: <20081222191001.CA6AF70130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/images
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv4312/images
Added Files:
FirefoxWithKerberosSSO.png SCLogin.png SCLoginEnrollment.png
auth-panel.png authicon.png n-t-n-ipsec-diagram.png
n-to-n-ipsec-local.png n-to-n-ipsec-remote.png
rh-securitylevel.png sec-ipsec-host2host.png serv-config.png
tcp_wrap_diagram.png user_pass_groups.png user_pass_info.png
Log Message:
Adding Common_Content and image directories
From sparks at fedoraproject.org Mon Dec 22 19:10:01 2008
From: sparks at fedoraproject.org (Eric Christensen)
Date: Mon, 22 Dec 2008 19:10:01 +0000 (UTC)
Subject: web/html/docs/security-guide/en_US/Common_Content/images 1.png, NONE,
1.1 1.svg, NONE, 1.1 10.png, NONE, 1.1 10.svg, NONE, 1.1 11.png,
NONE, 1.1 11.svg, NONE, 1.1 12.png, NONE, 1.1 12.svg, NONE,
1.1 13.png, NONE, 1.1 13.svg, NONE, 1.1 14.png, NONE, 1.1 14.svg,
NONE, 1.1 15.png, NONE, 1.1 15.svg, NONE, 1.1 16.png, NONE,
1.1 16.svg, NONE, 1.1 17.png, NONE, 1.1 17.svg, NONE, 1.1 18.png,
NONE, 1.1 18.svg, NONE, 1.1 19.png, NONE, 1.1 19.svg, NONE,
1.1 2.png, NONE, 1.1 2.svg, NONE, 1.1 20.png, NONE, 1.1 20.svg,
NONE, 1.1 21.png, NONE, 1.1 21.svg, NONE, 1.1 22.png, NONE,
1.1 22.svg, NONE, 1.1 23.png, NONE, 1.1 23.svg, NONE, 1.1 3.png,
NONE, 1.1 3.svg, NONE, 1.1 4.png, NONE, 1.1 4.svg, NONE,
1.1 5.png, NONE, 1.1 5.svg, NONE, 1.1 6.png, NONE, 1.1 6.svg,
NONE, 1.1 7.png, NONE, 1.1 7.svg, NONE, 1.1 8.png, NONE,
1.1 8.svg, NONE, 1.1 9.png, NONE, 1.1 9.svg, NONE,
1.1 background.png, NONE, 1.1 bkgrnd_greydots.png, NONE,
1.1 bullet_arrowblue.png, NONE, 1.1 documentation.png, NONE,
1.1 dot.png, NONE, 1.1 dot2.png, NONE, 1.1 h1-bg.png, NONE,
1.1 image_left.png, NONE, 1.1 image_right.png, NONE,
1.1 important.png, NONE, 1.1 important.svg, NONE, 1.1 key.png,
NONE, 1.1 logo.png, NONE, 1.1 note.png, NONE, 1.1 note.svg, NONE,
1.1 shade.png, NONE, 1.1 stock-go-back.png, NONE,
1.1 stock-go-forward.png, NONE, 1.1 stock-go-up.png, NONE,
1.1 stock-home.png, NONE, 1.1 title_logo.png, NONE,
1.1 title_logo.svg, NONE, 1.1 warning.png, NONE, 1.1 warning.svg,
NONE, 1.1 watermark-alpha1.png, NONE, 1.1 watermark-alpha2.png,
NONE, 1.1 watermark-beta1.png, NONE, 1.1 watermark-beta2.png,
NONE, 1.1 watermark-blank.png, NONE,
1.1 watermark-pre-release-candidate.png, NONE,
1.1 watermark-release-candidate.png, NONE, 1.1
Message-ID: <20081222191001.721C370130@cvs1.fedora.phx.redhat.com>
Author: sparks
Update of /cvs/fedora/web/html/docs/security-guide/en_US/Common_Content/images
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv4312/Common_Content/images
Added Files:
1.png 1.svg 10.png 10.svg 11.png 11.svg 12.png 12.svg 13.png
13.svg 14.png 14.svg 15.png 15.svg 16.png 16.svg 17.png 17.svg
18.png 18.svg 19.png 19.svg 2.png 2.svg 20.png 20.svg 21.png
21.svg 22.png 22.svg 23.png 23.svg 3.png 3.svg 4.png 4.svg
5.png 5.svg 6.png 6.svg 7.png 7.svg 8.png 8.svg 9.png 9.svg
background.png bkgrnd_greydots.png bullet_arrowblue.png
documentation.png dot.png dot2.png h1-bg.png image_left.png
image_right.png important.png important.svg key.png logo.png
note.png note.svg shade.png stock-go-back.png
stock-go-forward.png stock-go-up.png stock-home.png
title_logo.png title_logo.svg warning.png warning.svg
watermark-alpha1.png watermark-alpha2.png watermark-beta1.png
watermark-beta2.png watermark-blank.png
watermark-pre-release-candidate.png
watermark-release-candidate.png
Log Message:
Adding Common_Content and image directories
--- NEW FILE 1.svg ---
--- NEW FILE 10.svg ---
--- NEW FILE 11.svg ---
--- NEW FILE 12.svg ---
--- NEW FILE 13.svg ---
--- NEW FILE 14.svg ---
--- NEW FILE 15.svg ---
--- NEW FILE 16.svg ---
--- NEW FILE 17.svg ---
--- NEW FILE 18.svg ---
--- NEW FILE 19.svg ---
--- NEW FILE 2.svg ---
--- NEW FILE 20.svg ---
--- NEW FILE 21.svg ---
--- NEW FILE 22.svg ---
--- NEW FILE 23.svg ---
--- NEW FILE 3.svg ---
--- NEW FILE 4.svg ---
--- NEW FILE 5.svg ---
--- NEW FILE 6.svg ---
--- NEW FILE 7.svg ---
--- NEW FILE 8.svg ---
--- NEW FILE 9.svg ---
--- NEW FILE important.svg ---
--- NEW FILE note.svg ---
--- NEW FILE title_logo.svg ---
--- NEW FILE warning.svg ---
From stickster at gmail.com Tue Dec 23 21:09:15 2008
From: stickster at gmail.com (Paul W. Frields)
Date: Tue, 23 Dec 2008 16:09:15 -0500
Subject: Schedule hackfest
Message-ID: <20081223210915.GA4736@localhost.localdomain>
Hello Artwork, Docs, L10n, Marketing, and Websites teams!
First, I hope you all have a happy holiday season, and enjoy some time
with friends, family, and loved ones. We've had a really big year in
Fedora and I am so incredibly proud to have worked with all of you
each day. We've pushed out two incredibly great releases of Fedora
this year, Fedora 9 and 10, each stronger than the one before.
As we are now deeply into the Fedora 11 development cycle, I've been
thinking we really all want to know the various team interdependencies
before we get to the Alpha phase of the release. If one team has a
particular deadline, and that requires input from some other team to
complete, we want to know that. In the best possible world, each team
will be producing what its partner needs in plenty of time for that
partner team to work effectively, and so on down the line.
We've had release day planning meetings over the last couple of
releases which have helped, I think, quite a bit to ensure people have
what they need from other groups. We have an opportunity to make this
process work even more smoothly, and driven more by each team, if we
can figure out the very broad tasks that each team has to complete for
a release, and map them out on the release schedule.
Some of the teams receiving this message have done preliminary (or
maybe even more) work on the schedule already, which is fantastic. I
think FUDCon gives us a chance to bring together people from most of
your teams to flesh that work out where it's helpful. I don't believe
we need to "finish" the schedule, and that might be a hazy goal
anyway. We'll probably end up finding places where we can refine it
after this release to do even better for Fedora 12. But each
iteration brings us something that we can use to help releases go more
smoothly.
Many of us are volunteers, and we all still want to know, first and
foremost, that our work is important, and valued in Fedora. The work
we do is far more important than simply hitting a date on a calendar.
But we also all want to know that we are helping our fellow community
members, and that each of us is doing our best to help Fedora move
forward as a project.
I've asked John Poelstra to help me put together a hackfest at FUDCon
Boston 2009, bringing together people from each of your teams to talk
through these interdependencies and record them. The result, I
believe, will make each succeeding release easier, more efficient, and
more enjoyable.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
From marcferguson at gmail.com Wed Dec 24 19:36:23 2008
From: marcferguson at gmail.com (Marc Ferguson)
Date: Wed, 24 Dec 2008 14:36:23 -0500
Subject: Looking for Ideas on a User-friendly Join Process
Message-ID:
Hi,
My name is Marc Ferguson. I recently joined the websites group for Fedora
Project and I've been assigned to help figure out a very universal and
user-friendly way to tweak http://fedoraproject.org/en/join-fedora. Can you
please respond to this thread and let us know what your process is for
people to join your group. In the end we want to make sure we're all "on
the same page" and that the joining process is much easier, thus increasing
the contributors to the project. Thanks.
--
*Marc F.*
www.fergytech.com
"..Grace to you and peace from Him who is and who was and who is to come.."
-Rev1:4
"When life gives me lemons... I make Linuxaide!" -Marc F.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From marcferguson at gmail.com Wed Dec 24 20:37:10 2008
From: marcferguson at gmail.com (Marc Ferguson)
Date: Wed, 24 Dec 2008 15:37:10 -0500
Subject: Self Introduction
In-Reply-To: <20081222191613.GC23943@sphe>
References:
<20081222191613.GC23943@sphe>
Message-ID:
Welcome Jeff. I'm new as well and I need to send out an intro email too.
Funny story, it was actually your "self introduction" email that key'd me
into the online meeting that was taking place 20 minutes before I joined.
So thanks Jeff. I always wanted to join an open source project, but never
took the first step. Now I'm a part of the websites group.
2008/12/22 Ricky Zhou
> On 2008-12-15 11:34:04 PM, Jeffrey Ravenhorst wrote:
> > My name is Jeffrey Ravenhorst, and i'm interested in contributing to the
> fedora
> > websites project.
> >
> > I've been doing web programming/design for about 6 years now (i guess
> that's
> > not a really long time, but i'm only 21), and its pretty much my favorite
> thing
> > to do as far as computing goes. I'm currently a senior at Longwood
> University
> > in virginia, usa, working on a BS in computer science (they really don't
> do
> > much web stuff there, but i do a lot on my own and for work). Anyways, i
> hope i
> > can help out... here are some of the things i consider myself useful for:
> Hey, welcome! We have weekly meetings on Mondays (although we've missed
> a few this month), so if you can make it, we have one in about 45
> minutes in #fedora-meeting on irc.freenode.net.
>
> Hopefully we'll be able to work out some tasks for people to work on in
> the meeting.
>
> Thanks,
> Ricky
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
>
>
--
Marc F.
www.fergytech.com
"..Grace to you and peace from Him who is and who was and who is to come.."
-Rev1:4
"When life gives me lemons... I make Linuxaide!" -Marc F.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From D.J.Woodbridge at lse.ac.uk Tue Dec 23 18:21:00 2008
From: D.J.Woodbridge at lse.ac.uk (D.J.Woodbridge at lse.ac.uk)
Date: Tue, 23 Dec 2008 18:21:00 -0000
Subject: (no subject)
Message-ID:
the main fedora download doesn't work, my browser keeps timing out, if you could fix it that'd be great
Please access the attached hyperlink for an important electronic communications disclaimer: http://www.lse.ac.uk/collections/secretariat/legal/disclaimer.htm
From danstalls at gmail.com Fri Dec 26 14:52:40 2008
From: danstalls at gmail.com (Dan Adams)
Date: Fri, 26 Dec 2008 07:52:40 -0700
Subject: feedback
Message-ID: <95f9f4950812260652o7ccfc03l729b97c319b8b9c9@mail.gmail.com>
I have read in no less than 5 places on your website how much feedback is
valued, yet I have found the feedback process cryptic and frustrating. All I
wanted to do was provide a little feedback before uninstalling fedora, not
join a club or create the one thousandth password that will never be used
again. Nor read endless pages of someone else's opinions. I just wanted to
pass on a comment that I though might be of some use to developers. If your
developers truly want honest feedback then perhaps you might suggest to them
that they create a conduit for that purpose that does not require all of the
BS.
--
Thanks,
Dan Adams.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ricky at fedoraproject.org Mon Dec 29 09:19:44 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 04:19:44 -0500
Subject: feedback
In-Reply-To: <95f9f4950812260652o7ccfc03l729b97c319b8b9c9@mail.gmail.com>
References: <95f9f4950812260652o7ccfc03l729b97c319b8b9c9@mail.gmail.com>
Message-ID: <20081229091944.GA6975@sphe.fedora.phx.redhat.com>
On 2008-12-26 07:52:40 AM, Dan Adams wrote:
> I have read in no less than 5 places on your website how much feedback is
> valued, yet I have found the feedback process cryptic and frustrating. All I
> wanted to do was provide a little feedback before uninstalling fedora, not join
> a club or create the one thousandth password that will never be used again. Nor
> read endless pages of someone else's opinions. I just wanted to pass on a
> comment that I though might be of some use to developers. If your developers
> truly want honest feedback then perhaps you might suggest to them that they
> create a conduit for that purpose that does not require all of the BS.
If you click on the "Communicate" link on the left sidebar (subtitled
"Speak with Fedora") on http://fedoraproject.org/, you are taken to
http://fedoraproject.org/wiki/Communicate, which has a section for this,
"Provide Feedback to Developers." In that section, we include
information about our bugzilla and various mailing lists where your
feedback would be appropriate.
If you had trouble finding the exact section, here is a link to it:
http://fedoraproject.org/wiki/Communicate#Providing_Feedback_to_Developers
We welcome any suggestions on how to make this information clearer to
website visitors.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From sundaram at fedoraproject.org Mon Dec 29 09:31:32 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 29 Dec 2008 15:01:32 +0530
Subject: Join Fedora
Message-ID: <495898F4.8040905@fedoraproject.org>
Hi,
Apparently the "OS Developer" icon in join Fedora page doesn't translate
well into "testing" or "maintaining packages" for many people. There was
a brief discussion in fedora-devel list starting at
https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02553.html
To summarize, maybe "Fedora Developer", "Developer" or "Developing/
Testing" or individual icons for these that point to the same section
might be better.
Rahul
From ricky at fedoraproject.org Mon Dec 29 09:36:47 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 04:36:47 -0500
Subject: Join Fedora
In-Reply-To: <495898F4.8040905@fedoraproject.org>
References: <495898F4.8040905@fedoraproject.org>
Message-ID: <20081229093647.GB6975@sphe.fedora.phx.redhat.com>
On 2008-12-29 03:01:32 PM, Rahul Sundaram wrote:
> Apparently the "OS Developer" icon in join Fedora page doesn't translate
> well into "testing" or "maintaining packages" for many people. There was
> a brief discussion in fedora-devel list starting at
>
> https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02553.html
>
> To summarize, maybe "Fedora Developer", "Developer" or "Developing/
> Testing" or individual icons for these that point to the same section
> might be better.
Thanks for passing this one - we actually discussed this at our last
meeting, and Marc Ferguson sent out a couple of emails asking for
feedback for our join page. It has been pretty quiet for now (holidays,
I guess), but our next big goal for this release is to improve our
join-fedora page (much like we improved get-fedora last time).
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 29 09:41:28 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 04:41:28 -0500
Subject: Websites Meeting?
Message-ID: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
Hey, I know a lot of people are are enjoying the winter holidays, so I
thought I'd check first - can most people make a meeting at 22:00 UTC
today?
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From sundaram at fedoraproject.org Mon Dec 29 09:41:50 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 29 Dec 2008 15:11:50 +0530
Subject: Join Fedora
In-Reply-To: <20081229093647.GB6975@sphe.fedora.phx.redhat.com>
References: <495898F4.8040905@fedoraproject.org>
<20081229093647.GB6975@sphe.fedora.phx.redhat.com>
Message-ID: <49589B5E.8080301@fedoraproject.org>
Ricky Zhou wrote:
> On 2008-12-29 03:01:32 PM, Rahul Sundaram wrote:
>> Apparently the "OS Developer" icon in join Fedora page doesn't translate
>> well into "testing" or "maintaining packages" for many people. There was
>> a brief discussion in fedora-devel list starting at
>>
>> https://www.redhat.com/archives/fedora-devel-list/2008-December/msg02553.html
>>
>> To summarize, maybe "Fedora Developer", "Developer" or "Developing/
>> Testing" or individual icons for these that point to the same section
>> might be better.
> Thanks for passing this one - we actually discussed this at our last
> meeting, and Marc Ferguson sent out a couple of emails asking for
> feedback for our join page. It has been pretty quiet for now (holidays,
> I guess), but our next big goal for this release is to improve our
> join-fedora page (much like we improved get-fedora last time).
Sorry, I am not following meeting notes much these days.
Does the goal include improving http://spins.fedoraproject.org?
Personally, I would put that as a higher priority than join page. We
have a increasingly large number of spins and the traffic directed
towards them has clearly gone down with the new Get Fedora page because
the spins are more or less invisible for the large majority of users.
Rahul
From ricky at fedoraproject.org Mon Dec 29 09:43:33 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 04:43:33 -0500
Subject: (no subject)
In-Reply-To:
References:
Message-ID: <20081229094333.GD6975@sphe.fedora.phx.redhat.com>
On 2008-12-23 06:21:00 PM, D.J.Woodbridge at lse.ac.uk wrote:
> the main fedora download doesn't work, my browser keeps timing out, if
> you could fix it that'd be great
It's possible that a mirror is having problems. Could you tell us
exactly what link you clicked, and what mirror you got redirected to?
(The link should be http://download.fedoraproject.org/..., which
redirects you to a nearby mirror.)
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 29 09:50:23 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 04:50:23 -0500
Subject: Join Fedora
In-Reply-To: <49589B5E.8080301@fedoraproject.org>
References: <495898F4.8040905@fedoraproject.org>
<20081229093647.GB6975@sphe.fedora.phx.redhat.com>
<49589B5E.8080301@fedoraproject.org>
Message-ID: <20081229095023.GE6975@sphe.fedora.phx.redhat.com>
On 2008-12-29 03:11:50 PM, Rahul Sundaram wrote:
> Does the goal include improving http://spins.fedoraproject.org?
> Personally, I would put that as a higher priority than join page. We
> have a increasingly large number of spins and the traffic directed
> towards them has clearly gone down with the new Get Fedora page because
> the spins are more or less invisible for the large majority of users.
Not really - there was some planning work done for spins.fp.o at the
last FUDCon and a fedorahosted project was started for it, but it seems
to be blocking on the development work for a spins web app (as the spins
site was planned to be more complicated than just a set of static
pages).
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From sundaram at fedoraproject.org Mon Dec 29 09:55:41 2008
From: sundaram at fedoraproject.org (Rahul Sundaram)
Date: Mon, 29 Dec 2008 15:25:41 +0530
Subject: Join Fedora
In-Reply-To: <20081229095023.GE6975@sphe.fedora.phx.redhat.com>
References: <495898F4.8040905@fedoraproject.org> <20081229093647.GB6975@sphe.fedora.phx.redhat.com> <49589B5E.8080301@fedoraproject.org>
<20081229095023.GE6975@sphe.fedora.phx.redhat.com>
Message-ID: <49589E9D.4000103@fedoraproject.org>
Ricky Zhou wrote:
> On 2008-12-29 03:11:50 PM, Rahul Sundaram wrote:
>> Does the goal include improving http://spins.fedoraproject.org?
>> Personally, I would put that as a higher priority than join page. We
>> have a increasingly large number of spins and the traffic directed
>> towards them has clearly gone down with the new Get Fedora page because
>> the spins are more or less invisible for the large majority of users.
> Not really - there was some planning work done for spins.fp.o at the
> last FUDCon and a fedorahosted project was started for it, but it seems
> to be blocking on the development work for a spins web app (as the spins
> site was planned to be more complicated than just a set of static
> pages).
I think there is a FUDCon session planned on spins and if we are not
getting a web app by the end of it, a simple set of static pages might
be way better than what we have at this point.
Rahul
From onekopaka at gmail.com Mon Dec 29 09:58:21 2008
From: onekopaka at gmail.com (Darren VanBuren)
Date: Mon, 29 Dec 2008 01:58:21 -0800
Subject: Websites Meeting?
In-Reply-To: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
References: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
Message-ID: <98F197F7-ECBE-489D-A3D1-B3F971502EBD@gmail.com>
On Dec 29, 2008, at 1:41 AM, Ricky Zhou wrote:
> Hey, I know a lot of people are are enjoying the winter holidays, so I
> thought I'd check first - can most people make a meeting at 22:00 UTC
> today?
>
> Thanks,
> Ricky
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
As long as I don't have to go anywhere, yes.
Darren VanBuren
onekopaka at gmail.com
----------------------------------------------
Administrator of Onekopakaspace
Blog:
http://oks.kicks-ass.net/~onekopaka/blog/
Sweetcron install:
http://sweetcron.oks.kicks-ass.net/
PGP Key: 66F46296 (gpg --keyserver pgp.mit.edu --recv-keys 66F46296)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2421 bytes
Desc: not available
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL:
From marcferguson at gmail.com Mon Dec 29 16:07:22 2008
From: marcferguson at gmail.com (Marc Ferguson)
Date: Mon, 29 Dec 2008 11:07:22 -0500
Subject: Websites Meeting?
In-Reply-To: <98F197F7-ECBE-489D-A3D1-B3F971502EBD@gmail.com>
References: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
<98F197F7-ECBE-489D-A3D1-B3F971502EBD@gmail.com>
Message-ID:
2008/12/29 Darren VanBuren
>
> On Dec 29, 2008, at 1:41 AM, Ricky Zhou wrote:
>
> Hey, I know a lot of people are are enjoying the winter holidays, so I
> thought I'd check first - can most people make a meeting at 22:00 UTC
> today?
>
> Thanks,
> Ricky
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
>
>
> As long as I don't have to go anywhere, yes.
> Darren VanBuren
> onekopaka at gmail.com
> ----------------------------------------------
> Administrator of Onekopakaspace
>
> Blog:
> http://oks.kicks-ass.net/~onekopaka/blog/
>
> Sweetcron install:
> http://sweetcron.oks.kicks-ass.net/
>
> PGP Key: 66F46296 (gpg --keyserver pgp.mit.edu --recv-keys 66F46296)
>
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
>
>
I think 22:00 UTC is 15:00 EST. If so then I'll be able to make it. Ricky,
I had an item I wanted to put on the agenda, but I don't know how to do
that.
Some one blogged on Planet Fedora about the SHA1SUM files being 5 levels
deep on the site. I thought we could talk about that and just make it 2
levels by placing a link along with the other big blue blocks on the
right-hand side on the "get fedora" page.
--
*Marc F.*
www.fergytech.com
Registered Linux User: #410978
"When life gives me lemons... I make Linuxaide, hmm good stuff!" -Marc F.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ricky at fedoraproject.org Mon Dec 29 20:42:59 2008
From: ricky at fedoraproject.org ('Ricky Zhou')
Date: Mon, 29 Dec 2008 15:42:59 -0500
Subject: feedback
In-Reply-To: <000e01c969d3$ce852ce0$0601a8c0@mred>
References: <95f9f4950812260652o7ccfc03l729b97c319b8b9c9@mail.gmail.com>
<20081229091944.GA6975@sphe.fedora.phx.redhat.com>
<000e01c969d3$ce852ce0$0601a8c0@mred>
Message-ID: <20081229204259.GF6975@sphe.fedora.phx.redhat.com>
On 2008-12-29 10:37:55 AM, Dan Adams wrote:
> Yeah, did that, I really can read, but that not feedback is it? I hate to be
> a smart ass, but you might try re-reading my email.
"Communicate (Speak with Fedora)" and "Providing Feedback to Developers"
isn't feedback? Did you expect something more than bugzilla and mailing
lists? Exactly what part of this were you dissatisfied with?
Again, we welcome any constructive suggestions on how to make this more
obvious.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 29 20:49:54 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 15:49:54 -0500
Subject: Websites Meeting?
In-Reply-To:
References: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
<98F197F7-ECBE-489D-A3D1-B3F971502EBD@gmail.com>
Message-ID: <20081229204954.GH6975@sphe.fedora.phx.redhat.com>
On 2008-12-29 11:07:22 AM, Marc Ferguson wrote:
> Some one blogged on Planet Fedora about the SHA1SUM files being 5 levels deep
> on the site. I thought we could talk about that and just make it 2 levels by
> placing a link along with the other big blue blocks on the right-hand side on
> the "get fedora" page.
We actually discussed that a few meetings ago, and came to the same
conclusion. If you want, I can walk you through making that change
when you have a chance today.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Mon Dec 29 21:25:11 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Mon, 29 Dec 2008 16:25:11 -0500
Subject: Websites Meeting?
In-Reply-To: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
References: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
Message-ID: <20081229212511.GC25189@sphe.fedora.phx.redhat.com>
On 2008-12-29 04:41:28 AM, Ricky Zhou wrote:
> Hey, I know a lot of people are are enjoying the winter holidays, so I
> thought I'd check first - can most people make a meeting at 22:00 UTC
> today?
All right, since we only got a few responses, I think it's best to start
meetings again next week (2009-01-05 at 20:00 UTC).
Have a great holiday/new year, everybody!
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From kamisamanou at kamisamanou.net Tue Dec 30 05:20:43 2008
From: kamisamanou at kamisamanou.net (Kamisamanou Burgess)
Date: Mon, 29 Dec 2008 23:20:43 -0600
Subject: feedback
In-Reply-To: <95f9f4950812260652o7ccfc03l729b97c319b8b9c9@mail.gmail.com>
References: <95f9f4950812260652o7ccfc03l729b97c319b8b9c9@mail.gmail.com>
Message-ID: <5dbb83710812292120u152daa3doab931c82f50b816b@mail.gmail.com>
First, I want to say that I am sorry you are having so much trouble. Second,
I want to point out that I am not a very active developer of Fedora and I
have, with the exception of the user-supplier relationship, no connection to
RedHat. Now that all of the formal junk is taken care of, let's address the
issues:
2008/12/26 Dan Adams
> I have read in no less than 5 places on your website how much feedback is
> valued, yet I have found the feedback process cryptic and frustrating.
I will assume this(
http://fedoraproject.org/wiki/Communicate#Providing_Feedback_to_Developers)
is the process you speak of.
> All I wanted to do was provide a little feedback before uninstalling
> fedora, not join a club or create the one thousandth password that will
> never be used again.
Congratulations on 999 passwords(ok, I'm sorry, I couldn't resist).
Seriously:
- The first thing I want to point out is the reason for the necessary evil
of account creation. If everybody let whoever post/email/submit their
opinion without any way of determining who was doing so, the amount of
irrelevant or otherwise useless information that would be received would be
come a tedious waste of time. Also, people would be able to post the same
thing over and over again resulting in a heavily innaccurate idea of
"customer satisfaction." There is also the fact that if you go out of your
way to say something, it really matters to you.
A home-hitting example of this would be the webmaster email of the Fedora
Project. There is a large percentage of email that comes through this
address that is worthless and a total waste of time.(People asking us about
other websites that we are not affiliated with).
- Now that that is out of the way, Bugzilla: I will admit, I have used this
and I hate it with an utter and total passion. I do believe that cryptic and
frustrating could be used to describe this process and I'm not entirely sure
how one would provide general feedback using this.
Mailing Lists: This is probably the easiest, most effective way to provide
general feedback on the project. Sign up is quick and painless(in my
opinion) and those lists are often probed by the "important people." The
biggest downside is that while you are on the list, you will receive a bunch
of emails you most likely wouldn't give a crap about. The good news is that
you can unsubscribe from those mailing lists pretty easily.
> Nor read endless pages of someone else's opinions. I just wanted to pass on
> a comment that I though might be of some use to developers. If your
> developers truly want honest feedback then perhaps you might suggest to them
> that they create a conduit for that purpose that does not require all of the
> BS.
If I may ask of you, could you provide an idea of something you think would
be better, keeping in mind that account creation is important.
>
>
> --
> Thanks,
> Dan Adams.
Sayonara,
Kamisamanou Burgess
http://www.kamisamanou.net
>
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From marcferguson at gmail.com Wed Dec 31 19:40:11 2008
From: marcferguson at gmail.com (Marc Ferguson)
Date: Wed, 31 Dec 2008 14:40:11 -0500
Subject: Websites Meeting?
In-Reply-To: <20081229204954.GH6975@sphe.fedora.phx.redhat.com>
References: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
<98F197F7-ECBE-489D-A3D1-B3F971502EBD@gmail.com>
<20081229204954.GH6975@sphe.fedora.phx.redhat.com>
Message-ID:
2008/12/29 Ricky Zhou
> On 2008-12-29 11:07:22 AM, Marc Ferguson wrote:
> > Some one blogged on Planet Fedora about the SHA1SUM files being 5 levels
> deep
> > on the site. I thought we could talk about that and just make it 2
> levels by
> > placing a link along with the other big blue blocks on the right-hand
> side on
> > the "get fedora" page.
> We actually discussed that a few meetings ago, and came to the same
> conclusion. If you want, I can walk you through making that change
> when you have a chance today.
>
> Thanks,
> Ricky
>
>
> --
> Fedora-websites-list mailing list
> Fedora-websites-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-websites-list
>
>
Hi Ricky,
That would be great! You might have to put it in an email or something, I'm
not certain how we're gonna do any live communications right now. :D
--
*Marc F.*
www.fergytech.com
Registered Linux User: #410978
"When life gives me lemons... I make Linuxaide, hmm good stuff!" -Marc F.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mikey.j at ntlworld.com Mon Dec 29 23:25:09 2008
From: mikey.j at ntlworld.com (Mike Johnson)
Date: Mon, 29 Dec 2008 23:25:09 +0000
Subject: Fedora 10
Message-ID: <49595C55.3060907@ntlworld.com>
An HTML attachment was scrubbed...
URL:
From goldensunphotography at gmail.com Wed Dec 31 05:37:22 2008
From: goldensunphotography at gmail.com (goldensunphotography at gmail.com)
Date: Tue, 30 Dec 2008 21:37:22 -0800
Subject: comment
Message-ID: <5fd2da8b0812302137g3d3d4d07u4c6fc0e3dc8a3043@mail.gmail.com>
I am a "regular joe" visitor to your website.I'm pretty savvy with
computing but still chained to Windows XP.I'm passionate about saving
the world and ,upon reviewing the benefits of an open source operating
system,would love to try it.
Then i get stuck.And I mean stuck!
Does the open source community cater just to the Technically
Advanced?Doesnt this run counter to the set goals of the open source
community?
Surely at some point the open source community (and your website) must
make this revolution available to all.Even though your "product" is
free.....no-one knows how to use it!
Respectfully,
David Wells,BC,Canada
From krishmys at gmail.com Wed Dec 31 11:23:39 2008
From: krishmys at gmail.com (krishna N)
Date: Wed, 31 Dec 2008 16:53:39 +0530
Subject: difficulty in creating account
Message-ID: <85d0ed210812310323x178621c9v72ccc5a031841bc2@mail.gmail.com>
i have half way registered in fedora website but cant access my home
page....i have to fill some things like latitude,longitude,IRC nick,well the
website irc.freenode.net is not working,GPG key id,Public RSA SSH Key,i dont
know what they are and how to make the key the instruction is difficult to
understand like this : Public RSA SSH Key Many resources require public key
authentiaction to work. By uploading your public key to us, you can then log
in to our servers. Type "man ssh-keygen" for more information on creating
your key (it must be an RSA key). Once created you will want to upload
~/.ssh/id_rsa.pub...what this means.....and i cannot find india in
asia....for time....and i see that the form for free cd is closed and there
i came on a sentence that we have to provide a cd....well i hope UBUNTU is
better than this...i easily sign up there...and getting free cd's from past
a year with out any difficulty...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ricky at fedoraproject.org Wed Dec 31 21:48:26 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Wed, 31 Dec 2008 16:48:26 -0500
Subject: Websites Meeting?
In-Reply-To:
References: <20081229094128.GC6975@sphe.fedora.phx.redhat.com>
<98F197F7-ECBE-489D-A3D1-B3F971502EBD@gmail.com>
<20081229204954.GH6975@sphe.fedora.phx.redhat.com>
Message-ID: <20081231214826.GA13367@sphe.fedora.phx.redhat.com>
On 2008-12-31 02:40:11 PM, Marc Ferguson wrote:
> That would be great! You might have to put it in an email or something, I'm
> not certain how we're gonna do any live communications right now. :D
Ah, I'm sorry - I forgot that I had promised somebody I'd make that
change by Monday, so I ended up doing it.
I'll make sure to email/ping you for the next change.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From henriquecsj at gmail.com Wed Dec 31 23:43:24 2008
From: henriquecsj at gmail.com (Henrique Junior)
Date: Wed, 31 Dec 2008 21:43:24 -0200
Subject: Fedora's Mediawiki Skin
Message-ID: <4f629b520812311543u2a15dbf5g6bed59dc0d2ccbe9@mail.gmail.com>
Hi folks,
My name is Henrique and I'm one of the Brazilian ambassadors of Fedora here
in Brazil. We,re going to integrate a variety of tools to Fedora Project
Brazil and one of these tools is a wiki (that is online and working for
almost one year now)[1]. We'd like to use the same skin as
https://fedoraproject.org/wiki uses.
Is there any chance to get the same skin used by Fedora Project's
international mediawiki?
[1] - http://fedora.wiki.br
--
Henrique "LonelySpooky" Junior
http://www.lonelyspooky.com
-------------------------------------------------------------
"In a world without walls and fences, who needs windows and gates?!"
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ricky at fedoraproject.org Wed Dec 31 23:52:02 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Wed, 31 Dec 2008 18:52:02 -0500
Subject: Fedora's Mediawiki Skin
In-Reply-To: <4f629b520812311543u2a15dbf5g6bed59dc0d2ccbe9@mail.gmail.com>
References: <4f629b520812311543u2a15dbf5g6bed59dc0d2ccbe9@mail.gmail.com>
Message-ID: <20081231235202.GA17354@sphe.fedora.phx.redhat.com>
On 2008-12-31 09:43:24 PM, Henrique Junior wrote:
> My name is Henrique and I'm one of the Brazilian ambassadors of Fedora here in
> Brazil. We,re going to integrate a variety of tools to Fedora Project Brazil
> and one of these tools is a wiki (that is online and working for almost one
> year now)[1]. We'd like to use the same skin as https://fedoraproject.org/wiki
> uses.
> Is there any chance to get the same skin used by Fedora Project's international
> mediawiki?
I'm not sure what the rules are about logos (you can try asking
fedora-advisory-board or fedora-art-list about those), but our mediawiki
theme is available at
http://git.fedorahosted.org/git/fedora-web.git/?p=fedora-web.git;a=tree;f=fedoraproject.org/mediawiki
You can clone the entire git repository with:
git clone git://git.fedorahosted.org/git/fedora-web.git
and all of the theme files are in
fedora-web/fedoraproject.org/mediawiki/ (although note that that theme
references some files from http://fedoraproject.org/)
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
From ricky at fedoraproject.org Wed Dec 31 23:52:50 2008
From: ricky at fedoraproject.org (Ricky Zhou)
Date: Wed, 31 Dec 2008 18:52:50 -0500
Subject: comment
In-Reply-To: <5fd2da8b0812302137g3d3d4d07u4c6fc0e3dc8a3043@mail.gmail.com>
References: <5fd2da8b0812302137g3d3d4d07u4c6fc0e3dc8a3043@mail.gmail.com>
Message-ID: <20081231235250.GB17354@sphe.fedora.phx.redhat.com>
On 2008-12-30 09:37:22 PM, goldensunphotography at gmail.com wrote:
> I am a "regular joe" visitor to your website.I'm pretty savvy with
> computing but still chained to Windows XP.I'm passionate about saving
> the world and ,upon reviewing the benefits of an open source operating
> system,would love to try it.
> Then i get stuck.And I mean stuck!
> Does the open source community cater just to the Technically
> Advanced?Doesnt this run counter to the set goals of the open source
> community?
> Surely at some point the open source community (and your website) must
> make this revolution available to all.Even though your "product" is
> free.....no-one knows how to use it!
Can you please tell us exactly where you got stuck? We'd be happy to
help you out or direct you to the right place for your question.
Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: