Sponsored Content
Special Forums Cybersecurity NFS security issues with lockd and statd Post 85 by Neo on Friday 13th of October 2000 01:30:11 AM
Old 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

Problem with NFS & rpc.lockd-Help Needed

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 Sun Solaris 9

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

Issues with LDAP user/group permissions on NFS share

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

Security issues with universal access of file

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

nfs mount permission issues

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

FreeBSD AMD NFS over TCP issues

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

SFU and NFS issues

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

Cron security issues?

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

NFS mount issues

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
STG-SINK(1)							   StGit Manual 						       STG-SINK(1)

NAME
stg-sink - Send patches deeper down the stack SYNOPSIS
stg sink [-t <target patch>] [-n] [<patches>] DESCRIPTION
This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be more easily committed or pushed. If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to option allows to place them under any applied patch. Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then (unless --nopush is also given) pushing back into place the formerly-applied patches. OPTIONS
-n, --nopush Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed. -t TARGET, --to TARGET Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack. -k, --keep Keep the local changes. STGIT
Part of the StGit suite - see linkman:stg[1] StGit 03/13/2012 STG-SINK(1)
All times are GMT -4. The time now is 08:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy