Igor:
Here is my understanding of how the Partnership files
are signed:
i. When a user registers, the website creates for them a public
private key pair. It stores the public key in a database, and
puts the private key into the Registration file.
ii. When two users create a partnership, the server creates a
partnership file based on the two user's names, email addresses,
and IP addresses. It *think* it also puts the two public-keys
in there as well, adds some random padding, then signs the
result using its Partnership Server Secret Key (PSSK).
iii. The GetEngaged.exe application comes built-in with the
PSSK so that it can check the validity of a Partnership file's
signature before installing it. When a connection request is
initiated, it's the job of Kaboodle to check the validity of
that incoming request based on the contents of the exchanged
Partnership file.
There are some problems here, which since you are not
very familiar with MS Crypto Api, might be something you don't
want to work on. In general, I want there to be two types of
Partnership files:
1. Partnership files generated by the GetEngaged webserver. In this
mode, *both* partners must have the files as created for them
installed or the VPN connection won't validate.
Right now, this is the only mode that works, but I am not
sure how well Kaboodle checks the validity of a VPN connection request.
That is, after partner discovery is done, is there some sort of
challenge-response going on? Can a malicious user hack the Kaboodle
source to give seemingly legitimate responses during authentication?
2. Partnership files that a user generates and distributes widely.
Anyone who installs one can VPN with that user, with an optional
password.
To create these files, I want to allow the users to use GPG
and their existing keys if they have it installed. The second
alternative is to use Zebedee (which has a pub-priv key generation
capability). We will have to modify GetEngaged.exe so that it allows
the installation of these types of Partnership files, and then modify
Kaboodle so that it does traditional SSH-like challenge/response
verification.
A lot of this works now, but I know all of it doesn't. It'd
be good to get it right for 1.0. :)
-Scott
On Wed, 2 Oct 2002, Igor Kotelevsky wrote:
> Hello Scott.
> I have some problem in the Partnership file generating because of
> - I don't familiar with MS Crypto Api very good,
> - the Partnership file contains some data (near the middle of the file),
> which looks like a signature, but that data don't check both by Kaboodle.exe
> or GetEngaged.exe.
> Please send me source code (script) of the Website
> http://www.getengaged.net/
> and/or some additional data about format of Partnership file and algorithm
> of signature.
>
> - Igor
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 25, 2002 9:36 AM
> Subject: Re: 21 Sept bug report
>
>
> > 4. We need a way for users to generate Partnership files without
> > going to our servers. Presume that users also have GPG
> > installed, and have each other's public keys already. They
> > need a way to generate the file via Kaboodle and we need
> > a way for Kaboodle to verify the integrity of the file when
> > it's received (ie, checking it against their GPG private
> > key). We should also add GPG to the Components list.
>
>
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
