Linux NFS development
 help / color / mirror / Atom feed
From: Greg Hennessy <greg.hennessy@navy.mil>
To: nfs@lists.sourceforge.net
Subject: rpc.statd
Date: Thu, 16 Nov 2006 11:02:14 -0500	[thread overview]
Message-ID: <455C8B86.4000907@navy.mil> (raw)

[-- Attachment #1: Type: text/plain, Size: 415 bytes --]

I'm running Fedora core 5 on my departmental workstations, and as part
if a certification and accreditation effort I need to verify that
the computers I'm running don't suffer from CAN-2004-1014,
Linux NFS RPC.STATD Remote Denial Of Service Vulnerability.
nfs-utils 1.0.6 is listed as a vulnerable version on
http://www.securityfocus.com/bid/11785/info
Can anyone speak on if 1.0.7 (which is what I run) is safe?



[-- Attachment #2: greg.hennessy.vcf --]
[-- Type: text/x-vcard, Size: 278 bytes --]

begin:vcard
fn:Greg Hennessy
n:Hennessy;Greg
org:USNO;Astrometry Department
adr:;;3450 Mass. Ave. NW;Washington;DC;20392;USA
email;internet:gsh@usno.navy.mil
title:Astronomer
tel;work:(202) 762-1523
tel;fax:(202) 762-1514
url:http://ad.usno.navy.mil/~gsh
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2006-11-16 16:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=455C8B86.4000907@navy.mil \
    --to=greg.hennessy@navy.mil \
    --cc=gsh@usno.navy.mil \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox