| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <41B21FED.3020807@nbnet.nb.ca>
From: smenard at nbnet.nb.ca (Stephen Menard)
Subject: MacOSX -FreeBSD
>>
>> On 2-Dec-04, at 3:32 PM, Randall Craig wrote:
>>
>> On Thu, 2 Dec 2004 10:58:02 -0600, Randall Craig
>> <rgcraig@...il.com> wrote:
>> Ok I am super duper new to this list and also new to *nix... i will
>> never go back to M$ ceptin for gaming purposes... I am running on OS
>> X.3.3 and was wanting to know if the Security Alert pertaining to
>> FreeBSD would also affect my system. I know that BSD is running
>> underneath OS X... I am fairly sure that Apple is aware of it by
>> now-.
>> thnx
>
From Mac OS X Developer technotes
only reference gdb access to /proc
_maybe_ there is a compatibility layer there ;
key word _compatibilityLayer_
try from the terminal
>man fstab
`procfs.c'
This contains the /target_ops vector/ that supports Unix child
processes on systems which use /proc to control the child.
BSD 4.4 man page _bottom_
*FILES*
/dev special files and device names
/var/run/dev.db /dev name database
/var/db/kvm_kernel.db system namelist database
/proc the mount point of procfs(5)
*SEE* *ALSO*
kill(1) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/kill.1.html#//apple_ref/doc/man/1/kill>, w(1) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/w.1.html#//apple_ref/doc/man/1/w>, kvm(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/kvm.3.html#//apple_ref/doc/man/3/kvm>, strftime(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/strftime.3.html#//apple_ref/doc/man/3/strftime>, procfs(5), pstat(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/pstat.8.html#//apple_ref/doc/man/8/pstat>
*BUGS*
Since *ps* cannot run faster than the system and is run as any other sched-scheduled
uled process, the information it displays can never be exact.
4th Berkeley Distribution April 18, 1994 4th Berkeley Distribution
ALTHOUGH there is a DARWIN Man Page highlighting procfs
You should check to see if it matches the MacOSX man page for fstab
-=-==-=-=--==-=--=-=-=
FSTAB(5) BSD File Formats Manual FSTAB(5)
*NAME*
*fstab* - static information about the filesystems
*SYNOPSIS*
*#include* *<**fstab.h**>*
*DESCRIPTION*
The file *fstab* contains descriptive information about the various file
systems. *fstab* is only read by programs, and not written; it is the duty
of the system administrator to properly create and maintain this file.
Each filesystem is described on a separate line; fields on each line are
separated by tabs or spaces. The order of records in *fstab* is important
because diskarbitrationd(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/diskarbitrationd.8.html#//apple_ref/doc/man/8/diskarbitrationd>, fsck(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/fsck.8.html#//apple_ref/doc/man/8/fsck>, mount(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/mount.8.html#//apple_ref/doc/man/8/mount>, and umount(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/umount.8.html#//apple_ref/doc/man/8/umount> sequen-sequentially
tially iterate through *fstab* doing their thing.
The first field, (_fs_*_*_spec_), describes the block special device, the local
filesystem, or the remote filesystem to be mounted. The diskarbitrationd
program supports the identification of a local filesystem uniquely by its
UUID or by its volume name, irrespective of hardware configuration and of
hardware parallelism, using the constructs ``UUID'' and ``LABEL''.
The second field, (_fs_*_*_file_), describes the mount point for the filesys-filesystem.
tem. For swap partitions, this field should be specified as ``none''.
The third field, (_fs_*_*_vfstype_), describes the type of the filesystem. The
system currently supports these types of filesystems:
_ufs_ a local UNIX filesystem
_nfs_ a Sun Microsystems compatible ``Network File System''
_swap_ a disk partition to be used for swapping
_msdos_ a DOS compatible filesystem
_cd9660_ a CD-ROM filesystem (as per ISO 9660)
_procfs_ a file system for accessing process data
_kernfs_ a file system for accessing kernel parameters
_fdesc_ an implementation of /dev/fd
_union_ a translucent filesystem
The fourth field, (_fs_*_*_mntops_), describes the mount options associated
with the filesystem. It is formatted as a comma separated list of
options. It contains at least the type of mount (see _fs_*_*_type_ below) plus
any additional options appropriate to the filesystem type.
The option ``auto'' can be used in the ``noauto'' form to cause a file
system not to be mounted automatically (with ``mount -a'', or system boot
time).
The type of the mount is extracted from the _fs_*_*_mntops_ field and stored
separately in the _fs_*_*_type_ field (it is not deleted from the _fs_*_*_mntops_
field). If _fs_*_*_type_ is ``rw'' or ``ro'' then the filesystem whose name is
given in the _fs_*_*_file_ field is normally mounted read-write or read-only on
the specified special file. If _fs_*_*_type_ is ``sw'' then the special file
is made available as a piece of swap space by the swapon(8) command at
the end of the system reboot procedure. The fields other than _fs_*_*_spec_
and _fs_*_*_type_ are unused. If _fs_*_*_type_ is specified as ``xx'' the entry is
ignored. This is useful to show disk partitions which are currently
unused.
The fifth field, (_fs_*_*_freq_), is used for these filesystems by the dump(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/dump.8.html#//apple_ref/doc/man/8/dump>
command to determine which filesystems need to be dumped. If the fifth
field is not present, a value of zero is returned and dump will assume
that the filesystem does not need to be dumped.
The sixth field, (_fs_*_*_passno_), is used by the fsck(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/fsck.8.html#//apple_ref/doc/man/8/fsck> program to determine
the order in which filesystem checks are done at reboot time. The root
filesystem should be specified with a _fs_*_*_passno_ of 1, and other filesys-filesystems
tems should have a _fs_*_*_passno_ of 2. Filesystems within a drive will be
checked sequentially, but filesystems on different drives will be checked
at the same time to utilize parallelism available in the hardware. If
the sixth field is not present or zero, a value of zero is returned and
fsck will assume that the filesystem does not need to be checked.
#define FSTAB_RW "rw" /* read-write device */
#define FSTAB_RO "ro" /* read-only device */
#define FSTAB_SW "sw" /* swap device */
#define FSTAB_XX "xx" /* ignore totally */
struct fstab {
char *fs_spec; /* block special device name */
char *fs_file; /* filesystem path prefix */
char *fs_vfstype; /* type of filesystem */
char *fs_mntops; /* comma separated mount options */
char *fs_type; /* rw, ro, sw, or xx */
int fs_freq; /* dump frequency, in days */
int fs_passno; /* pass number on parallel fsck */
};
The proper way to read records from _fstab_ is to use the routines
getfsent(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/getfsent.3.html#//apple_ref/doc/man/3/getfsent>, getfsspec(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/getfsspec.3.html#//apple_ref/doc/man/3/getfsspec>, getfstype(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/getfstype.3.html#//apple_ref/doc/man/3/getfstype>, and getfsfile(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/getfsfile.3.html#//apple_ref/doc/man/3/getfsfile>.
*FILES*
/etc/fstab The file *fstab* resides in _/etc_.
*SEE* *ALSO*
getfsent(3) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/getfsent.3.html#//apple_ref/doc/man/3/getfsent>, diskarbitrationd(8) <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/diskarbitrationd.8.html#//apple_ref/doc/man/8/diskarbitrationd>
*HISTORY*
The *fstab* file format appeared in 4.0BSD.
Darwin March 28, 2002 Darwin
=--=-=-=-=-=-==--=-==-
SVR4 Process information
Many versions of SVR4 provide a facility called `/proc' that can be used
to examine the image of a running process using file-system subroutines.
If GDB is configured for an operating system with this facility, the
command |info proc| is available to report on several kinds of
information about the process running your program. |info proc| works
only on SVR4 systems that include the |procfs| code. This includes OSF/1
(Digital Unix), Solaris, Irix, and Unixware, but not HP-UX or GNU/Linux,
for example.
|info proc|
Summarize available information about the process.
|info proc mappings|
Report on the address ranges accessible in the program, with
information on whether your program may read, write, or execute each
range.
-=-=-=-==--=
Mac OS X implements
Beneath the appealing, easy-to-use interface of Mac OS X is a rock-solid
foundation that is engineered for stability, reliability, and
performance. This foundation is a core operating system commonly known
as Darwin. Darwin integrates a number of technologies, most importantly
Mach 3.0, operating-system services based on 4.4BSD (Berkeley Software
Distribution), high-performance networking facilities, and support for
multiple integrated file systems.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20041204/fa475deb/attachment.html
Powered by blists - more mailing lists