|
Thanks for the reply. The clients are employees, not the public. We just need to tell them how to import the certs. Looking around windows now. Any tips on where to import? Art On 1/30/07, Sean Porterfield <sporter@xxxxxxxxxxxx> wrote:
Art Tostaine, Jr. wrote: > We have secure telnet working, but we want to limit telnet connections > outside the firewall to users who have been emailed a certificate that we've > created. > > We know how to create the cert. > > How do we configure telnet to require it? How do we import it to the > client? Is it possible? Thanks There are many possible answers depending on exactly what you want to do and what release level you have. I'm taking it for granted that you are forwarding port 992 through the firewall but not 23 (ensuring that SSL is required from outside.) In DCM, you can update the telnet server with "Client authentication required" which means it will not allow SSL connections without a trusted certificate. You assign which CA to be trusted, and that part is set. On the clients, you have to have the server CA in the key database, then you can import the certificate. Otherwise, a pre-made kdb could be sent to the client with instructions on where to put it and what the password is. This part really depends on who your clients are. -- Sean Porterfield -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.