Re: secure telnet/equivalent

[Peter Czarny <pczarny@xxxxxxxxxxx>]

Paul,

Well, IBM makes it quite difficult to tell whether cryptographic 
support is required or not. But, when I start to go through the 
configuration (of DCM) through the HTTP server, it hits me with a 
message that cryptographic support is required. I can not find an 
alternate way to proceed and any documentation I research leads me down 
the same path. It does seem quite convoluted. Of course, the discussion 
about IBM SSL is academic as the system is at 4.3 which is not 
supported by IBM. However, now I am determined to solve this. If and 
when I find an answer I will let you know. I really appreciate your 
input.

Peter

On Wednesday, Apr 2, 2003, at 16:42 US/Central, James Rich wrote:

> On Wed, 2 Apr 2003, Peter wrote:
>
> > I was hoping that some third party had put together a ssh package for
> > the AS/400.
>
> None that I'm aware of.  Too bad, really.
>
> > About  IBM SSL feature - does it not require cryptographic support? 
> > Your
> > comment about requiring much help implies that implementation is a bit
> > complex or am I reading this, incorrectly.
>
> I don't believe it requires crytographic support.  At least SSL doesn't
> require the cryptographic coprocessor.  It took the help of others
> (including IBM) because it is new to me and the Digital Certificate
> Manager (what is used to configure SSL) had some problems (largely 
> fixed
> by PTFs - my personal opinion is the the DCM is a piece of junk, 
> openssl
> did a *much* better job that doesn't require any moronic web interface 
> to
> configure and *works all the time*  IBM get a clue from openssl and
> openssh, these two projects are really well done - the DCM is 
> garbage!).
>
> Yes, I was frustrated :)  But it works now.
>
> James Rich
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.