I have another question about pfexec, it does not source .profile of the user
it runs as. Is this by design?
Is it assumed that the executable has the environment already set or we need to
write wrappers which source the user's .profile?
Thanks in advance,
-- prasad
--
This message p
as a symlink in the
pathname (for historical reasons and now our users are used to it). Now pfexec
is failing with permission denied because of the above logic.
What are my options?
a) Educate my users to use the new pathname
b) Remove the symlink
Thanks in advance,
-- prasad
--
This message posted from opensolaris.org
/logLvl
ppriv[6658]: missing privilege "file_dac_execute" (euid = 2000, syscall = 59)
needed at ufs_access+0x3c
ppriv: /u01/apps/dncs/bin/logLvl: Permission denied
Why is logLvl running with euid=2000? When does it run with euid=app?
Thanks in advance,
-- prasad
--
This message p
off base here, so please point me
in the right direction.
Thanks in advance.
-- prasad
--
This message posted from opensolaris.org
Hi,
In general RC4 is variable key length algorithm. But in openssl pkcs#11 engine,
it is implemented like other fixed length algorithms and its key length is
limited to 128 bit.
Can you please tell me whether my understanding is right?
Thanks
DP
This message posted from opensolaris.org
Hi Darren and Jan,
Thank you very much for clarifying my doubts.
This message posted from opensolaris.org
different from openssl PKCS#11 engine?
Thanks in advance
Durga Prasad
This message posted from opensolaris.org
tion processes authorization aware (is this the
right term?) i.e. use auth_attr.h, chkauthattr(3SECDB), etc.
Are we approaching this the correct way? How do we handle scripts (run them as
"approot")? How do we deal with physical files that are currently owned by
"appuser"?
T
