× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




The DC just ensures the client that the server machine is who it says it
is.

The client credentials (user id and password) ensure the server that the
client is who it says it is. The client credentials are encrypted by the
client using the public key contained in the DC and decrypted by the
server using the private key.

When the credentials are checked and the session is established the
participants (client and server) agree on a new encryption key. That key
is secret.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hart, Doug - EI
Sent: Wednesday, April 23, 2008 12:41 PM
To: Midrange Systems Technical Discussion
Subject: FTP-SSL from Client Side


I have my iSeries setup for FTP-SSL hosting. Then I exported the Local CA
digital certificate so I could send it out to my business partner so they
can securely connect to my system. Here is where I loose the concept. To
test I thought I would connect from my Windows PC. I never installed the
DC in Windows or into the FileZilla FTP client I'm using.
When I connect to my host I login and get a popup from FileZilla asking
if I will accept a DC. I respond yes and I'm in. Why am I sending out
the DC to the remote client? This doesn't seem very secure as the DC
isn't confirming the remote connection site (yes it may still be doing a
secure transfer).


--
Douglas Hart


This e-mail and any files transmitted with it may be proprietary and are
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error please notify the
sender. Please note that any views or opinions presented in this e-mail
are solely those of the author and do not necessarily represent those of
ITT Corporation. The recipient should check this e-mail and any
attachments for the presence of viruses. ITT accepts no liability for any
damage caused by any virus transmitted by this e-mail.
--
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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.