Thanks all for your explanations.
Suleiman Shahin
> Date: Fri, 9 May 2008 09:00:45 -0500
> From: [EMAIL PROTECTED]
> Subject: Re: Coding the port statement in the TCPIP profile.
> To: IBMVM@LISTSERV.UARK.EDU
>
> Thanks Mark.
>
> The problem is maybe with the English
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Coding the port statement in the TCPIP profile.
Hello Thomas and Suleiman,
I believe the confusion over label length (and other characteristics) has=
arisen due to not considering the type of certificate. For a CA
certificate, the label can be as Thomas cited --
Hello Thomas and Suleiman,
I believe the confusion over label length (and other characteristics) has
arisen due to not considering the type of certificate. For a CA
certificate, the label can be as Thomas cited -- up to 200 characters in
length, can be mixed-case, and can contain blanks. A SER
Subject: Re: Coding the port statement in the TCPIP profile.
On Wednesday, 05/07/2008 at 08:53 EDT, Suleiman Shahin
<[EMAIL PROTECTED]> wrote:
> I am coming back to an old question.
> The original question used wrong words.
>
> It should have been "how do I use the Ce
On Wednesday, 05/07/2008 at 08:53 EDT, Suleiman Shahin
<[EMAIL PROTECTED]> wrote:
> I am coming back to an old question.
> The original question used wrong words.
>
> It should have been "how do I use the Cerificate *label* on the port
statement
> when the *label* is 60 characters long.
>
>
Greetings,
I am coming back to an old question.
The original question used wrong words.
It should have been "how do I use the Cerificate *label* on the port statement
when the *label* is 60 characters long.
Example:
777 TCP INTCLIEN SECURE the 60 character long certificate label xyz fro
