09-24-2003
Hi,
There is :
root Userid 0
non-root Userid 1 <> 100
users Userid > 100
In fact only root will have more permissions. The rest is what you specify inside the application or with file ownership. I think you need to learn the unix basics starting at examine an "ls -l" and then understanding what is says.
Regs David
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I was wondering if someone could help me with ACL's. I have a file, say output, created by the root user, member of group other. Its permissions are rwxr--r--. I want only people in group other to have rwx access, but I also want one other user, stephen, member of some_other_group to have rwx... (1 Reply)
Discussion started by: sroberts82
1 Replies
2. Shell Programming and Scripting
Hey all, I have a directory (own by user: b; group: grpB) which I want a user (user: a; group: grpA) to be able to read and execute from, I wonder if I should add user a to this particular directory's ACL or that I would add group grpB to user a's subgroup?
I would like to know the difference... (3 Replies)
Discussion started by: mpang_
3 Replies
3. Solaris
Hi,
I want to set access control list on folders but it should be recursively,
any Idea? command (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. UNIX for Dummies Questions & Answers
In OS like windows, I can define an Access Control List (ACL) and specify which accounts and groups have what access to a specific file.
I assume U*X, Linux and cygwin on windows have this ACL feature too. I'm using cygwin on windows. What do I type at a bash prompt to allow a specific user... (1 Reply)
Discussion started by: siegfried
1 Replies
5. UNIX for Dummies Questions & Answers
I need to control intenet access @ work. xample. I need PC 1 to only be able to access these five sites and add to the list as needed. Can anyone pint me a direction. (1 Reply)
Discussion started by: fruiz
1 Replies
6. AIX
Hello,
I've configurated a LDAP user authentication on AIX V6 against Active Directory (Windows Server 2008).
The Tree is built as follows:
test (DC)
|--- testgroup (group with members: user1, user2)
|
|--- sys1 (OU)
| |--- sys1group (group with member: user1)
|
|--- sys2 (OU)... (0 Replies)
Discussion started by: xia777
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am using eTrust Access Control at work. I have got no output after type checklogin. I wonder what is the reason. Does anyone know? Thanks
eTrustAC selang v8.00a-1555.13 - eTrustAC command line interpreter
Copyright (c) 2006 CA. All rights reserved.
eTrustAC> checklogin user1... (0 Replies)
Discussion started by: uuontario
0 Replies
8. Proxy Server
Dear all experts here,
:)
I would like to install a proxy server on Linux server to perform solely to control the access of Web server.
In this case, some of my vendor asked me to try Squid and I have installed it onto my Linux server.
I would like know how can I set the configuration to... (1 Reply)
Discussion started by: kwliew999
1 Replies
LEARN ABOUT DEBIAN
sivtest
SIVTEST(1) General Commands Manual SIVTEST(1)
*
NAME
sivtest - interactive MANAGESIEVE test program
SYNOPSIS
sivtest [ -t keyfile ] [ -p port ] [ -m mechanism ]
[ -a userid ] [ -u userid ] [ -k num ] [ -l num ]
[ -r realm ] [ -f file ] [ -n num ] [ -c ]
[ -i ] [ -o option=value ] [ -v ] hostname
DESCRIPTION
sivtest is a utility that allows you to authenticate to a MANAGESIEVE server and interactively issue commands to it. Once authenticated you
may issue any MANAGESIEVE command by simply typing it in. It is capable of multiple SASL authentication mechanisms and handles encryption
layers transparently. This utility is often used for testing the operation of a timsieved server. Also those developing MANAGESIEVE clients
find it useful.
OPTIONS
-t keyfile
Enable TLS. keyfile contains the TLS public and private keys. Specify "" to negotiate a TLS encryption layer but not use TLS
authentication.
-p port
Port to connect to. If left off this defaults to sieve as defined in /etc/services.
-m mechanism
Force sivtest to use mechanism for authentication. If not specified the strongest authentication mechanism supported by the server
is chosen.
-a userid
Userid to use for authentication; defaults to the current user. This is the userid whose password or credentials will be presented
to the server for verification.
-u userid
Userid to use for authorization; defaults to the current user. This is the userid whose identity will be assumed after authentica-
tion. NOTE: This is only used with SASL mechanisms that allow proxying (e.g. PLAIN, DIGEST-MD5).
-k num Minimum protection layer required.
-l num Maximum protection layer to use (0=none; 1=integrity; etc). For example if you are using the KERBEROS_V4 authentication mechanism
specifying 0 will force sivtest to not use any layer and specifying 1 will force it to use the integrity layer. By default the max-
imum supported protection layer will be used.
-r realm
Specify the realm to use. Certain authentication mechanisms (e.g. DIGEST-MD5) may require one to specify the realm.
-f file
Pipe file into connection after authentication.
-n num Number of authentication attempts; default = 1. The client will attempt to do SSL/TLS session reuse and/or fast reauth (e.g.
DIGEST-MD5), if possible.
-c Enable challenge prompt callbacks. This will cause the OTP mechanism to ask for the the one-time password instead of the secret
pass-phrase (library generates the correct response).
-i Don't send an initial client response for SASL mechanisms, even if the protocol supports it.
-o option=value
Set the SASL option to value.
-v Verbose. Print out more information than usual.
SEE ALSO
timsieved(8)
CMU
Project Cyrus SIVTEST(1)