Hi,
I am a Linux / Unix newbie c programmer.
I have a c/c++ daemon server that will receive authentication (userid / password) from a windows client.
All I want to do is authenticate the user via PAM API - i.e. user must exist on the Unix / Linux system + password must be validated.
... (1 Reply)
I have a linux machine which authenticate users to ldap, this is working fine. But I would like to limit users that logon to the machines to just the system admins.
The machines hosts different web sites which users accessed from there home directory like http://foo.mdx.ac.uk/~username
At the... (0 Replies)
HI,
There is a user having problem when he try to login to solaris box, it works after few tried. What may be the problem?
PAM authentication
Password:
PAM authentication
Password:
PAM authentication
New Password: (1 Reply)
Hello Group,
I'm facing Problem with the configuration of "***pam_radius_auth.so.1***" module to be integrated with Freeradius and Funk Steel Belted Radius. Both this radius servers are able to make "Access-Accept" packet. But the SSH or Telnet client is not able to login to the system with the... (0 Replies)
My PAM module seems to work right but it fails in authentication. Althought it can't authenticate, the session module works and the software who uses it executes well.
For example, when I login through "gdm" using pam to authenticate against an ldap server
/var/log/auth.log shows
Any... (1 Reply)
Greetings!
I just managed to install Solaris 10 on a Sparc based machine. However, there might be a problem with the way ssh is configured.
I CAN ssh from the machine into another on the network (same subnet, as root), but then the newly installed machine CANNOT seem to accept incoming ssh... (2 Replies)
Hi,
I've configured two linux boxes to authenticate against Windows Active Directory using Kerberos while retrieving authorization data (uids, gids ,,,)from NIS.
The problem I ran into with my PAM configuration is that all authentication attempts succeed in order.i.e. if someone tried his... (0 Replies)
Hi all.
I'm having real trouble authenticating users against active directory for my SCO UnixWare 7.1.4 box running samba 3.0.24 (installed via Maintenance pack 4). I can list AD users/groups (after overcoming several hiccups) with wbinfo -g / wbinfo -u. I can use id to get a view an ad user ie:... (0 Replies)
I have applied pam authentication for local users as highlighted in below file.
# cat /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required pam_env.so
auth sufficient pam_unix.so... (0 Replies)
Hello all,
I recently updated PAM policy files (pam_authz.policy) on HP-UX Servers with AD groups involving allowing and denying the certain groups..
Could anyone tell me what is the equivalent mechanism in SLES(Linux)? Is it possible to allow/deny AD group access with the SLES LDAP... (0 Replies)
Discussion started by: lcclaj0
0 Replies
LEARN ABOUT OPENSOLARIS
brands
brands(5) Standards, Environments, and Macros brands(5)NAME
brands - alternate operating environments for non-global zones
DESCRIPTION
The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which
provide non-global zones that contain non-native operating environments.
The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current zones
structure.
Every zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed
and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time. The default
is the native brand.
A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ-
ment. Once a zone has been assigned a brand, that brand cannot be changed or removed.
BrandZ extends the zones tools in the following ways:
o A brand is an attribute of a zone, set at zone create time.
o The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone.
o The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone.
Device Support
The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects
any attempt to add an unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported
device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C),
ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F)SunOS 5.11 13 Feb 2009 brands(5)