Skip to content

Commit

Permalink
move DTLS comments
Browse files Browse the repository at this point in the history
  • Loading branch information
David Woodhouse authored and David Woodhouse committed Sep 22, 2008
1 parent c3ce49c commit 77e0799
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 5 deletions.
17 changes: 17 additions & 0 deletions dtls.c
Expand Up @@ -22,6 +22,23 @@

#include "anyconnect.h"

/*
* The master-secret is generated randomly by the client. The server
* responds with a DTLS Session-ID. These, done over the HTTPS
* connection, are enough to 'resume' a DTLS session, bypassing all
* the normal setup of a normal DTLS connection.
*
* Cisco's own client uses an old version of OpenSSL, which implements
* the pre-RFC version of DTLS. I haven't been able to get it working
* when I force it to link against any of my own builds of OpenSSL.
*
* Hopefully, it'll just work when I get round to implementing it
* here, either with the system OpenSSL, or linking against their
* library (which will at least be progress, and make it a little
* easier to debug.
*/


int setup_dtls(struct anyconnect_info *vpninfo)
{
struct vpn_option *dtls_opt = vpninfo->dtls_options;
Expand Down
5 changes: 0 additions & 5 deletions main.c
Expand Up @@ -35,11 +35,6 @@

#include "anyconnect.h"

/* The master-secret is generated randomly by the client. The server
responds with a DTLS Session-ID. These are enough to 'resume' the DTLS
session, bypassing all the initial setup of a normal DTLS connection.
Or you can just send traffic over the HTTPS connection... */

int verbose = 0;

static struct option long_options[] = {
Expand Down

0 comments on commit 77e0799

Please sign in to comment.