acmeattic-devel team mailing list archive
-
acmeattic-devel team
-
Mailing list archive
-
Message #00067
Re: Encryption blueprint
On Tue, Jul 13, 2010 at 3:24 PM, krishnan parthasarathi <
krishnan.parthasarathi@xxxxxxxxx> wrote:
>
> On Wed, Jul 14, 2010 at 12:32 AM, Karthik Swaminathan Nagaraj <
> nkarthiks@xxxxxxxxx> wrote:
>
>> used to recover the RSA key pair on the client machine (should be
>> preferred).
>>
>>>
>>>
>>> This method avoids the loss and regeneration of RSA keys, and makes it
>>> easy to add a new machine to an account on the server. Thoughts?
>>>
>> I would like to keep separate keys for separate machines. If we follow the
>> SpiderOak model, each client (for the same user) has a unique identity and
>> maintains its own synced folders.
>>
>
>
>> Thus maintaining a separate key is not an issue and somewhat feels like a
>> cleaner separation to me (gut feeling).
>>
>
> If each client installation for the same user is going to have different
> RSA keypair then sharing files becomes a problem. We are planning to use the
> RSA public key of the 'sharee' to sign/encrypt the AES key of the file
> shared by the 'sharer'.
>
True. Thanks for reminding me about sharing. I had temporarily thrown it out
of my mind.
>
> cheers,
> krishnan
>
>
--
Karthik
Follow ups
References