b! 0 H DX P 1L .text P P DX P t .data E ^ @.bss ( ( .loader 8( .debug ( K B (= , |nx|#x|+xb , 0 A A < | S * N!A 9 @}{x~x H ` , A b $H CmA | @ __start , M H 4N @ __threads_init !|A f H | F N!A b |`yA c | C N!A b |`yA t c | C N!A b |`yA c | C N!A b |`yA c | C N!A H8! @}N b |`yAK A __threads_init@AF2_1 | 4! HH qA H8! @}N A (
call_pth_init 8A L | N | !P D8` a Da b Hc a @a @( @ H $a @c ( Àa @c 8 8 H %A , @a D( @ <8` H -A a Da D( A H 88 8H -A H La D 8 T:H 9A a a ( A H 8 8 8H A a a D8a H8 8 AH ` a @c 8c a a c ( =A a c ( A H H 4a 8c a a c ( =A a c ( A KԀa @ |P8a HH ` 8 8a HH ` 8a HH A D T:|d).a D T:|c .( A H 8@8t8H A a 8c a a @8c a @a @c ( @H A 8axH A ax8|H 1A b |8c H EA a|H aA axH }A 8` aTH ` aT aUb c , A tb 9? L8 8` 8 8 8 ?H aA 8apH }A ap8tH A b t8c H A atH ŀA apH A @8` H
eA 8U8T8 T8 8 9 H ՀA `d 8`X DH
-A X8` | @ aX,ܻA b c , A tb 9? \8 8` 8 8 8 @H
yA 8ahH
A ah8lH
A b l8c H
A alH
݀A ahH
A 8` )aTH ,aX,ܻ@ b c , A xb AX9? d8 8` 8 8 8 CH ݀A 8a`H A a`8dH
A b d8c H
%A adH
AA a`H
]A 8` aTH b c , A xb AX9? l88` 8 8 8 AH MA 8aXH iA aX8\H A b \8c H A a\H A aXH ̀A 8` aTH aL, A 8` )aTH aL8c aL8` a\8` aT8` a@<`8c aD8H8a@H A ,@ @H рA c , @ !H!@H H 8H8a@H }A ,AH 8` )aTH H a88c a8a8`| A aT, )@ H H aX,ܠ@ 8` a\H b c , A tb 9? t88` 8 8 8 BH
ɀA 8a0H
A a084H
A b 48c H A a4H -A a0H IA 8` )aTH a\, @̀aT, @\8 tx|8a}8 H ` 8` aT8` 8 8 H A apap, @ 8` )aTH 8` a}8 88 |8a~H uA ap8|8H A , @ H A c , 7@ apH A H t8` aTapH qA 8` aa x8` | @ ax8c axax<8 |c!a 8 8aH
]A ,@ @H
uA c , @ ! !H H 8 8aH
!A ,AH 8` ac |8|8 |ac |8|8 |aaaa<`su8cria8` a88aH
5` aTaT, A hb c , A L8a H A a 8H A b 8c H A aH рA a H A 8` )aTH ap8H *` aTaT, A hb c , A L8aH A a8H A b 8c H 1A aH MA aH iA 8` )aTH 4b c , A$ap8H 2 ` aTaT, A hb c , A L8aH qA a8 H A b 8c H A a H A aH ՀA 8` )aTH 88aH ` aTaT, A hb c , A L8aH A a8H A b 8c H A aH 5A aH QA 8` )aTH a( dA 8` )aTH apH 9A 8aH 5` 8aH )` 8aH ` aT, @ H 0at, <|` &Tc/aat8c ata, @b c , A aT, @ lb c , A 0b $9? 8(8` 8 8 8 IH A H ,b 9? 848` 8 8 8 DH yA H ,b 9? 8@8` )8 8 8 EH MA 8aH iA a8H A b 8c H A aH A aH ̀A aTH H |8!N "A
` main LA L | N PA L | N TA L | N XA L | N H
@ memset / T, / |M 00A HA A , , N@ A , N@ A $ , % N@ A $ , , / / N@ A L N@ A L N@ A L% N@ A L $ , , / / K B N B N B N % B N @ strncpy pk =@!k 9J}i8 A , A P8 B 8 } P8})P},P@ } P8})P},PA})@})PyA}+ 4Uk|Xp !k }iA , 8 M 8 B 耤 0|P8})P},P@ 4 } P8})P},P@ , |P8})P},PA})(})PyAH })@})PyA}Cx8 t T@> @N @ strcat \A L | N `A L | N hA L | N lA L | N pA L | N tA L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N A L | N ĐA L | N ȐA L | N !a h la lc c a @a @( A @a h @d a lc hd a @ hd a h l d H h H|d)a D8c a Da H8ca Ha D H| AH H X|8! PN A cas__reverse |! Xa h la ha Da D, @ a h|c Аa h8` a @a h8
|#|)|eP8c 0Tc> l @|e1a @8c a @a h|c#a ha h, Aa D, @ l @8` -|d)a @8c a @ l @8` |d)a lK]H H X|8! PN A cas__itoa | !;8b c a La L, A ,a L, A $a L, A a L, A H pH l8 @8 c d 8` a GH UA a H8a @H A 8 9 H8 @8 8 8 9 H IA H H h|8! `N A cas__trace_exit |! Ha Xa X( A 8a Xc ( A (a Xc H A X8` d Xd H H|8! @N A d cas__release_buffer |! Ha Xa X( A da Xc , A @a Xc $( A 0a Xc $ X 8 KQ` a Xc $H %A a X8 8 (K-` H H|8! @N A cas__release_xdata |fx|#x|3xH @ bcopy @ memmove АA L | N ԐA L | N ܐA L | N A L | N A L | N A L | N A L | N A L | N A L | N |! Ha X \ `a X \ `H ]A H H|8! @N A @ poll | !P;a Ȑ 8` a @a Ha L 萁 Pa T8a X8\H ` 8b c a a , A a , A H 0H ,8a XK-A 8 8 X8 L8 K8 KaA a Ȑa H8` a L8` H A a T P8a H8 Kѐa @ @8` | @ KqA c , @ D P8` H aA c `e 8` T|(P | P P P| @ H b KA c C 9? 8H8`
8 8 8 K歀A 8`
a @H a @, @ 4b $8T8` f8 8 8 KqA 8` fa @H ha @, @ Xa NTc( A 8` a @H @b A N9? 8`8`
8 8 8 KA 8`
a @H K8b c a a , A a , A H 8H 48a XK]A 8 9 @8 X8 T8 L8 9 KA a @H H |8! N A _cas__check_socket_for_reading | !P;a Ȑ 8` a @8a D8 d $ X p %( "| % ; Δ " $\ $ ( ' & ) "$ P | *p ( 1X / * 0 U X x N HH ( F Wh @ | e s YX p w [X g up $ , a P Kl | - '< , z8 ( l\ ]` S I 8p 5 )p E8 BD c _p 4 < 7p : 8 p p ` 0 P L $ !t THL file: %1$s Trace file: %1$s Config. file: %1$s Trace levels: %1$s UDS file name: %1$s 2649-170 %1$s: %2$s
Reserved: DO NOT USE! Trace file size: %1$d Public key file: %1$s Private key file: %1$s Request queue size: %1$d SRC system %1$s is active.
Trace file (env. var.): %1$s SRC system %1$s is starting.
Request queue init time: %1$s 2649-070 Authentication error. No. of requests serviced: %1$d Trace levels (env. var.): %1$s HBA CCDB's time-to-live: %1$ds HBA2 CCDB's time-to-live: %1$ds 2649-042 Invalid mechanism code. 2649-077 Invalid ACL entry type. 2649-040 Unix Identity mismatch. 2649-001 Informational message 1. Trace file size (env. var.): %1$d 2649-004 Configuration file error. 2649-008 The connection timed out. 2649-127 Unix Identity mis-match.
2649-039 Unable to allocate memory. 2649-044 A socket operation failed. 2649-071 Network credentials error. 2649-072 Delegated credentials error. 2649-169 %1$s: Invalid option: %2$c.
HBA2 security context lifetime: %1$ds 2649-129 The credentials have expired. 2649-002 ctcasd is not running as root. No. of worker threads: %1$d (%2$d idle) Max/min no. of worker threads: %1$d/%2$d 2649-073 User information processing error. 2649-020 Unable to find directory /var/ct/.
SRC system %1$s is inactive or inoperative.
2649-043 Incorrect buffer or version number. 2649-076 Empty ACL submitted for processing. 2649-003 Memory allocation error (%1$s:%2$d). 2649-010 The reading of data was interrupted. Client or server must continue data exchange. 2649-078 Invalid privilege attributes buffer. SRC system %1$s is ready to receive requests.
SRC system %1$s is ready to process requests.
CAS client socket file clean up interval: %1$ds SRC system %1$s is already running on the host.
2649-069 A socket operation failed (errno = %d). 2649-074 Unable to obtain host name or IP address. No. of current requests: %1$d active; %2$d pending 2649-036 Caller provided incorrect arguments to %s. 2649-037 Invalid security services or context token. 2649-013 Service 0x%1$08x is not supported by ctcasd. 2649-014 Error on thread operation (%1$s: rc = %2$d). 2649-167 %1$s: Option provided more than once: %2$s.
2649-024 The server reported a 'server busy' condition 2649-132 Environment Variable: %1$s value is in error. SRC system %1$s was started successfully (pid = %2$d).
2649-041 Buffer has incorrect identifier or is corrupt. 2649-006 Error on socket operation (%1$s: errno = %2$d). 2649-018 Error on signal operation (%1$s: errno = %2$d).
2649-075 Unable to determine service name for target: %s. Unable to allocate memory for full status, but I'm alive! 2649-130 The credentials are either not valid or corrupted. 2649-005 One of the arguments provided to %1$s is not valid. 2649-012 Request 0x%1$08x not supported by service 0x%2$08x. SRC system %1$s was started but unable to receive requests.
2649-168 %1$s: Option %2$s provided with invalid value: %3$s.
2649-128 The system call to retrieve the local hostname failed. 2649-019 Unable to create directory %1$s (mkdir(): errno = %2$d).
2649-035 An error occurred in the MPM layer: %08#x %08#x %08#x %s. 2649-063 Verification of the signature failed in the routine %s.
2649-060 Invalid security context token or identity context token.
2649-011 %1$s: the buffer containing the marshaled data is not valid. 2649-051 unix_mpm Failure: Invalid mapping entry in the mapping file
2649-054 unix_mpm Failure: The network identity (%1$s) has no mapping
2649-021 The server is not able to perform the authentication request.
2649-061 User represented by identity context (%s) is not authorized.
2649-015 Unable to queue request:
queue size=%1$d
pending requests=%2$d
2649-016 Unable to create the minimum number of worker threads configured.
2649-047 Unix mpm failure: Unable to determine service name for target: %s. 2649-030 %1$s Failure: Incorrect mapping entry in the mapping file:
%2$s
2649-032 %1$s Failure: The following network identity has no mapping
%2$s
2649-062 One or more input buffers supplied to the routine %s are not valid.
2649-049 unix_mpm Failure: Error in routine %1$s while getting the mapped name
2649-022 An error occured during the server's attempt to get the client's identity.
2649-099 libct_cas Failure: Error on socket operation [%1$s:%2$d].
%3$s: errno = %4$d 2649-009 Data communication failure (send(): message length = %1$d, bytes sent = %2$d. 2649-059 Current process (%1$d) does not have permissions to set the user id to %2$d.
2649-045 Session Key expected but not received from CtCasd. Possible transmission error. 2649-052 unix_mpm Failure: The number of tokens in rule and network identity
does not match.
2649-023 Unable to set the current working directory to /var/ct/IW/run/ctcas (chdir(): %1$d).
2649-007 The file descriptor ready for reading or writing does not match the connecting socket. 2649-017 Unable to set the appropriate permission on file/directory %1$s (chmod(): errno = %2$d).
2649-053 unix_mpm Failure: The network identity (%1$s) supplied to translator routine is not valid
2649-001 Unable to start DAE: dae_init() failed (rc = %1$d)
file = %2$s
version = %3$s
line = %4$d
2649-038 Unix MPM Failure: The credentials acquired by the unix mpm
is either not valid or corrupted.
2649-046 Unix mpm failure: Configuration error,Check the defaults/overrides file in /opt/rsct/lib/mpm/ 2649-134 libct_cas Status: The host identified in the credentials
is not a trusted host on this system.
2649-131 The public key in %1$s does not match the public key for the host in the Trusted Host List %2$s.
2649-057 Unix MPM Failure: The network identity acquired by the Unix
mpm is either not valid or corrupted.
2649-031 %1$s Failure: The following network identity supplied to
translator routine is not valid:
%2$s.
2649-056 unix_mpm Failure: Context token doesn't support the data privacy services
requested by application
2649-055 unix_mpm Failure: Context token doesn't support the data integrity services
requested by application
2649-065 unix_mpm Failure: unable to obtain the hostname of the current host.
Detail: gethostname() returned -1.
2649-034 %1$s Failure: The number of tokens in the identity mapping
rule and the network identity does not match.
2649-086 %1$s Failure: The context control data buffer acquired by
the security mechanism are either invalid or corrupted.
2649-058 Unable to find mapping for predefined service name %1$s.
Check the unix.map file in /var/ct/cfg/ or /opt/rsct/cfg/ . 2649-064 unix_mpm Failure: unable to obtain the node id of the current host.
Detail: cu_get_node_id() returned error code %1$d.
2649-068 unix_mpm Failure: The network identity (%1$s) and the ACLE
identifier (%2$s) provided to the %3$s routine do not match.
An error occurred when attempting to acquire status of SRC system %1$s.
Make sure that the named SRC system is defined and has a valid definition.
SRC system %1$s could not be started by the SRC master.
Make sure that /opt/rsct/bin/ctcasd exists and is a valid
program or that system resources are available to start the daemon.
2649-171 Failure: Unable to find a mapping for predefined service
name %1$s.
Please check the ctcas_hba2.map file in /var/ct/cfg/ or /opt/rsct/cfg/
and make sure such a mapping exists. 2649-029 %1$s Failure: The following network identity, which was
supplied to the internal translator routine, is not valid:
network identity value: %2$s
detected by subroutine: %3$s
2649-105 libct_cas Internal failure detected.
Function name: %1$s
Return code from function: %2$d
Routine calling the function: %3$s
Contact IBM Customer Support and report this incident.
2649-025 libct_cas failure: the ctcas client library is unable to execute
the /opt/rsct/bin/ctstrtcasd command. The following error was returned by the
system() function call: errno = %1$d.
2649-067 unix_mpm Failure: The network identity (%1$s) provided
to the %2$s routine is not a valid network identity. A valid network identity
is of the following format: @.
2649-141 ctcasd Failure: The daemon was unable to initialize the
CLiC runtime environment. The following message was returned by CLiC
initialization routine:
%1$s
File name: %2$s
Line number: %3$d
2649-066 unix_mpm Failure: This security mechanism does not support the
use of the SEC_F_NO_RESOLVE flag with a host name. To use the SEC_F_NO_RESOLVE
option, specify the target host as an address.
2649-139 libct_cas Failure: Unable to determine the permission of the
client socket file.
socket file name: %1$s
stat() errno: %2$d
Make sure that there is no other application that deleted the socket file.
2649-026 libct_cas failure: the ctcas client library is unable to start
the ctcas SRC subsystem. Please make sure that the subsystem is registered with
SRC and that /opt/rsct/bin/ctcasd exists on the system.
2649-118 ctcasd Daemon Internal failure detected.
Function name: %1$s
Return code from function: %2$d
Routine calling the function: %3$s
Contact the cluster software service provider and report this incident.
2649-173 ctcasd Failure : Unable to enqueue SRC request due to a time-out condition.
Source file name: %1$s(%2$d)
The most probable reason for this error is a server busy condition.
Resubmit the SRC request at a later time.
2649-085 %1$s Failure: This security mechanism does not support the
use of the SEC_F_NO_RESOLVE flag with a host name or with an incorrect host
address. To use the SEC_F_NO_RESOLVE option, specify the target host as a
valid address.
2649-119 ctcasd Daemon Internal Failure: incorrect parameters were
provided to a daemon subroutine.
Function name: %1$s
Positional parameter number: %2$d
Parameter value: 0x%3$x
Contact the cluster software service provider and report this incident.
2649-175 ctcasd Failure : Unable to receive the SRC request.
recvfrom() returned the following error: errno = %1$d
Source file name: %2$s(%3$d)
The most probable reason for this error is a communication problem.
Resubmit the SRC request at a later time.
2649-084 %1$s Failure: A data buffer is not in a valid format.
An incorrect data buffer may have been used, or the data may have been
corrupted. Contact IBM Customer Support and report this failure.
failing subroutine name: %2$s
location: %3$d
2649-120 ctcasd Daemon Failure: the daemon detected that an
unsupported key generation method was configured. The following unsupported
key generation method was configured:
0x%1$x
Repair the ctcasd daemon configuration information to specify a supported
key generation method.
2649-176 ctcasd Failure : Unable to receive the SRC request.
recvfrom() received a smaller amount of bytes than expected.
Number of bytes returned: %1$d
Source file name: %2$s(%3$d)
The most probable reason for this error is a communication problem.
Resubmit the SRC request at a later time.
2649-048 unix_mpm Failure: Incorrect parameters detected.
Detecting function name: %1$s
Positional parameter in error: %2$d
Value of parameter: 0x%3$x
Verify that the application is providing the correct parameters to this
function, and correct the application to pass valid parameters.
2649-174 ctcasd Failure : Internal failure : pthread routine error.
Name of failing routine: %1$s
Return code of failing routine: %2$d
Source file name: %3$s(%4$d)
The most probable reason for this error is a programming error.
Please contact IBM Customer Support Center and report this problem.
2649-140 libct_cas Failure: Unable to change the file permission of
the client socket file to at least execute/read/write by owner.
socket file name: %1$s
chmod() errno: %2$d
file permission: %3$o
file's owner uid: %4$d
effective uid of process: %5$d
Make sure that there is no other application that modified the socket file
in any way.
2649-106 libct_cas Failure: The security library is unable to
initialize the data structures necessary to convert between the codeset used
by this application and the UTF-8 data encoding format. This failure has
occurred because resources needed by the cluster utilities are not available
at this time. Try to run this application again at a later time.
2649-156 ctcasd Failure : Unable to fully resolve the target host name
provided in the request.
Target host name: %1$s
cu_gethostbyname() rc: %2$d
Source file name: %3$s(%4$d)
The most probable reason for this error is the fact that the target
host name does not have an entry with the DNS service. Update the DNS
record to include the target host name specified.
2649-088 %1$s Failure: A response CCDB buffer was provided by
the %2$s system service, but the %1$s was not expecting it. This failure
forces the security infrastructure to not treat the client application as
authentic. Note this failure information and contact the system
administrator. System administrators should contact IBM Customer Support
and report the problem.
2649-133 ctcasd Failure: the cipher contained in the CCDB has a length
(%1$d) that is not multiple of the RSA modulus for the type of key used
for decryption (%2$d). This condition may happen when the client and
server hosts have different types of host keys. Please make sure that
the client and server hosts has the same type of Host Based
Authentication (HBA) keys.
2649-087 %1$s Failure: Unable to locate a fully resolved host
name for the specified target host system.
target host name: %2$s
Ensure that the correct name was provided for the target host system. If
the correct name was provided, contact the system administrator and have
the system administrator verify that the host is registered with the domain
name services for the network.
2649-154 ctcasd Failure: Credential timestamp/nonce already played.
Credential owner: %1$s
Credential nonce: %2$llx
Source file name: %3$s(%4$d)
The credentials provided for authentication contain a timestamp and nonce
that were already played before. This symptom is indicative of a credential
replay attack and the authentication of these credentials is purposedly
terminated with a failure.
2649-152 ctcasd Failure : Failed to initialize any of the HBA2 replay
protection-related pthread mutex locks.
Source file name: %1$s(%2$d)
The usual reason for this failure is a lack of system resources. Make
sure that the system has sufficient pthread resources available.
The failure to initialize any of the HBA2 protection pthread mutex locks
renders the protection mechanism inoperational.
2649-083 %1$s Failure: The security context has expired. The
application must end this security context and establish a new security
context. If this condition persists, report this condition to the software
service representatives for the application. The software service
representatives should modify the application to establish a new security
context when the existing security context expires.
2649-027 %1$s Failure: incorrect parameters provided.
Function name: %2$s
Positional parameter number: %3$d
Parameter value: 0x%4$x
If this failure is encountered during the execution of the Cluster software
trusted services, contact IBM Customer Support and report this incident.
If this failure is encountered during the execution of other software,
verify that the software is using this function correctly.
2649-101 libct_cas Failure: incorrect parameters provided.
Function name: %1$s
Positional parameter number: %2$d
Parameter value: 0x%3$x
If this failure is encountered during the execution of the Cluster software
trusted services, contact IBM Customer Support and report this incident.
If this failure is encountered during the execution of other software,
verify that the software is using this function correctly.
2649-151 ctcasd Failure : Failed to lock the replay log pthread mutex lock.
pthread_mutex_lock() rc: %1$d
Source file name: %2$s(%3$d)
The logging of replay info is done in order to provide persistent
tracking during daemon restarts. The failure to lock the pthread mutex
lock associated with the replay logging may be indicative of a system-wide
problem. Please contact the IBM Customer Support and report this
incident.
2649-137 Unix Identity mis-match. The party asking for credential
authentication (%1$s) is not the intended target of the credentials.
This condition may happen if the service name used by the client does not
map to the same user id on both the client's and the server's host.
Please check whether the process presenting the credential for authentication
to the ctcasd security daemon is running under the correct identity.
2649-111 ctcasd Daemon Failure: The stat system call reported a
failure in obtaining kernel memory resources. This may indicate that the
operating system is not configured properly, or that additional resources
need to be dedicated to the operating system kernel. Consult the problem
determination documentation and procedures for the operating system in use
on the system and perform any corrective actions recommended by those
sources.
2649-082 %1$s Failure: A data buffer provided to the security
mechanism subroutine is not large enough to store the requested data.
subroutine name: %2$s
size of data buffer provided: %3$d bytes
size of data buffer needed: %4$d bytes
Report this information to the software service representatives for the
application. The application service representatives should modify the
application to provide a buffer with sufficient memory space.
2649-143 ctcasd Failure : Unable to stat() the HBA2 service mapping file.
Name of the HBA2 service mapping file: %1$s
stat() errno: %2$d
Source file name: %3$s(%4$d)
Most often, this failure occurs when the file or a directory in the file
path does not exist.
This files is installed by default by RSCT and the fact that it does not
exist may signal other problems with RSCT. If the file does not exist,
contact the IBM Customer Support and report this incident.
2649-155 ctcasd Failure : The HBA2 security mechanism does not support the
use of the SEC_F_NO_RESOLVE flag with a host name. To use the SEC_F_NO_RESOLVE
option, specify the target host as an address.
Target host name: %1$s
Source file name: %2$s(%3$d)
The target host identifier is provided in a format that is incompatible
with the SEC_F_NO_RESOLVE flag. If the SEC_F_NO_RESOLVE flags is provided,
then the target host identifier must be provided as an IP address instead
of a host name.
2649-161 ctcasd Failure: The server credentials provided for authentication
do not contain a valid session key.
Source file name: %1$s(%2$d)
The most probable cause for this failure is a corrupted credentials
due to a hacking attack or a communication problem between the
application client and server.
Make sure the application client and server are free of memory
violation problems.
If this happens in relation to an RSCT trusted service, please contact
the IBM Customer Support and report this incident.
2649-164 ctcasd Failure: The HBA2 request is not valid. The request does
not contain a valid CCDB that can be authenticated.
Source file name: %1$s(%2$d)
The most probable cause for this failure is a corrupted request due to a
hacking attack or a communication problem between the application client
and server.
Make sure the application client and server are free of memory violation
problems.
If this happens in relation to an RSCT trusted service, please contact
the IBM Customer Support and report this incident.
2649-080 %1$s Attention: A match between a network identity and an
access control list entry was not found.
Network identity: %2$s
Acess control list entry identity: %3$s
Comparison subroutine name: %4$s
This may be the expected result of this comparison. This result occurred
because an application was performing an access control verification step.
The application is responsible for determining whether this result is the
expected result, or if the result indicates a failure condition.
2649-090 %1$s Failure: A session key was provided by the %2$s
system service for a security context that already has a session key
established for it. This condition causes the security subsystem to not
consider the client application authentic. Contact the system administrator
and report this incident. System administrators should examine the %2$s
system service for possible failure information and perform any necessary
troubleshooting procedures and repairs. If the condition persists, contact
IBM Customer Support.
2649-172 ctcasd Failure : Unable to verify the credentials provided
for authentication by client. Failed to find any public key for the host
identifiers included in the credentials that can verify the credential.
Client name: %1$s
Source file name: %2$s(%3$d)
The most probable reason for this error is an incomplete setup of the
THL file on the local host. Please make sure that there is a public key
for at least one of the host identifiers provided in the credential and
that it matches the private key of the host it represents.
2649-089 %1$s Failure: Unable to extract a session key from the
data provided by the %2$s system service. A security context cannot be
established without a session key. This failure causes the security
subsystem to not consider the client application authentic.
Contact the system administrator and report this incident. System
administrators should examine the %2$s system service for possible failure
information and perform any necessary troubleshooting procedures and
repairs. If the condition persists, contact IBM Customer Support.
2649-158 ctcasd Failure: Unix Identity mis-match. The party asking for
credential authentication is not the intended target of the credentials.
Client asking for credential authenticatoin: %1$s
Identity for which credential was intended: %2$s
Source file name: %3$s(%4$d)
This condition may happen if the service name used by the client does not
map to the same user id on both the client's and the server's host.
Please check whether the process presenting the credential for authentication
to the ctcasd security daemon is running under the correct identity.
2649-165 ctcasd Failure: The HBA2 time-to-live value is not valid.
Its value contains charaters that are not numeric.
TTL value string: %1$s
Source file name: %2$s(%3$d)
The HBA2 time-to-live value is specified by the HBA2_CRED_TIMETOLIVE
configuration parameter. Make sure that its value in the ctcad configuration
file (either the default /opt/rsct/cfg/ctcasd.cfg or the overriding
copy /var/ct/cfg/ctcasd.cfg) is a number between 0 and 600.
If its value already is a number between 0 and 600, please contact the IBM
Customer Support and report this incident.
2649-103 libct_cas Failure: The marshaled data provided to this
routine is either incorrect or corrupted. It is possible that the application
has inadvertently overwritten the variable containing the address of the
data, or the application may have inadvertently overwritten the memory used
to store the data. Verify that the application is providing the correct
address for the marshaled input data to this routine. Perform memory leak
and memory use verification tests on the application to ensure that the
application is not inadvertently modifying this memory.
2649-079 %1$s Failure: A network identity is not in a valid format.
The format expected is: @.
Network identity in error: %2$s
Detected in subroutine: %3$s
This failure was detected as part of an access control verification step.
Determine which application was performing this verification and contact the
software support service for this application. Software support should
verify that the proper access control data structures are being provided to
the verification interfaces, and that this data has not somehow become
corrupted.
2649-135 ctcasd Failure: Unable to construct a credential for the
requesting client.
Failing routine: %1$s
Return code from failing routine: %2$d
This failure may occur when the ctcasd daemon is unable to allocate memory.
Verify that the system has sufficient virtual memory available. Administrators
might consider extending the virtual memory size of the system or terminating
applications using excessive virtual memory. If this condition persists or
occurs frequently, contact the cluster software security service provider and
report this condition.
2649-162 ctcasd Failure: The HBA2 request is not valid. The request is
either intended for a different service or has an unsupported version.
Request magic: %1$08x
Request version: %2$d
Source file name: %3$s(%4$d)
The most probable cause for this failure is a corrupted request due to a
hacking attack or a communication problem between the application client
and server.
Make sure the application client and server are free of memory violation
problems.
If this happens in relation to an RSCT trusted service, please contact
the IBM Customer Support and report this incident.
2649-159 ctcasd Failure: The credentials provided for
authentication are not valid. The credential flags indicate they are
both client's and server's credentials.
Credentials flags: 0x%1$08x
Source file name: %2$s(%3$d)
The most probable cause for this failure is a corrupted credentials
due to a hacking attack or a communication problem between the
application client and server.
Make sure the application client and server are free of memory
violation problems.
If this happens in relation to an RSCT trusted service, please contact
the IBM Customer Support and report this incident.
2649-166 ctcasd Failure: The HBA2 time-to-live value is not valid.
Unable to convert its string representation to a numerical representation.
strtol() errno: %1$d
TTL value string: %2$s
Source file name: %3$s(%4$d)
The HBA2 time-to-live value is specified by the HBA2_CRED_TIMETOLIVE
configuration parameter. Make sure that its value in the ctcad configuration
file (either the default /opt/rsct/cfg/ctcasd.cfg or the overriding
copy /var/ct/cfg/ctcasd.cfg) is a number between 0 and 600.
If its value already is a number between 0 and 600, please contact the IBM
Customer Support and report this incident.
2649-163 ctcasd Failure: The HBA2 request is not valid. The request does
not contain a valid target user/service name or a valid target registry name.
Request target name: %1$s
Request target user/service name: %2$s
Source file name: %3$s(%4$d)
The most probable cause for this failure is a corrupted request due to a
hacking attack or a communication problem between the application client
and server.
Make sure the application client and server are free of memory violation
problems.
If this happens in relation to an RSCT trusted service, please contact
the IBM Customer Support and report this incident.
2649-033 %1$s Failure: unable to obtain the Reliable Scalable Cluster
Technology (RSCT) Node Identifier of the current host. This condition can
occur when the RSCT software has not been configured, when the RSCT software
configuration has been removed, or when the RSCT configuration files on the
local system have been corrupted. Contact the system administrator and
report this problem. System administrators should verify that the RSCT
software configuration has been properly established. If the RSCT
configuration is correct, contact IBM Customer Support.
Detail: cu_get_node_id() returned error code %2$d.
2649-157 ctcasd Failure : Unable to verify the credentials provided
for authentication by client. Failed to find a public key for the host
identifiers included in the credentials that can verify the credential.
Client name: %1$s
Source file name: %2$s(%3$d)
The most probable reason for this error is an incomplete setup of the
THL file on the local host. Another reason for this error may be an
unsanctioned change in the HBA key setup on the remote host.
Please make sure that there is a public key for at least one of the
host identifiers provided in the credential and that it matches the
private key of the host it represents.
2649-104 libct_cas Failure: The marshaled data provided to this
routine does not contain a required data field. It is possible that the
application has provided an incorrect address for the marshaled data, or has
inadvertently overwritten the variable containing the address of the
data, or the application may have inadvertently overwritten the memory used
to store the data. Verify that the application is providing the correct
address for the marshaled input data to this routine. Perform memory leak
and memory use verification tests on the application to ensure that the
application is not inadvertently modifying this memory.
2649-148 ctcasd Failure : Failed to open the HBA2 service mapping file.
Name of the HBA2 service mapping file: %1$s
open() errno: 0x%2$08x
Source file name: %3$s(%4$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
If the problem occurs with the overriding copy of the HBA2 service file ,
please make sure that the file is valid. Otherwise, please contact the
IBM Customer Support and report this incident.
2649-153 ctcasd Failure : Credential time skew too great.
Credential owner: %1$s
Time skew value in seconds: %2$d
Source file name: %3$s(%4$d)
The credentials provided for authentication are too old or too far into
the future. It is possible that the time difference between the credential
initiator's host and the credential authenticator's host is greater than
the time skew value. It is also possible that the network latency is too
great. Another possibility is that these credentials are replayed.
Please make sure that the time between the initiator's and the
authenticator's hosts is synchronized and that there is no noticeable
network latency.
2649-144 ctcasd Failure : The ctcasd's HBA2 service mapping file is a directory.
Name of the HBA2 service mapping file: %1$s
File mode bits as returned by stat(): 0x%2$08x
Source file name: %3$s(%4$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
Such an error with the HBA2 service mapping file may be generated by
other problems within RSCT or the base operating system.
Contact the IBM Customer Support and report this incident.
2649-145 ctcasd Failure : The HBA2 service mapping file has no contents.
Name of the HBA2 service mapping file: %1$s
Size of the file as returned by stat(): %2$d
Source file name: %3$s(%4$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
If the problem occurs with the overriding copy of the HBA2 service file ,
please make sure that the file has a valid contents. Otherwise, please
contact the IBM Customer Support and report this incident.
2649-146 ctcasd Failure : The HBA2 service mapping file is not owned by root.
Name of the HBA2 service mapping file: %1$s
Owner of the file as returned by stat(): %2$d
Source file name: %3$s(%4$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
If the problem occurs with the overriding copy of the HBA2 service file ,
please make sure that the file is owned by root. Otherwise, please
contact the IBM Customer Support and report this incident.
2649-160 ctcasd Failure: The credentials provided for authentication
are not valid. Either there is no registry list; or the credentials are
server credentials and there are more than one registry in the registry list.
Credentials flags: 0x%1$08x
Number of registries in list: %2$d
Source file name: %3$s(%4$d)
The most probable cause for this failure is a corrupted credentials
due to a hacking attack or a communication problem between the
application client and server.
Make sure the application client and server are free of memory
violation problems.
If this happens in relation to an RSCT trusted service, please contact
the IBM Customer Support and report this incident.
2649-100 libct_cas Failure: The marshaled data provided to this
routine is either invalid or corrupted.
Name of the routine: %1$s
Source file name: %2$s(%3$d)
The routine detected a repeated data field within the marshalled data.
It is possible that the application has inadvertently overwritten the
variable containing the address of the data, or the application may have
inadvertently overwritten the memory used to store the data. Verify that
the application is providing the correct address for the marshalled input
data to this routine. Perform memory leak and memory use verification
tests on the application to ensure that the application is not inadvertently
modifying this memory.
2649-149 ctcasd Failure : Failed to read the content of the HBA2 service
mapping file.
Name of the HBA2 service mapping file: %1$s
read() errno: %2$d
Number of bytes requested to read: %3$d
Source file name: %4$s(%5$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
If the problem occurs with the overriding copy of the HBA2 service file ,
please make sure that the file is valid. Otherwise, please contact the
IBM Customer Support and report this incident.
2649-109 libct_cas Failure: The marshaled data provided to this
routine is either incorrect or corrupted. The marshaled data interpretation
functions of the security library detected a repeated data field within the
marshaled data. It is possible that the application has inadvertently
overwritten the variable containing the address of the data, or the
application may have inadvertently overwritten the memory used to store the
data. Verify that the application is providing the correct address for the
marshaled input data to this routine. Perform memory leak and memory use
verification tests on the application to ensure that the application is not
inadvertently modifying this memory.
2649-150 ctcasd Failure : Failed to read the content of the HBA2 service mapping file.
Name of the HBA2 service mapping file: %1$s
Number of bytes requested to read: %2$d
Number of bytes read: %3$d
Source file name: %4$s(%5$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
If the problem occurs with the overriding copy of the HBA2 service file ,
please make sure that the file is valid. Otherwise, please contact the
IBM Customer Support and report this incident.
2649-107 libct_cas Failure: The security library is unable to
translate a character string between the application codeset and
the UTF-8 data encoding format. The character string contains bytes that are
non-valid in the application codeset. This failure can occur when
codesets that do not fully support UTF-8 conversion are used by the execution
environment. This failure can also occur if the character string memory is
overwritten. Verify that the application uses a locale with a codeset that
does support UTF-8 conversion, or contact the system administrator to have
the default execution environment set to use such a locale. Also verify that
the application is not accidentally overwriting the character string data.
2649-108 libct_cas Failure: The marshaled data provided to this
routine is either incorrect or corrupted. The marshaled data interpretation
functions of the security library detected more substitutional arguments than
indicated in the marshaled data's argument count. It is possible that the
application has inadvertently overwritten the variable containing the address
of the data, or the application may have inadvertently overwritten the memory
used to store the data. Verify that the application is providing the correct
address for the marshaled input data to this routine. Perform memory leak
and memory use verification tests on the application to ensure that the
application is not inadvertently modifying this memory.
2649-147 ctcasd Failure : The file permission bits of the HBA2 service mapping
file allow the file to be writable by other than the owner itself.
Name of the HBA2 service mapping file: %1$s
File mode bits as returned by stat(): 0x%2$08x
Source file name: %3$s(%4$d)
The ctcasd's HBA2 service mapping file provides the mapping between
service names and the user names used by the service's process during
their execution. The HBA2 service mapping file is installed by default
by RSCT and system administrators can customize it to fit their needs.
If the problem occurs with the overriding copy of the HBA2 service file ,
please make sure that the file is writable by root only. Otherwise, please
contact the IBM Customer Support and report this incident.
2649-125 ctcasd Daemon Failure: The daemon was unable to create an
initial trusted host list file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate systems within
the cluster. The daemon attempted to create the initial trusted host list
file in the following directory:
%1$s
The file system containing this directory does not have sufficient space to
create the initial trusted host list file. Contact the system administrator
and report this problem. System administrators should examine the file
system containing this directory for obsolete files that can be removed or
trimmed. The system administrator can also correct this problem by extending
he size of the file system containing this directory.
2649-115 ctcasd Daemon Failure: The daemon was unable to create an
initial public key file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon attempted to create the initial
public key file in the following directory:
%1$s
The file system containing this directory does not have sufficient space to
create the initial public key file. Contact the system administrator and
report this problem. System administrators should examine the file system
containing this directory for obsolete files that can be removed or trimmed.
The system administrator can also correct this problem by extending the size
of the file system containing this directory.
2649-114 ctcasd Daemon Failure: The daemon was unable to create an
initial private key file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon attempted to create the initial
private key file in the following directory:
%1$s
The file system containing this directory does not have sufficient space to
create the initial private key file. Contact the system administrator and
report this problem. System administrators should examine the file system
containing this directory for obsolete files that can be removed or trimmed.
The system administrator can also correct this problem by extending the size
of the file system containing this directory.
2649-124 ctcasd Daemon Failure: The daemon was unable to create an
initial trusted host list file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate systems within
the cluster. The daemon attempted to create the initial trusted host list
file in the following directory:
%1$s
A component directory in the above path name may be missing, or the access
permissions for one of these components may have been modified to forbid
access. Verify that the directory listed above exists, and that the
permissions on that directory permit processes running with root access to
access the directory and create files within the directory. If this condition
persists, contact the cluster software service provider and report this
incident.
2649-113 ctcasd Daemon Failure: The daemon was unable to create an
initial public key file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon attempted to create the initial
public key file in the following directory:
%1$s
A component directory in the above path name may be missing, or the access
permissions for one of these components may have been modified to forbid
access. Verify that the directory listed above exists, and that the
permissions on that directory permit processes running with root access to
access the directory and create files within the directory. If this condition
persists, contact the cluster software service provider and report this
incident.
2649-112 ctcasd Daemon Failure: The daemon was unable to create an
initial private key file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon attempted to create the initial
private key file in the following directory:
%1$s
A component directory in the above path name may be missing, or the access
permissions for one of these components may have been modified to forbid
access. Verify that the directory listed above exists, and that the
permissions on that directory permit processes running with root access to
access the directory and create files within the directory. If this condition
persists, contact the cluster software service provider and report this
incident.
2649-123 ctcasd Daemon Failure: The daemon was unable to locate or
access the trusted host list file to be used for host-based authentication.
Without this list, the daemon will be unable to authenticate systems within
the cluster. The daemon expected to find this file in the following directory:
%1$s
The trusted host list file may be missing, the permissions on the file may
have been modified to forbid any process from accessing the file, or a
component of the directory name may have been modified to forbid access.
Verify that the trusted host list file exists, and that the permissions on
the file and the directory are set to permit processes running with root
permission to access and modify the directory and the file. If this
condition persists, contact the cluster software service provider and report
this incident.
2649-110 ctcasd Daemon Failure: The daemon was unable to locate or
access the key files to be used for host-based authentication. Without
these files, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon expected to find these key
files in the following directory:
%1$s
The key files may be missing, the permissions on the files may have
been modified to forbid any process from accessing the files, or a component
of the directory name may have been modified to forbid access. Verify that
the public and private key files exist, and that the permissions on the files
and the directory are set to permit processes running with root permission
to access the directory and the files. If this condition persists, contact
the cluster software service provider and report this incident.
2649-142 ctcasd Failure : Memory allocation failure.
Attempted allocation: %1$d bytes
Source file name: %2$s(%3$d)
Most often, this failure occurs when a process exceeds its memory
allocation limit. In rare cases, this failure occurs when a number of
processes allocate huge amounts of memory and utilize all available
memory on the system.
Verify that the allocation itself is not exceeding ctcasd's own limit.
If it does not, contact IBM Customer Support and report this incident.
If another software application is exceeding its limit, examine the
software for memory management problems and memory leaks. If the
application is not exceeding its memory allocation limits, contact the
system administrator and report this incident. System administrators
should identify processes using excessive memory and consider
terminating these processes.
2649-126 ctcasd Daemon Failure: The daemon was unable to create an
initial trusted host list file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate systems within
the cluster. The daemon attempted to create the initial trusted host list
file in the following directory:
%1$s
This directory may reside in a read-only file system, one of the component
directories in this path name may be missing, the directory name may contain
more symbolic links than the operating system can support, or the path name
may not reference a directory. Contact the system administrator and report
this problem. System administrators should verify that the above directory
name is specified and constructed properly. If this condition persists,
contact the cluster software service provider and report this incident.
2649-117 ctcasd Daemon Failure: The daemon was unable to create an
initial public key file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon attempted to create the initial
public key file in the following directory:
%1$s
This directory may reside in a read-only file system, one of the component
directories in this path name may be missing, the directory name may contain
more symbolic links than the operating system can support, or the path name
may not reference a directory. Contact the system administrator and report
this problem. System administrators should verify that the above directory
name is specified and constructed properly. If this condition persists,
contact the cluster software service provider and report this incident.
2649-116 ctcasd Daemon Failure: The daemon was unable to create an
initial private key file to be used for host-based authentication.
Without this file, the daemon will be unable to authenticate the local system
to other systems in the cluster. The daemon attempted to create the initial
private key file in the following directory:
%1$s
This directory may reside in a read-only file system, one of the component
directories in this path name may be missing, the directory name may contain
more symbolic links than the operating system can support, or the path name
may not reference a directory. Contact the system administrator and report
this problem. System administrators should verify that the above directory
name is specified and constructed properly. If this condition persists,
contact the cluster software service provider and report this incident.
2649-102 libct_cas Memory allocation failure.
Function name: %1$s
Attempted allocation: %2$d bytes
Most often, this failure occurs when a process exceeds its memory allocation
limit. In rare cases, this failure occurs when a number of processes
allocate huge amounts of memory and utilize all available memory on the
system. Verify that the allocation itself is not exceeding its own limit.
If a Cluster software trusted service is exceeding its limit, contact IBM
Customer Support and report this incident. If another software application
is exceeding its limit, examine the software for memory management problems
and memory leaks. If the application is not exceeding its memory allocation
limits, contact the system administrator and report this incident. System
administrators should identify processes using excessive memory and consider
terminating these processes.
2649-050 unix_mpm : Memory allocation failure.
Function name: %1$s
Attempted allocation: %2$d bytes
Most often, this failure occurs when a process exceeds its memory allocation
limit. In rare cases, this failure occurs when a number of processes
allocate huge amounts of memory and utilize all available memory on the
system. Verify that the allocation itself is not exceeding its own limit.
If a Cluster software trusted service is exceeding its limit, contact IBM
Customer Support and report this incident. If another software application
is exceeding its limit, examine the software for memory management problems
and memory leaks. If the application is not exceeding its memory allocation
limits, contact the system administrator and report this incident. System
administrators should identify processes using excessive memory and consider
terminating these processes.
2649-136 libct_cas Failure: The marshaled data provided to this
routine is either not valid or corrupted. The most probable cause of this problem
is that the public key of the source host in the target's host THL file does not
match the private key of the source host. Another possible cause is that the
application has inadvertently overwritten the variable containing the address
of the data, or the application may have inadvertently overwritten the memory
used to store the data. Verify that the public keys in the THL files match
their corresponding private keys from the host listed in the THL records.
Also verify that the application is providing the correct address for the
marshaled input data to this routine. Perform memory leak and memory use
verification tests on the application to ensure that the application is not
inadvertently modifying this memory.
2649-028 %1$s Failure: Memory allocation failure.
Function name: %2$s
Attempted allocation: %3$d bytes
Most often, this failure occurs when a process exceeds its memory allocation
limit. In rare cases, this failure occurs when a number of processes
allocate huge amounts of memory and utilize all available memory on the
system. Verify that the allocation itself is not exceeding its own limit.
If a Cluster software trusted service is exceeding its limit, contact IBM
Customer Support and report this incident. If another software application
is exceeding its limit, examine the software for memory management problems
and memory leaks. If the application is not exceeding its memory allocation
limits, contact the system administrator and report this incident. System
administrators should identify processes using excessive memory and consider
terminating these processes.
2649-121 ctcasd Daemon Failure: the daemon detected a private key
file on the local system, but was unable to locate the associated public key
file on the local system. The daemon has concluded that the private and
public key configuration of the local system has been corrupted. The daemon
expected to find public key file in the following location:
%1$s
Inform the system administrator of this failure. System administrators
should recreate the public and private key files on the system. If cluster
security based keys are in use, these keys can be recreated using the
'ctskeygen' command. If secured remote shell keys are in use, consult the
documentation and procedures for configuring secured remote shell public and
private keys. System administrators should also consider monitoring the
status of the public and private key files, in case an application is
accidentally or intentionally removing these files.
2649-138 ctcasd Daemon Failure: the daemon detected a public key
file on the local system, but was unable to locate the associated private key
file on the local system. The daemon has concluded that the private and
public key configuration of the local system has been corrupted. The daemon
expected to find the private key file in the following location:
%1$s
Inform the system administrator of this failure. System administrators
should recreate the public and private key files on the system. If cluster
security based keys are in use, these keys can be recreated using the
'ctskeygen' command. If secured remote shell keys are in use, consult the
documentation and procedures for configuring secured remote shell public and
private keys. System administrators should also consider monitoring the
status of the public and private key files, in case an application is
accidentally or intentionally removing these files.
2649-122 ctcasd Daemon Failure: the daemon detected a public key
file on the local system, but was unable to locate the associated private key
file on the local system. The daemon has concluded that the private and
public key configuration of the local system has been corrupted. The daemon
expected to find both the public and the private key files in the following
directory:
%1$s
Inform the system administrator of this failure. System administrators
should recreate the public and private key files on the system. If cluster
security based keys are in use, these keys can be recreated using the
'ctskeygen' command. If secured remote shell keys are in use, consult the
documentation and procedures for configuring secured remote shell public and
private keys. System administrators should also consider monitoring the
status of the public and private key files, in case an application is
accidentally or intentionally removing these files.
2649-081 %1$s Failure: Unable to acquire credentials for a service
application. The application provided a service name that is not recognized
as a trusted service.
Service Name: %2$s
Verify that the proper service name was used. Contact the system
administrator to verify that the application name is listed as a trusted
service. Administrators should check the contents of this file to ensure
that the service name shown above is listed:
/var/ct/cfg/hba2.map
If this file does not exist, administrators should check the default file:
/opt/rsct/cfg/hba2.mpm
If the service name is not listed in this file, the security subsystem will
be unable to acquire credentials for this application. To add the service
name to this list, modify the file /var/ct/cfg/hba2.mpm. Do not modify the
default file /opt/rsct/cfg/hba2.mpm. To create /var/ct/cfg/hba2.mpm,
copy the contents of the default file /opt/rsct/cfg/hba2.mpm to this
location. If the problem persists after making these modifications, contact
IBM Customer Support and report this incident.
src D_SEC ctcasd select strtold cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cas__itoa strtoimax srcfilename cas__reverse getdtablesize /var/ct/IW/soc /var/ct/IW/run cas__trace_exit cas__release_xdata cas__marshal_xdata cas__release_buffer cas__marshal_xdata() /var/ct/IW/soc/ctcas /var/ct/IW/soc/ctcas /var/ct/IW/soc/ctcas /var/ct/IW/run/ctcas /var/ct/IW/run/ctcas /var/ct/IW/run/ctcas /var/ct/IW/run/ctcas /var/ct/IW/run/ctcas /var/ct/IW/run/ctcas cas__unmarshal_xdata cas__create_directory cas__unmarshal_xdata() cas__unmarshal_xdata() cas__add_elem_to_dllist cas__rem_elem_from_dllist /var/ct/IW/soc/ctcas/client /var/ct/IW/soc/ctcas/server /var/ct/IW/soc/ctcas/server /var/ct/IW/soc/ctcas/server cas__check_current_directory cas__check_socket_directories cas__insert_elem_before_dllist ../../../../../../src/rsct/security/CAS/bin/ctcas_utils.c ../../../../../../src/rsct/security/CAS/bin/ctcas_utils.c @(#)98 1.12.1.2 src/rsct/security/CAS/bin/ctcas_utils.c, ctsec, rsct_rady, rady2035a 9/24/09 15:02:22
#######################################################################
# Licensed Materials - Property of IBM #
# #
# 5765-F07 #
# #
# (C) COPYRIGHT International Business Machines Corp. 1996,2001 #
# All Rights Reserved #
# #
# US Government Users Restricted Rights - Use, duplication or #
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. #
# #
#######################################################################
src _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC _SEC poll poll() poll() send() send() poll() poll() recv() recv() select strtold cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat cthba.cat strtoimax srcfilename getdtablesize cas__send_data _cas__send_data _cas__send_data cas__receive_data _cas__receive_data _cas__receive_data _cas__check_socket_for_writing _cas__check_socket_for_reading _cas__check_socket_for_reading _cas__check_socket_for_writing ../../../../../../src/rsct/security/CAS/bin/ctcas_comm.c @(#)99 1.11 src/rsct/security/CAS/bin/ctcas_comm.c, ctsec, rsct_rady, rady2035a 8/4/08 10:52:36
#######################################################################
# Licensed Materials - Property of IBM #
# #
# 5765-F07 #
# #
# (C) COPYRIGHT International Business Machines Corp. 1996,2001 #
# All Rights Reserved #
# #
# US Government Users Restricted Rights - Use, duplication or #
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. #
# #
#######################################################################
P Eh
$
(
,
0 E ( 4 k environ @ errno @ chdir @
chmod @
close @
mkdir @
setreuid @
unlink @
socket @
@ @ ___fill @ @ _iob @ malloc @
realloc @
free @
_Errno @
exit @
strlen @
fprintf @
geteuid @
getuid @
sprintf @
getpid @
time @
strncmp @
strrchr @
' @
3 @
strdup @
stat64 @
__assert @
getopt @
putenv @
send @
connect @
recv @
? @
__crt0v @ L @ i @
v @ srcstat @
srcstrt @
@
@
@
@
@
@
__start !
$
0
4
8
<
@
D
H
L
P
T
X
\
`
d
h
l
p
t
x
|
$ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x | $ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x | $ ( , 0 4 8 < @ D H L P T X 0 < * @ ) D H - L , P + T X \ ` d h # l p ! t % x | $ . 0 1 3 4 2 / ' "
5 & ( $ /usr/lib:/lib libc.a shr.o libpthread.a shr_xpg5.o libsrc.a shr.o libct_cu.a shr.o libct_tr.a shr.o
___memset ___memmove
___strcpy
__fd_poll
nanosleep __mod_init __malloc_user_defined_name __pth_init
__pthread cu_set_error_1 cu_get_error_1 cu_rel_error_1 cu_get_errmsg_1 cu_rel_errmsg_1 tr_record_data_1 __default_char:t322=-5
:t119=-10 int64_t:t2=-31 intmax_t:t3=2 :t11=ar0;0;9;5 :t13=ar0;0;2047;-4 &fd_set:T14=s8192fds_bits:13,0,65536;; fd_set:t15=14 time_t:t17=-1 suseconds_t:t18=-1 0timeval:T19=s8tv_sec:17,0,32;tv_usec:18,32,32;;
:t21=f-1; :t22=ar0;0;6;5 :t24=ar0;0;13;5 :t26=f-13; :t27=ar0;0;7;5 :t29=ar0;0;11;5 :t31=ar0;0;4;5 uint_t:t33=-8
uid_t:t34=33 :t36=ar0;0;4095;-2 uchar_t:t40=-5 sa_family_t:t41=40 :t42=ar0;0;103;-2 Lsockaddr_un_s:T43=s106sun_len:40,0,8;sun_family:41,8,8;sun_path:42,16,832;; :t44=ar0;0;3;-2 Rsrchdr:T45=s114retaddr:43,0,848;pad:44,848,32;dversion:-3,880,16;cont:-3,896,16;; :t46=ar0;0;64;-2 :t47=ar0;0;29;-2 Xstatcode:T48=s100objtype:-3,0,16;status:-3,16,16;objtext:46,32,520;objname:47,552,240;; :t49=ar0;0;0;48 6statrep:T50=s214srchdr:45,0,912;statcode:49,912,800;; int32long64_t:t52=-1
pid_t:t53=52 int32_t:t54=-1 ct_int32_t:t55=54 ct_char_t:t56=-2 uint32_t:t58=-8 ct_uint32_t:t59=58 :T60=e-1:CU_ERROR_ARG_INT:0,CU_ERROR_ARG_LONG:1,CU_ERROR_ARG_LONG_LONG:2,CU_ERROR_ARG_DOUBLE:3,CU_ERROR_ARG_RESERVED:4,CU_ERROR_ARG_CHAR_STR:5,CU_ERROR_ARG_VOID_PTR:6,; cu_error_arg_type_t:t61=60
:t64=*-11 :T65=u8cu_arg_int:-1,0,32;cu_arg_long:-4,0,32;cu_arg_long_long:-31,0,64;cu_arg_double:-13,0,64;cu_arg_char_str:7,0,32;cu_arg_void_ptr:64,0,32;; cu_error_arg_value_t:t66=65 4:T67=s16cu_arg_type:61,0,32;cu_arg_value:66,64,64;; cu_error_arg_t:t68=67 :T70=s32cu_error_id:55,0,32;cu_ffdc_id:57,32,32;cu_msg_cat:57,64,32;cu_msg_set:55,96,32;cu_msg_num:55,128,32;cu_msg_default:57,160,32;cu_arg_cnt:59,192,32;cu_args:69,224,32;; cu_error_t:t71=70 :t73=ar0;0;0;-2 :t74=ar0;0;0;-2 1timespec:T75=s8tv_sec:17,0,32;tv_nsec:-4,32,32;; :t76=ar0;0;1022;-2 Lsockaddr_un:T77=s1025sun_len:40,0,8;sun_family:41,8,8;sun_path:76,16,8184;; cas_header_s:T78=s32hdr_magic:59,0,32;hdr_version:59,32,32;hdr_service:59,64,32;hdr_msgtype:59,96,32;hdr_rcode:59,128,32;hdr_reserved1:59,160,32;hdr_reserved2:59,192,32;hdr_reserved3:59,224,32;; cas_header_desc:t79=78 3sec_buffer_s:T80=s8length:55,0,32;value:64,32,32;; sec_buffer_desc:t81=80 5cas_xdata_s:T82=s40header:79,0,256;xdata:81,256,64;; cas_xdata_desc:t83=82 :t84=f-11; :t85=ar0;0;24;5 :t86=ar0;0;64;-2 cas_xdata_t:t89=88 sec_buffer_t:t92=91
:t102=*72
:t104=k56 :t105=*104 :t106=f55; :t107=ar0;0;878;5
:t108=k-5 :t109=ar0;0;4;108 :t110=ar0;0;2;108
:t111=*-1 :t112=f111; :t113=ar0;0;J;7 :t115=ar0;0;13;-2 Esockaddr:T116=s16sa_len:40,0,8;sa_family:41,8,8;sa_data:115,16,112;; :t117=k116 :t118=*117 __ulong32_t:t120=-10 socklen_t:t121=120 size_t:t126=-10 :t132=f64;
:t134=*-5 :T135=s32_ptr:134,0,32;_cnt:-1,32,32;_base:134,64,32;_bufendp:134,96,32;_flag:-3,128,16;_file:-3,144,16;__stdioid:-1,160,32;__newbase:7,192,32;_lock:64,224,32;; FILE:t136=135 :t137=*136 :t139=ar0;0;15;136 :t147=*146 :t149=f34;
:t153=k75 :t154=*153
:t155=*75 cas__clean_trace_environ:F-11
envvars:8
envvar:86 varcount:-1
__func__:V85 ssStatus:T37=s0; replyLength:-3
buffer:36 srcContinue:-1 nostats:-1 pResultStatus:38 pNewResult:38
pInput:51
__func__:V31
srcenv:73 srcargs:74
sockfd:-1
noretries:-1 progression:-1 sock_un:77 dummyreq:83 rsct_copyright:V107 CLiC_RSA_PUB_EXP_FERMAT4:V109 CLiC_RSA_PUB_EXP_3:V110
sccsid:V7 progname:G7
validopts:G7 alltheway:G-1 verbose:G-1 __default_char:t204=-5
:t7=f-13; :t8=ar0;0;7;3 int64_t:t10=-31 intmax_t:t11=10
:t13=f11; :t14=ar0;0;9;3 :t16=ar0;0;2047;-4 &fd_set:T17=s8192fds_bits:16,0,65536;; fd_set:t18=17 time_t:t20=-1 suseconds_t:t21=-1 0timeval:T22=s8tv_sec:20,0,32;tv_usec:21,32,32;;
:t24=f-1; :t25=ar0;0;6;3 :t27=ar0;0;13;3
:t29=*-11 ulong_t:t31=-10 :t33=ar0;0;4;3 :t35=ar0;0;11;3 :t37=ar0;0;30;3 :t38=ar0;0;63;-2 ushort_t:t40=-7 ushort:t41=40 @pollfd:T42=s8fd:-4,0,32;reqevents:41,32,16;rtnevents:41,48,16;; int32_t:t43=-1 ct_int32_t:t44=43 3sec_buffer_s:T45=s8length:44,0,32;value:29,32,32;; sec_buffer_t:t47=46 :t49=ar0;0;15;3 :t50=ar0;0;63;-2 uint32_t:t52=-8 ct_uint32_t:t53=52 :t55=ar0;0;14;3 :t57=ar0;0;30;3 :t58=ar0;0;63;-2 :t60=ar0;0;18;3 :t61=ar0;0;63;-2 :t63=ar0;0;17;3 tr_detail_level_t:t65=-5 :t66=ar0;0;J;65
:t69=f44; size_t:t71=-10
:t72=f71; :t74=ar0;0;4;73 :t75=ar0;0;2;73 ct_char_t:t76=-2
:t81=f20; :t82=ar0;0;878;3 :t83=ar0;0;J;5 ssize_t:t84=-4
:t85=k-11
:t87=f84;
:t91=f90;
:t95=f29; :t96=f-11; __listptr:p29 __nfds:p31 __timeout:p-4
__func__:V33 #_cas__check_socket_for_reading:F-1 toutval:p-1 timeout:20
timestamp:20 traceroutine:58
__func__:V57 #_cas__check_socket_for_writing:F-1 traceroutine:38
__func__:V37 _cas__send_data:F-1
nbytes:-1 traceroutine:50
__func__:V49 cas__send_data:F-1
__func__:V55 _cas__receive_data:F-1 traceroutine:61
__func__:V60 cas__receive_data:F-1
__func__:V63 CLiC_RSA_PUB_EXP_FERMAT4:V74 CLiC_RSA_PUB_EXP_3:V75 rsct_copyright:V82
sccsid:V5 __default_char:t294=-5 :t29=ar0;0;11;3 int32_t:t30=-1 ct_int32_t:t31=30
:t32=f31; :t33=ar0;0;25;3 ct_char_t:t34=-2 uint32_t:t37=-8 ct_uint32_t:t38=37 :T39=e-1:CU_ERROR_ARG_INT:0,CU_ERROR_ARG_LONG:1,CU_ERROR_ARG_LONG_LONG:2,CU_ERROR_ARG_DOUBLE:3,CU_ERROR_ARG_RESERVED:4,CU_ERROR_ARG_CHAR_STR:5,CU_ERROR_ARG_VOID_PTR:6,; cu_error_arg_type_t:t40=39
:t43=*-11 :T44=u8cu_arg_int:-1,0,32;cu_arg_long:-4,0,32;cu_arg_long_long:-31,0,64;cu_arg_double:-13,0,64;cu_arg_char_str:5,0,32;cu_arg_void_ptr:43,0,32;; cu_error_arg_value_t:t45=44 4:T46=s16cu_arg_type:40,0,32;cu_arg_value:45,64,64;; cu_error_arg_t:t47=46 :T49=s32cu_error_id:31,0,32;cu_ffdc_id:35,32,32;cu_msg_cat:35,64,32;cu_msg_set:31,96,32;cu_msg_num:31,128,32;cu_msg_default:35,160,32;cu_arg_cnt:38,192,32;cu_args:48,224,32;; cu_error_t:t50=49 :t53=ar0;0;16;3 __ulong64_t:t54=-8
dev_t:t55=54
ino_t:t56=54 uint_t:t57=-8 mode_t:t58=57 nlink_t:t60=-3 ushort_t:t62=-7
uid_t:t63=57
gid_t:t64=57 soff_t:t65=-1 1timespec:T66=s8tv_sec:20,0,32;tv_nsec:-4,32,32;; __long64_t:t67=-1 blksize_t:t68=67 blkcnt_t:t69=67 :t70=ar0;0;9;57 off64_t:t71=-31 }stat64:T72=s128st_dev:55,0,32;st_ino:56,32,32;st_mode:58,64,32;st_nlink:60,96,16;st_flag:62,112,16;st_uid:63,128,32;st_gid:64,160,32;st_rdev:55,192,32;st_ssize:65,224,32;st_atim:66,256,64;st_mtim:66,320,64;st_ctim:66,384,64;st_blksize:68,448,32;st_blocks:69,480,32;st_vfstype:-1,512,32;st_vfs:57,544,32;st_type:57,576,32;st_gen:57,608,32;st_reserved:70,640,320;st_size:71,960,64;; :t73=ar0;0;1022;-2 :t74=ar0;0;1022;-2 size_t:t76=-10 :t77=ar0;0;1022;-2 :t78=ar0;0;256;-2 :t79=ar0;0;256;-2 :t80=ar0;0;256;-2 :t81=ar0;0;256;-2 :t82=ar0;0;256;-2 uint:t83=57 uint64_t:t86=-32 ct_uint64_t:t87=86 :cu_timeinfo:T88=s16timeinfo1:87,0,64;timeinfo2:87,64,64;; cu_timeinfo_t:t89=88 :t90=ar0;0;0;-2 tr_detail_level_t:t92=-5 :t93=ar0;0;3;92 tr_category_description:T94=s16category_id:38,0,32;category_name:35,32,32;default_level_of_detail:38,64,32;minimum_level_of_detail:38,96,32;; !tr_category_description_t:t95=94 :t96=ar0;0;3;95 :t98=ar0;0;4;97 :t99=ar0;0;2;97
:t100=k38
:t101=k38
:t103=k34 :t104=*103
:t108=*38
:t110=k38
:t112=*92
:t113=k95 :t114=*113
:t115=k38
:t117=*89 :t119=f-11;
:t120=*35
:t123=*51 :t127=ar0;0;878;3 :t129=ar0;0;J;5
:t130=*72 :t132=f58; :t138=f76; cas__trace_detail_levels:G93 __default_char:t282=-5 cas__dlink_elem_s:T39=s0;
:t136=-13
:t125=-10 int32_t:t31=-1 ct_int32_t:t32=31
:t33=*-11 3sec_buffer_s:T34=s8length:32,0,32;value:33,32,32;; sec_buffer_t:t36=35 :t37=f-11; :t38=ar0;0;19;3 5cas__dlink_elem_s:T39=s8prev:40,0,32;next:40,32,32;; cas__dlink_elem_t:t41=40 :t44=ar0;0;25;3 :t46=ar0;0;23;3 :t48=ar0;0;30;3 uint32_t:t50=-8 ct_uint32_t:t51=50 cas_header_s:T52=s32hdr_magic:51,0,32;hdr_version:51,32,32;hdr_service:51,64,32;hdr_msgtype:51,96,32;hdr_rcode:51,128,32;hdr_reserved1:51,160,32;hdr_reserved2:51,192,32;hdr_reserved3:51,224,32;; cas_header_desc:t53=52 sec_buffer_desc:t54=34 5cas_xdata_s:T55=s40header:53,0,256;xdata:54,256,64;; cas_xdata_t:t57=56 :t59=ar0;0;18;3 :t61=ar0;0;20;3 :t63=ar0;0;18;3 uint_t:t64=-8 uint:t65=64 :t67=ar0;0;21;3 :t69=ar0;0;29;3 __ulong64_t:t70=-8
dev_t:t71=70
ino_t:t72=70 mode_t:t73=64 nlink_t:t75=-3 ushort_t:t77=-7
uid_t:t78=64
gid_t:t79=64 soff_t:t80=-1 1timespec:T81=s8tv_sec:20,0,32;tv_nsec:-4,32,32;; __long64_t:t82=-1 blksize_t:t83=82 blkcnt_t:t84=82 :t85=ar0;0;9;64 off64_t:t86=-31 }stat64:T87=s128st_dev:71,0,32;st_ino:72,32,32;st_mode:73,64,32;st_nlink:75,96,16;st_flag:77,112,16;st_uid:78,128,32;st_gid:79,160,32;st_rdev:71,192,32;st_ssize:80,224,32;st_atim:81,256,64;st_mtim:81,320,64;st_ctim:81,384,64;st_blksize:83,448,32;st_blocks:84,480,32;st_vfstype:-1,512,32;st_vfs:64,544,32;st_type:64,576,32;st_gen:64,608,32;st_reserved:85,640,320;st_size:86,960,64;; :t89=ar0;0;28;3 :t91=ar0;0;15;3 :t92=ar0;0;7;-2 int32long64_t:t93=-1
pid_t:t94=93 :t96=ar0;0;12;3 :t98=ar0;0;9;3 tr_detail_level_t:t100=-5 :t101=ar0;0;J;100
:t102=k51
:t103=k51 :t104=f32;
:t105=k-5 :t106=ar0;0;4;105 :t107=ar0;0;2;105 ct_char_t:t108=-2 :t109=k108 :t110=*109
:t112=*-1 :t113=f112; :t116=f94; :t118=ar0;0;878;3 :t119=ar0;0;J;5
:t121=*87 :t127=f126; :t128=f33; :t129=k-11 :t130=*129 $cas__insert_elem_before_dllist:F-11
queue:p42
__func__:V48 cas__rem_elem_from_dllist:F-11
__func__:V44 cas__add_elem_to_dllist:F-11
__func__:V46 cas__marshal_xdata:F-1
__func__:V59 cas__unmarshal_xdata:F-1
__func__:V61 cas__create_directory:F-1 dirname:p5
__func__:V67 "cas__check_socket_directories:F-1 bitmask:65 bitmask2:65
__func__:V69 !cas__check_current_directory:F-1
__func__:V89 cas__reverse:F-11
__func__:V96 cas__itoa:F-11
__func__:V98 cas__trace_exit:F-11
__func__:V91 progname:92 cas__release_buffer:F-11
__func__:V38 cas__release_xdata:F-11 CLiC_RSA_PUB_EXP_FERMAT4:V106 CLiC_RSA_PUB_EXP_3:V107 rsct_copyright:V118 __default_char:t16=-5 :t2=ar0;0;40;-2 :t4=ar0;0;202;3 cu_mesgtbl_cthba_msg:G4 R V p n r r t v z z | 2 B n
H v x ~ 7 < $ A @ F h A - $ K d A P V ~ Z d U p Z _ d i j i _ n , _ s x
}
,
8
N
^
| s
x
}
s $ x 4 } > H T ` t _ _ s x } & 0 < H j z s x }
, s
8 x
H }
R
\
h
t
s x } < 0 X 4 D p V x ( } 2 < H T p x } " 0 x @ } J T ` l g x } , ؙ 8 ؙ D s s , s 8 x H } R \ h t * R z - ( : b * R z B j
2 Z 2 n s < s D ( p ( ( ( ( ( L ( x ( ( ( !R ! ! s ! ! s " - "4 ( "` ( " ( " ( " ( # ( #< ( #h ( # ( # < # $ s $< ( $ $ ܙ $ $ % s %4 %F %P %x s & & ȏ &x י & & s & י ' '\ י ' (: (> ȏ ( י ( ( ( ) )( s )X י )z ) s ) ) ) * s * ,r ,v , , - - ҙ .P - .` ҙ .t - / " / , /F /n / / / 0 06 0^ 0 1$ 1v 1 1 1 1 2 Ù 2H 2d Ù 2 2 2 s 2 3 s 3F 3h s 3 3 3 4V 4p 4z 4 4 4 Ù 5, 5H Ù 5 5 5 s 5 5 s 6* 6L s 6f 6 6 76 7T 7^ 7 7 7 ș 8 8 8@ s 8R 8 8 8 9 s 9 9l 9 9 ș : : :0 s :B : : : : s ; ;` ; ; ; ; < < < = =( = ͙ = = = > s >2 > > > > s > ?P ?t ? < @ @4 s @F @ @ A$ ͙ A< AV A\ A s A A B B. BH s BZ B B CD ҙ Cb C C D D D 4 D D E E> :
$ :
0
4
8
<
@
D
H
L
P
T
X
\
`
d
h
l
p
t
x
|
$ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x | $ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x | $ ( , 0 4 8 < @ D H L P T X 0 0 n n n < j @ h D H L P l T X : \ ` P d 8 h \ l : p X t ` x 8 | F H R B E ^ H K
6 D V > $ J d Z " B L < T 0 N b f $ @ ,
0 L p x < l x ! d p |
h x | # % & ' ( ) * ( + 4 , @ 0 T 1 l 2 3 8 : <
<
=
( >
4 >
@ @
H @
L H
\ J
L
L
M
N
N
P
P
T
U
V
X Z , Z < [ P \ \ \ h _ | ` b c d f h h $ i 8 j D j P l X m \ m h u x w y y z { { } ~
4
@
P
d
p
|
$ ( 0 4 8 1 T ` d h t | ' $ , 0 D L p x | , D X d h 0 D P \ d h , 8 H \
h
t | # ($ 4% @& L) X) \* + - . / 1 2 5 6 49 @9 P: d; p; |> ? 1 10 1 1 1 1 1 1 1 1 2 2 2
2$ 28
2H 2\ 2 2 2 2 2 2 2 3 3 3 3( 38 3@ 3D ! 3p # 3x # 3| 3 ' 3 ' 3 ' 3 ( 3 ) 4` 4h 4x 4 4 4 4 4 4 4 4
5 5
5, 5@ 5p 5| 5 5 5 5 5 5 5 6 6 6 6$ 6( ! 6T # 6\ # 6` 6d ' 6 ' 6 ' 6 ( 6 ) 7D 7L 7\ 7 7 7 7
7
7 8 8
8H 8P 8 8 8 8 9 9 9d 9h 9 9 9 9 9 : :8 :@ : : : ! : " : % ; % ;X % ;\ % ; ' ; * ; * ; * ; + ; , ( >0 > > > > > > > ?H ?L ?| ? ? ? ? # ? # ? $ ? & ? ( ? ( ? * @ + @< . @D . @ . @ . @ / @ 2 @ 3 @ 4 @ 5 A 5 A 6 A< 7 AP 7 AT 8 A ; A ; A ; A ; B < B = B, > BP @ BX @ B @ B @ B A B C B C C 4 C F C I C< I CL J CX J C` M C M C M C N C O " D4 DH +
: l | , H V < H P \ ` l
, 8 L X d x ! " # $ % & ' ( ( 4 ) @ * T + ` , l - / 0 1 2 3 4 6 8 9 g !\ !d !p !t ! ! ! ! ! ! " " " "( "< "H "T "h "t " " " " " " ! " " " # " $ # % # & #$ ' #0 ( #D ) #P * #\ + #p , #| . # / # 0 # 1 # 2 # 3 # 4 $ 7 $$ 7 $( 9 $D < $H > $P ? x $ $ $ % %( %,
%D % % % % % & &$ &P &X &` # &l # &p % & ) & + & + & . & / ' / ' 0 ', 1 '0 4 '@ 5 'D 8 'P 8 'T : ' ; ' ; ' < ' = ' ? ' A ' B (@ (H (t (| ( ( (
( ( ( ( ( ( )0 )8 )< )@ ! )L ! )P # )x ' ) ) ) ) ) , ) - ) / ) 1 ) 5 * 8 * ; * < * * * * * + +t + + + + + + , ,
,( ,t , , , , - - -$ -p -| - - - - . . .< .X .h .| srcstat
srcstrt
"
1
A
Q
b
m environ errno chdir
chmod
close
mkdir
setreuid
unlink
socket
w ___fill .___fill _iob malloc
realloc
free
_Errno
exit
strlen
fprintf
geteuid
getuid
sprintf
getpid
time
strncmp
strrchr
strdup
stat64
__assert
getopt
putenv
send
connect
recv
__crt0v TOC k __crt0v < k @ k D k m H k b L k P k errno T k _$STATIC X k environ \ k strncmp ` k malloc d k __assert h k realloc l k strdup p k putenv t k x k geteuid | k getuid k setreuid k strrchr k progname k k getopt k k verbose k srcstat k k k k 1 k _iob k fprintf k A k " k srcstrt k k _Errno k socket k sprintf k connect k close k _$STATIC k mkdir k chmod k k stat64 k unlink k chdir k strlen k % k getpid k Q k free k k _$STATIC k time k send k recv k exit $ k g > g .__start P k .__start P __start
k , p_xargc p_xargv 0 p_xrcfg 4 p_xrc 8 I c ( .file g x k 9 @ k _$STATIC 0 k e
, $ B ( T , .file N g n :t63=-11 :t62=-13 :t39=-5 :t35=-3 :t32=-8 :t25=-13 :t12=-4 :t9=-1 :t4=-2 :t1=-31 ' 8 :t5=k-2 :t6=*5 :t7=*-2 :t8=*7 :t10=f3; H Y n :t16=*15 :t20=*19 , 9 :t28=f7; J \ m } ) ; ! :t51=*50 Y p :t57=*56 D b :t69=*68 a :t72=*71 u /
B [ :t88=*82 :t91=*80 :t99=*57 , 9 M Y m
"
9
N
`
m
y , 9 :t146=k7 N [ h t :t323=Z k 9 x .bf e cp:8 @ D H .bs : .es .bb d tcp:7 .bb 0 d p:64 .eb x d .eb x d .ef e .main @
| L 8 main:F-1 0 .bf d e 4 :t38=*37 argc:p-1 argv:p8 euid:34 @ ruid:34 D H L once:-1 L c:-1 P rc:-1 T rc2:-1 X \ # ` 0 d C S h .bs : _ , .es .bb @ d _ i:-1 8 pid:53 .bb d k err:72 errmsg:7 .eb
@ d r .bb
\ d { err:72 x errmsg:7 | .eb
d .bb
d n T z U .bb
d err:72 p errmsg:7 t .eb h d .bb d err:72 h errmsg:7 l .eb P d .bb x d err:72 ` errmsg:7 d .eb d .bb
d err:72 X errmsg:7 \ .eb
| d .eb
d .bb
d rqt:75 @ rmt:75 H .eb $ d .eb d d .bb d err:72 0 errmsg:7 4 .eb d .bb $ d p t x | .bb d rqt:75 rmt:75 .eb d .bb d reply:83 in:81 out:81 .bb d ' err:72 errmsg:7 .eb \ d , .bb d 1 err:72 errmsg:7 .eb d 6 .bb , d < err:72 errmsg:7 .eb t d A .bb d F err:72 errmsg:7 .eb d K .eb L d Z .bb d ^ err:72 errmsg:7 .eb | d o .eb | d p .ef e r Eh k _$STATIC k .bs : $
.es progname
*
$
8
(
G verbose
,
W .file 8 g ; U z l U m
e :t97=-13 :t64=-5 :t51=-8 :t39=-7 :t30=-10 :t28=-11 :t15=-4 :t12=-1 :t9=-31 :t2=-2 :t1=-13 :t3=k-2 :t4=*3 :t5=*-2 :t6=*5
~
:t19=*18 ( 8 M :t23=*22 :t34=f5; & 6 x :t46=*45
4 F X k } :t67=k53 :t68=k53 :t73=k-5
:t77=k76 :t78=*77 :t80=*20 / ; N _ p :t86=*85 | :t90=*-1 :t205=Z 1 k 9 .poll 1 k \ z poll:F-1 i .bf 1 e k X \ ` .bs 0 .es .ef 1@ e l 1` ` .bf 1 e sock:p-1 rc:-1 @ pfd:42 H P ) T 8 X .bs 0 J | .es .ef 4 e 4@ p Y @ * .bf 4` e . sock:p-1 rc:-1 @ ~ D .bs 0 .es .bb 4 d 3 ) pfd:42 .eb 6d d S .ef 6 e V 7 T X .bf 7D e Z sock:p-1 buff:p47 rc:-1 @ D H .bs 0 .es .bb 7 d _ nuint:53 .eb ; d .ef < e <@ \ \ @ .bf P ` n ! ! !& !Y !m ! ! ! ! #5 #G #Y #k # # # # # # # # $ $ $) $= $Q $^ $k $w $ $ $ $
N $ $ $ $ :t283=Z k 9 r : ) $ [ .bf e ` elem:p41 h % l tmp:41 @ .bs %+ .es .ef ( e i ` H ) %: 2 .bf l e 7 elem:p41 h % l .bs %[ .es .ef 8 e L V ) %j N .bf e S elem:p41 X % \ .bs % .es .ef e Y 6 D g ) % m .bf < e o data:p57 x out:p36 | cp:5 @ nuint:51 D rc:32 H .bs % @ .es .ef ! e J !@ T ^ x ) % .bf !\ e in:p36 x data:p57 | cp:5 @ nuint:51 D rc:32 H .bs % X .es .ef $h e ` $ D ) % .bf $ e & x mode:p65 | rc:-1 @ .bs & p .es .ef % e w & ) &"
.bf & e rc:-1 @ sinfo:87 H &F &S .bs &a | .es .ef ' e Y ( P ) &p [ .bf (@ e ] rc:-1 @ sinfo:87 H &F .bs & \ .es .ef *@ e * : ) & .bf * e s:p5 h c:-1 @ i:-1 D j:-1 H .bs & .es .ef +8 e +` d ) & .bf +t e n:p-1 h s:p5 l i:-1 @ sign:-1 D .bs & .es .ef ,@ e ,` ) & .bf ,t e .bs & .es .bb , d ' @ pid:94 H .eb - d .ef -8 e -` ) ' % .bf -p e ( buf:p36 X .bs '4 T .es .ef - e . . ) 'C .bf . e data:p57 X .bs X , .es .ef . e E k _$STATIC k .bs '] '} ' .es .file
g ' :t1=-2 ' :t3=*-2 ' _$STATIC ` k ׯ
0 , ' .file g Y k 9 s _$STATIC k U t
strcat.s g .strcat 8 ) strcpy.s g .strcpy D ! g .strncpy % ) moveeq.s , g .bcopy / A ) .ovbcopy / " ._moveeq / " .memcpy / " .memmove / " memset.s / g .memset ) glink.s 4 g .exit E< k ( .exit E< 0 glink.s 9 g .strncmp k ( .strncmp 5 glink.s > g .malloc ( k ( .malloc ( : glink.s C g P k ( P ? glink.s H g .realloc x k ( .realloc x D glink.s M g .strdup 8 k ( .strdup 8 I glink.s R g .putenv ` k ( .putenv ` N glink.s W g .geteuid k ( .geteuid S glink.s \ g .getuid k ( .getuid X glink.s a g k ( ] glink.s f g .strrchr k ( .strrchr b glink.s k g .getopt ( k ( .getopt ( g glink.s p g .srcstat P k ( .srcstat P l glink.s u g x k ( x q glink.s z g k ( v glink.s g k ( { glink.s g .fprintf k ( .fprintf glink.s g k ( glink.s g @ k ( @ glink.s g .srcstrt h k ( .srcstrt h glink.s g k ( glink.s g ._Errno k ( ._Errno glink.s g .socket k ( .socket glink.s g .sprintf k ( .sprintf glink.s g .connect 0 k ( .connect 0 glink.s g .close X k ( .close X glink.s g D k ( D glink.s g .strlen 0 k ( .strlen 0 glink.s g 0\ k ( 0\ glink.s g .time D k ( .time D glink.s g .send D k ( .send D glink.s g .recv E k ( .recv E glink.s g .free 0 k ( .free 0 glink.s g .stat64 / k ( .stat64 / glink.s g .mkdir /D k ( .mkdir /D glink.s g .chmod /l k ( .chmod /l glink.s g .unlink / k ( .unlink / glink.s g .chdir / k ( .chdir / glink.s g .getpid 04 k ( .getpid 04 glink.s g - k ( - 9cu_set_error_1 cu_get_error_1 cu_rel_error_1 cu_get_errmsg_1 cu_rel_errmsg_1 tr_record_data_1 __pth_init __pthread ___memset .___memset ___memmove .___memmove ___strcpy .___strcpy __fd_poll nanosleep __mod_init __malloc_user_defined_name crt0_data validopts alltheway cu_mesgtbl_cthba_msg cas__trace_detail_levels crt0main.s _malloc_user_defined_name __C_runtime_pstartup ../../../../../../../src/bos/usr/ccs/lib/libc/__threads_init.c Sat Aug 7 17:38:28 2010 IBM XL C for AIX, Version 11.1.0.1 .__threads_init .__threads_init@AF2_1 _bsd_init_routine _xti_tli_init_routine _nsl_init_routine __dce_compat_init_routine ../../../../../../src/rsct/security/CAS/bin/ctcas_strtcasd.c Thu Mar 3 13:29:02 2022 IBM XL C for AIX, Version 12.1.0.0 .cas__clean_trace_environ ../../../../../../src/rsct/security/CAS/bin/ctcas_comm.c Thu Mar 3 13:28:59 2022 /project/sprelady/build/radys004a/tools/power/power/bosdeps/ibm/7.1.0/usr/include/sys/poll.h ._cas__check_socket_for_reading ._cas__check_socket_for_writing ._cas__send_data .cas__send_data ._cas__receive_data .cas__receive_data ../../../../../../src/rsct/security/CAS/bin/ctcas_trace.c Thu Mar 3 13:28:57 2022 ../../../../../../src/rsct/security/CAS/bin/ctcas_utils.c Thu Mar 3 13:28:58 2022 .cas__insert_elem_before_dllist .cas__rem_elem_from_dllist .cas__add_elem_to_dllist .cas__marshal_xdata .cas__unmarshal_xdata .cas__create_directory .cas__check_socket_directories .cas__check_current_directory .cas__reverse .cas__itoa .cas__trace_exit .cas__release_buffer .cas__release_xdata ../lib/cthba_msg.c ../../../../../../../../src/bos/usr/ccs/lib/libpthreads/init.c Sat Aug 7 17:46:00 2010 .call_pth_init __pth_init_routine strncpy.s .__assert .setreuid .cu_set_error_1 .cu_get_error_1 .cu_get_errmsg_1 .cu_rel_errmsg_1 .cu_rel_error_1 .nanosleep .__fd_poll .tr_record_data_1 .__pth_init