| To: | REALbasic NUG <realbasic-nug@lists.realsoftware.com> |
|---|---|
| Subject: | Re: Securing Client Server Communications? |
| From: | Norman Palardy <npalardy@great-white-software.com> |
| Date: | Fri, 29 Aug 2008 18:02:20 -0600 |
| Authentication-results: | mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com |
| Delivered-to: | listarchive@realsoftware.com |
| In-reply-to: | <C4DDD601.7BD56%heizer1@llnl.gov> |
| References: | <C4DDD601.7BD56%heizer1@llnl.gov> |
| Reply-to: | REALbasic NUG <realbasic-nug@lists.realsoftware.com> |
| Sender: | realbasic-nug-bounces@lists.realsoftware.com |
On 29-Aug-08, at 5:36 PM, Charles E. Heizer wrote: I have played with a few of the client server examples and have started to grasp the whole thing but before I get to far down the road I would like to know how/best way to secure the communication/command from the server to theclient to prevent man-in-the-middle etc... Start with things like key exchange (like Diffie - Hellman) Many secure algorithms on the internet rely on it _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Securing Client Server Communications?, Charles E. Heizer |
|---|---|
| Next by Date: | Re: Securing Client Server Communications?, lists@mgreg |
| Previous by Thread: | Securing Client Server Communications?, Charles E. Heizer |
| Next by Thread: | Re: Securing Client Server Communications?, lists@mgreg |
| Indexes: | [Date] [Thread] [Top] [All Lists] |