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
lx
lx(5) Standards, Environments, and Macros lx(5)NAME
lx - Linux branded zone
DESCRIPTION
The lx brand uses the branded zones framework described in brands(5) to enable Linux binary applications to run unmodified on a machine
with a Solaris Operating System kernel.
The lx brand includes the tools necessary to install a CentOS 3.x or Red Hat Enterprise Linux 3.x distribution inside a non-global zone.
The brand supports the execution of 32-bit Linux applications on x86/x64 machines running the Solaris system in either 32-bit or 64-bit
mode.
Supported Linux Distributions
The lx brand emulates the system call interfaces provided by the Linux 2.4.21 kernel, as modified by Red Hat in the RHEL 3.x distributions.
This kernel provides the system call interfaces consumed by the glibc version 2.3.2 released by Red Hat.
In addition, the lx brand partially emulates the Linux /dev and /proc interfaces.
Configuration and Administration
The lx brand supports the whole root non-global zone model. All of the required linux packages are installed into the private file systems
of the zone.
The zonecfg(1M) utility is used to configure an lx branded zone. Once a branded zone has been installed, that zone's brand cannot be
changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used
to log in to the zone.
Application Support
The lx zone only supports user-level Linux applications. You cannot use Linux device drivers, Linux kernel modules, or Linux file systems
from inside an lx zone.
You cannot add any non-standard Solaris devices to a Linux zone. Any attempt to do so will result in a zone that zonecfg(1M) will refuse to
verify.
You cannot run Solaris applications inside an lx zone. Solaris debugging tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be
applied to Linux processes executing inside the zone, but the tools themselves must be running in the global zone. Any core files generated
are produced in the Solaris format, and such files can only be debugged with Solaris tools.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWlxr, SUNWlxu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO mdb(1), zlogin(1), zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M), brands(5), zones(5), lx_systrace(7D)SunOS 5.11 19 Sep 2006 lx(5)