Sponsored Content
Full Discussion: Security Setup
Top Forums UNIX for Dummies Questions & Answers Security Setup Post 42613 by Perderabo on Friday 31st of October 2003 10:26:04 AM
Old 10-31-2003
My solution would be to change the way you are using groups. Your business id's would be given a group of "guest" in the passwd file. But their home directories would have another group, "adm". And I would:
chown bus01:adm /home/bus01
chmod 770 /home/bus01

Now bus01 can access his home directory, but only his. And any member of the adm group can access all the home directories.

Also the solaris ftpd supports chrooted homes and I would put all of the busxx folks into one large chrooted environment.

Finally I would consider replacing the solaris ftpd with a super-secure replacement like pureftpd. That would be the ultimate in security.
 

We Also Found This Discussion For You

1. AIX

NIM server setup on etherchannel setup environment

I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it? I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame. Any help is appreciated. (1 Reply)
Discussion started by: pdtak
1 Replies
mkmanifest(1)						      General Commands Manual						     mkmanifest(1)

Name
       mkmanifest - makes list of file names and their DOS 8+3 equivalent

Note of warning
       This  manpage  has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete.  See the
       end of this man page for details.

Description
       The mkmanifest command is used to create a shell script (packing list) to restore Unix filenames. Its syntax is:

       mkmanifest [ files ]

       Mkmanifest creates a shell script that aids in the restoration of Unix filenames that got clobbered by the  MS-DOS  filename  restrictions.
       MS-DOS filenames are restricted to 8 character names, 3 character extensions, upper case only, no device names, and no illegal characters.

       The mkmanifest program is compatible with the methods used in pcomm, arc, and mtools to change perfectly good Unix filenames to fit the MS-
       DOS restrictions. This command is only useful if the target system which will read the diskette cannot handle VFAT long names.

Example
       You want to copy the following Unix files to a MS-DOS diskette (using the mcopy command).

	    very_long_name
	    2.many.dots
	    illegal:
	    good.c
	    prn.dev
	    Capital

       ASCII converts the names to:

	    very_lon
	    2xmany.dot
	    illegalx
	    good.c
	    xprn.dev
	    capital

       The command:

	  mkmanifest very_long_name 2.many.dots illegal: good.c prn.dev Capital >manifest

       would produce the following:

	    mv very_lon very_long_name
	    mv 2xmany.dot 2.many.dots
	    mv illegalx illegal:
	    mv xprn.dev prn.dev
	    mv capital Capital

       Notice that "good.c" did not require any conversion, so it did not appear in the output.

       Suppose I've copied these files from the diskette to another Unix system, and I now want the files back to their original  names.   If  the
       file "manifest" (the output captured above) was sent along with those files, it could be used to convert the filenames.

Bugs
       The short names generated by mkmanifest follow the old convention (from mtools-2.0.7) and not the one from Windows 95 and mtools-3.0.

See Also
       Mtools' texinfo doc

Viewing the texi doc
       This  manpage  has  been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
       items, such as crossreferences, footnotes and indices are lost in this translation process.  Indeed, these items have no appropriate repre-
       sentation  in  the manpage format.  Moreover, not all information has been translated into the manpage version.	Thus I strongly advise you
       to use the original texinfo doc.  See the end of this manpage for instructions how to view the texinfo doc.

       *      To generate a printable copy from the texinfo doc, run the following commands:

		     ./configure; make dvi; dvips mtools.dvi

       *      To generate a html copy,	run:

		     ./configure; make html

       A premade html can be found at `http://www.gnu.org/software/mtools/manual/mtools.html'

       *      To generate an info copy (browsable using emacs' info mode), run:

		     ./configure; make info

       The texinfo doc looks most pretty when printed or as html.  Indeed, in the info version certain examples are difficult to read due  to  the
       quoting conventions used in info.

mtools-4.0.18							      09Jan13							     mkmanifest(1)
All times are GMT -4. The time now is 01:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy