10 More Discussions You Might Find Interesting
1. SCO
I'm trying to virtualize an instance of SCO Open Server 5.0.2c in VirtualBox (called VM- A) , I can not configure the network (NIC).
The NIC I'm using is PCnet -FAST III (Am79C973 ) (this NIC works with VirtualBox + SCO 5.0.5M)
When I add from ' Add new LAN adapter' I detects the NIC... (2 Replies)
Discussion started by: flako
2 Replies
2. Shell Programming and Scripting
Hello all,
I am having an issue setting up an environment on .profile. I want to set up my .profile in that way that everytime I login to the host, it should automatically set up my group. I tried the folllowing but it doesn't work. It is on the solaris OS.
HOSTNAME=$(hostname)
if ] || ]... (14 Replies)
Discussion started by: Pateltiger
14 Replies
3. Solaris
Hi,
I have a Solaris (SunOS 5.10) installed, by default with the en_AU.UTF-8 locale. I want to change it to en_US.UTF-8
With AU, I have no issues whatsoever, so I installed the language package and now locale -a shows "en_US.UTF-8".
Problem is even with LC_ALL set in etc/default/init, the... (2 Replies)
Discussion started by: asdfg
2 Replies
4. Solaris
Dear All,
I Have problem at my console (Ultra 24, solaris 10 x86), when i type dmesg always come out :
like this
You have new mail.
root@console # bash
root@console # dmesg
couldn't set locale correctly
couldn't set locale correctly
So how to fix it...?
Best Regards
simbah (3 Replies)
Discussion started by: mbah_jiman
3 Replies
5. Solaris
Hello,
I have a recently configured machine that when log into it as a user or remotely as root it displays "Couldn't set locale correctly"
When I type locale it displays the below which is wrong compared to other machines
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"... (7 Replies)
Discussion started by: Mr Pink
7 Replies
6. Solaris
hi All,
I'm using sun OS 5.10.
All locales are set to en_US.ISO8859-1 in /etc/profile/init file.
I'm using one functional user.When I tried to "sesu - functionalUser",its giving me error like "Couldn't set locale correctly".In functional user profile i'm tring to set locales to en_US.After... (1 Reply)
Discussion started by: Kathraji
1 Replies
7. UNIX for Dummies Questions & Answers
I am getting the error message
"Permission denied (publickey).
lost connection"
when I attempt to do an scp migration. I know how to generate the public keys in both IIS and UNIX, and I believe they are both suppose to have the same public key - but where are they each suppose to be stored (I... (1 Reply)
Discussion started by: whs2k
1 Replies
8. UNIX for Dummies Questions & Answers
The “set -o vi” command won't run in the .profile. WHY?
This has me puzzled as the problem seems to be too simple, but can't figure it out. Here's the info...
Running...
Generic sun4u sparc SUNW,Ultra-5_10
K shell
Here's the .profile
# Copyright (c) 2001 by Sun Microsystems, Inc.
# All... (12 Replies)
Discussion started by: jimmyc
12 Replies
9. UNIX for Dummies Questions & Answers
When a user connects via ssh to one of out Sun V120 boxes the following message is displayed.
"couldn't set locale correctly"
The .profile has the following line
# @(#)local.profile 1.6 98/02/06 SMI
stty istrip
stty erase ^H
So I put a set -x in the .profile and re sourced it and... (1 Reply)
Discussion started by: mattd
1 Replies
10. UNIX for Dummies Questions & Answers
I'm using Linux-Mandrake 8.0 in my laptop. After I logged in as a "root", I added a new path in my .bashrc file (I use bash shell). Then I can observe it has been set correctly by typing echo $PATH.
But, when I log in again as a personal account, not "root", then I open my bash shell, and type... (5 Replies)
Discussion started by: yishen
5 Replies
LOGPROF(8) AppArmor LOGPROF(8)
NAME
aa-logprof - utility program for managing AppArmor security profiles
SYNOPSIS
aa-logprof [-d /path/to/profiles] [-f /path/to/logfile] [-m <mark in logfile>]
OPTIONS
-d --dir /path/to/profiles
The path to where the AppArmor security profiles are stored
-f --file /path/to/logfile
The path to the location of the logfile that contains AppArmor
security events.
-m --logmark "mark"
aa-logprof will ignore all events in the system log before the
specified mark is seen. If the mark contains spaces, it must
be surrounded with quotes to work correctly.
DESCRIPTION
aa-logprof is an interactive tool used to review AppArmor's complain mode output and generate new entries for AppArmor security profiles.
Running aa-logprof will scan the log file and if there are new AppArmor events that are not covered by the existing profile set, the user
will be prompted with suggested modifications to augment the profile.
When aa-logprof exits profile changes are saved to disk. If AppArmor is running, the updated profiles are reloaded and if any processes
that generated AppArmor events are still running in the null-complain-profile, those processes are set to run under their proper profiles.
Responding to AppArmor Events
aa-logprof will generate a list of suggested profile changes that the user can choose from, or they can create their own, to modifiy the
permission set of the profile so that the generated access violation will not re-occur.
The user is then presented with info about the access including profile, path, old mode if there was a previous entry in the profile for
this path, new mode, the suggestion list, and given these options:
(A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit
If the AppArmor profile was in complain mode when the event was generated, the default for this option is (A)llow, otherwise, it's (D)eny.
The suggestion list is presented as a numbered list with includes at the top, the literal path in the middle, and the suggested globs at
the bottom. If any globs are being suggested, the shortest glob is the selected option, otherwise, the literal path is selected. Picking
includes from the list must be done manually.
Hitting a numbered key will change the selected option to the corresponding numbered entry in the list.
If the user selects (N)ew, they'll be prompted to enter their own globbed entry to match the path. If the user-entered glob does not match
the path for this event, they'll be informed and have the option to fix it.
If the user selects (G)lob last piece then, taking the currently selected option, aa-logprof will remove the last path element and replace
it with /*.
If the last path element already was /*, aa-logprof will go up a directory level and replace it with /**.
This new globbed entry is then added to the suggestion list and marked as the selected option.
So /usr/share/themes/foo/bar/baz.gif can be turned into /usr/share/themes/** by hitting "g" three times.
If the user selects (A)llow, aa-logprof will take the current selection and add it to the profile, deleting other entries in the profile
that are matched by the new entry.
Adding r access to /usr/share/themes/** would delete an entry for r access to /usr/share/themes/foo/*.gif if it exists in the profile.
If (Q)uit is selected at this point, aa-logprof will ignore all new pending capability and path accesses.
After all of the path accesses have been handled, logrof will write all updated profiles to the disk and reload them if AppArmor is
running.
New Process (Execution) Events
If there are unhandled x accesses generated by the execve(2) of a new process, aa-logprof will display the parent profile and the target
program that's being executed and prompt the user to select and execute modifier. These modifiers will allow a choice for the target to:
have it's own profile (px), inherit the parent's profile (ix), run unconstrained (ux), or deny access for the target. See apparmor.d(5) for
details.
If there is a corresponding entry for the target in the qualifiers section of /etc/apparmor/logprof.conf, the presented list will contain
only the allowed modes.
The default option for this question is selected using this logic--
# if px mode is allowed and profile exists for the target
# px is default.
# else if ix mode is allowed
# ix is default
# else
# deny is default
aa-logprof will never suggest "ux" as the default.
ChangeHat Events
If unknown change_hat(2) events are found, the user is prompted to add a new hat, if the events should go into the default hat for this
profile based on the corresponding entry in the defaulthat section of logprof.conf, or if the following events that run under that hat
should be denied altogether.
Capability Events
If there are capability accesses, the user is shown each capability access and asked if the capability should be allowed, denied, or if the
user wants to quit. See capability(7) for details.
BUGS
None. Please report any you find to bugzilla at <http://bugzilla.novell.com>.
SEE ALSO
klogd(8), auditd(8), apparmor(7), apparmor.d(5), change_hat(2), logprof.conf(5), aa-genprof(1), aa-complain(1), aa-enforce(1), and
<http://forge.novell.com/modules/xfmod/project/?apparmor>.
NOVELL
/SUSE 2008-06-11 LOGPROF(8)