10-13-2000
You must insure that the versions of network daemons such as the services you decribe in your post are running the lastest patches which have addressed the vulnerabilites you are concerned about. Most software with known vulnerabilites has patches to close the security holes. NFS has had many vulnerablities, historically, over the years; but they are patched and newer versions fixed. You should check to see what versions you are running and make sure you have the latest versions.
9 More Discussions You Might Find Interesting
1. AIX
We have windows clients that access drawing files shared from our AIX server using NFS. The Windows clients are intermittently unable to open files or access the system. For some reason restarting the rpc.lockd temporarily resolves the problem. However, that is the only clue I have to what the... (1 Reply)
Discussion started by: theologic
1 Replies
2. Solaris
How to implement NFS Security in server where filesystem is configured as NFS & AutoFS?
Any special patch need to be applied?
What are the procedures? (1 Reply)
Discussion started by: KhawHL
1 Replies
3. Red Hat
I can't seem to make sense of this.
$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.2 Beta (Tikanga)
$
$ mount
/dev/sda2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on... (6 Replies)
Discussion started by: dfinn
6 Replies
4. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
If you look at the permissions associated with a symbolic link, it has universal access. Does this lead to... (0 Replies)
Discussion started by: linux17
0 Replies
5. UNIX for Advanced & Expert Users
Hello,
We have some new application requirements that require us to use nfs mounts from aix 5.3 and mount to Oracle Linux 5.6.
Do you know why when on the destination ( linux ) box, the root user cannot access directories made by other users in the nfs mounted filesystem ?
I read that there... (0 Replies)
Discussion started by: fwellers
0 Replies
6. BSD
Hi!
I have a major issue with FreeBSD 7.1 i386.
We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp.
Now I cant mount homedirs since NFS/AMD seem to fallback to udp :(
Trying to force it with amd options nfs_proto=tcp and so on.
... (0 Replies)
Discussion started by: Esaia
0 Replies
7. HP-UX
Hi, I support a small lab of older HP UX 9 and 10 boxes. We have some older NT 4.0 machines at each UX box, with a old ZFS Server programs hosting two mounted directories. (Each UX and NT machine is on its own private network via crossover cable). Due to hardware failure/support EOL on NT, I have... (3 Replies)
Discussion started by: the spyder
3 Replies
8. UNIX for Advanced & Expert Users
Does the use of cron (HP-UX 11) present a security risk IF it is only given to accounts which have shell access anyway.
If it does present a risk, what is the risk?
Can a script (or command) run via cron; run anything, write anywhere or read anywhere that the same user can not do outside of... (2 Replies)
Discussion started by: eileenkeeney
2 Replies
9. Red Hat
Hi Experts,
I have been using Linux (Redhat server 5.6) as a NFS server and it is mounted to 4 linux (SUSE) servers for storing the db logs. I added an entry in fstab in all my 4 clients to make sure the mount is available all the time. but unfortunately the mount is not showing in servers after... (6 Replies)
Discussion started by: sarav
6 Replies
LEARN ABOUT DEBIAN
stg-series
STG-SERIES(1) StGit Manual STG-SERIES(1)
NAME
stg-series - Print the patch series
SYNOPSIS
stg series [options] [<patch-range>]
DESCRIPTION
Show all the patches in the series, or just those in the given range, ordered from top to bottom.
The applied patches are prefixed with a + (except the current patch, which is prefixed with a >), the unapplied patches with a -, and the
hidden patches with a !.
Empty patches are prefixed with a 0.
OPTIONS
-b BRANCH, --branch BRANCH
Use BRANCH instead of the default branch.
-a, --all
Show all patches, including the hidden ones.
-A, --applied
Show the applied patches only.
-U, --unapplied
Show the unapplied patches only.
-H, --hidden
Show the hidden patches only.
-m BRANCH, --missing BRANCH
Show patches in BRANCH missing in current.
-c, --count
Print the number of patches in the series.
-d, --description
Show a short description for each patch.
--author
Show the author name for each patch.
-e, --empty
Before the +, >, -, and ! prefixes, print a column that contains either 0 (for empty patches) or a space (for non-empty patches).
--showbranch
Append the branch name to the listed patches.
--noprefix
Do not show the patch status prefix.
-s, --short
List just the patches around the topmost patch.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SERIES(1)