Re: [dtn-security] Re(2): Re(2): Is there a "secure" reference implementation of the DTN stack?

"Graham Keellings (Leonix Solutions Pte Ltd)" <Graham@LeonixSolutions.com> Fri, 10 July 2009 05:27 UTC

Received: from sky.fastbighost.net (sky.fastbighost.net [76.76.22.153]) by maillists.intel-research.net (8.13.8/8.13.8) with ESMTP id n6A5RXPB011712 for <dtn-security@maillists.intel-research.net>; Thu, 9 Jul 2009 22:27:33 -0700
Received: from dyn98-b60-access.superdsl.com.sg ([202.73.60.98] helo=[192.9.200.103]) by sky.fastbighost.net with esmtpa (Exim 4.69) (envelope-from <Graham@LeonixSolutions.com>) id 1MP8d0-0002Vd-2A; Fri, 10 Jul 2009 01:26:34 -0400
Message-ID: <4A56D108.9050303@LeonixSolutions.com>
Date: Fri, 10 Jul 2009 13:26:32 +0800
From: "Graham Keellings (Leonix Solutions Pte Ltd)" <Graham@LeonixSolutions.com>
Organization: Leonix Solutions Pte Ltd
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Peter Lovell <plovell@mac.com>
References: <89E48AE60E64EF4E8EB32B0B7EC74920A1B0F5@EVS-EC1-NODE2.surrey.ac.uk> <4A12195A.6000207@LeonixSolutions.com> <3A5AA67A8B120B48825BFFCF5443856137E0B06196@NDJSSCC03.ndc.nasa.gov> <4A1DD73F.50000@bbn.com> <023601c9df2a$694fd5b0$3bef8110$@com> <4A2DF7FD.5020104@LeonixSolutions.com> <3A5AA67A8B120B48825BFFCF5443856137E3553C4B@NDJSSCC03.ndc.nasa.gov> <029d01c9e925$1e354880$5a9fd980$@com> <4A46C257.3040006@LeonixSolutions.com> <20090628050243.1566215671@smtp.mac.com> <4A46FBB2.3080205@LeonixSolutions.com> <20090628052255.640550503@smtp.mac.com> <4A470CD7.4010502@LeonixSolutions.com> <20090628141313.1532044204@smtp.mac.com> <4A4878A6.7010707@LeonixSolutions.com> <20090629123400.1726285002@smtp.mac.com>
In-Reply-To: <20090629123400.1726285002@smtp.mac.com>
Content-Type: multipart/mixed; boundary="------------010804040201090703040103"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sky.fastbighost.net
X-AntiAbuse: Original Domain - maillists.intel-research.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - LeonixSolutions.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: dtn-security@maillists.intel-research.net
Subject: Re: [dtn-security] Re(2): Re(2): Is there a "secure" reference implementation of the DTN stack?
X-BeenThere: dtn-security@maillists.intel-research.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DTN Security Discussion <dtn-security.maillists.intel-research.net>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@maillists.intel-research.net?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-security>
List-Post: <mailto:dtn-security@maillists.intel-research.net>
List-Help: <mailto:dtn-security-request@maillists.intel-research.net?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@maillists.intel-research.net?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2009 05:27:34 -0000

Peter Lovell wrote:
> Hi Graham,
>
> the best document at this time is the Bundle Security Protocol
> Specification, available at <http://tools.ietf.org/id/draft-irtf-dtnrg-
> bundle-security-08.txt>
>   
wow, that did take some reading (and I doubt that I truly understood 
half of it ;-)

Is there no similar document which covers the whole system, describing 
security measures at each layer, or each stage of the transaction?

~graham();





> This is quite a long document and describes both the general approach
> with ciphersuites and the specific implementation of suites for Bundle
> Authentication (BA), Payload Integrity (PI), Payload Confidentiality
> (PC) and Extension Security (EA). In your search for A Rosetta Stone,
> you'll find that this is about as stony as it gets. It will take some
> time to discern the humour in that statement :)
>
> Regards.....Peter
>
>
>
> On Mon, Jun 29, 2009, Graham Keellings (Leonix Solutions Pte Ltd)
> <Graham@LeonixSolutions.com> wrote:
>
>   
>> hi, Peter,
>>
>>   firs dumb question - is here a single document which discusses the
>> security aspects built into the reference stack? 
>>
>> What I have is someone who "wants DTN with security" but only because he
>> has been told from above that that is what he wants. 
>>
>> He wants to take "a slow, phased approach, maybe just starting with
>> adding (H)MAC to the link establish, then working up to more in later
>> phases". It sounds from what you say that HMAC is already there (for
>> data bundles only? Control plane too?)
>>
>> He is not too clear about what he wants, possibly because he himself  is
>> being given instructions which vary. He has a cryptography (but not
>> necessarily a security) expert from the local university who is
>> "analyzing the code to find weak points" - some weeks I am just supposed
>> to fill these weak points with code, and other weeks I am supposed to be
>> providing security analysis and advice
>>
>> I have been looking around, but I suppose that I ought have started by
>> asking if there is a Rosseta Stone for security in the reference stack.
>>
>> Sorry to be such a nuisance.
>>
>> Thanks, as always, for your help.
>>
>> With best wishes,
>>
>> Graham 
>>
>>
>>
>> Peter Lovell wrote:
>> Hi Graham,
>>
>> threats such as the ones you describe are handled by the Bundle Security
>> Protocol (BSP) code in the RI. Your application does not have to do
>> encryption etc - that is part of BSP RI code.
>>
>> You *do* have to handle management of keys and that means that you have
>> to write some code that the RI code will call. The thumbnail sketch is
>> that the RI code needs protection applied to something (small, such as
>> an ephemeral key) and your code needs to select an appropriate key and
>> do it. There will be some sample code for this but it's not there yet.
>>
>> Each bundle can have HMAC to protect against changes and also against
>> DOS injection attacks. This is standard already.
>>
>> In short, you'll find that the fundamental capabilities you need are
>> already present but you have to supply the key-management code as
>> appropriate for your key mechanism.
>>
>> Regards.....Peter
>>
>>
>> On Sun, Jun 28, 2009, Graham Keellings (Leonix Solutions Pte Ltd)
>> <Graham@LeonixSolutions.com> wrote:
>>
>>  
>> That;'s the problem - I am not a security expert?
>>
>> I guess encryption would be provided by the application which uses DTN?
>>
>> What about add a MAC (or HMAC) for the link established stuff (or even
>> every bundle)?
>>
>> How to denying man in the middle attacks or spoofed bundles, DOS at the
>> network layer by injecting many fake packets? That sort of thing ...
>>
>> Thanks again for your help, Peter.
>>
>>
>>
>> Peter Lovell wrote:
>>    
>> Hi Graham,
>>
>>
>>      
>> there is an agreed upon standard "reference implementation" of DTN 2.6
>> and Oasys 1.3, but  it lacks security features.
>>
>>        
>> what security features do you find missing? The RI is not a turnkey
>> solution but more of a "reference framework".
>>
>> I'm trying to help but am unsure of what's lacking.
>>
>> Regards.....Peter
>>
>>
>>
>> On Sun, Jun 28, 2009, Graham Keellings (Leonix Solutions Pte Ltd)
>> <Graham@LeonixSolutions.com> wrote:
>>
>>
>>      
>> hi, Peter,
>>
>> there is an agreed upon standard "reference implementation" of DTN 2.6
>> and Oasys 1.3, but  it lacks security features.
>>
>> Now, let us say that someone wants a "secure" implementation - but
>> doesn't care about the details of "secure", just that it is generally
>> agreed to be "secure" (or (much) more so than the standard
>> implementation. Is there a reference build for that which can be
>>        
>> downloaded?
>>    
>> My guess is that everyone's perception of "secure" differs and that even
>> for one person it is a matter of trade-offs, but I just though that I
>> would  ask if there is some consensus on what it means for DTN to be
>> "secure".
>>
>> Thanks very much for taking the time to reply.
>>
>> With best wishes,
>>
>> Graham
>>
>>
>> Peter Lovell wrote:
>>
>>        
>> On Sun, Jun 28, 2009, Graham Keellings (Leonix Solutions Pte Ltd)
>> <Graham@leonixsolutions.com> wrote:
>>
>>
>>
>>          
>> Is there a "secure" reference implementation of the DTN stack available
>> for download? Is there even agreement of what a "secure" implementation
>> should be, or is it all a question of trade-offs?
>>
>> Thanks in advance for any help.
>>
>> Graham
>>
>>
>>            
>> Hi Graham,
>>
>> I'm not sure what you're expecting when you refer to a "secure"
>> reference implementation. Do you mean one with the security protocols,
>> or one that had been hardened, or one that has been certified by some
>> organization or other?
>>
>> If you can give a little more context we can help fill in what you need.
>>
>> Cheers.....Peter
>>
>>
>>
>>
>>          
>> --
>> Technical Director
>> Leonix Solutions (Pte) Ltd
>> 18 Boon Lay Way
>> #09-95 TradeHub 21
>> Singapore 609966
>> Telephone:+65 6316 9968
>> Fax: +65 6316 9208
>>
>>
>>        
>>
>>
>>      
>> --
>> Technical Director
>> Leonix Solutions (Pte) Ltd
>> 18 Boon Lay Way
>> #09-95 TradeHub 21
>> Singapore 609966
>> Telephone:+65 6316 9968
>> Fax: +65 6316 9208
>>
>>    
>>
>>
>> _______________________________________________
>> dtn-security mailing list
>> dtn-security@maillists.intel-research.net
>> http://maillists.intel-research.net/mailman/listinfo/dtn-security
>>
>>  
>>
>>
>> -- 
>> Technical Director
>> Leonix Solutions (Pte) Ltd
>> 18 Boon Lay Way
>> #09-95 TradeHub 21
>> Singapore 609966
>> Telephone:+65 6316 9968
>> Fax: +65 6316 9208
>>     
>
>
> _______________________________________________
> dtn-security mailing list
> dtn-security@maillists.intel-research.net
> http://maillists.intel-research.net/mailman/listinfo/dtn-security
>
>   


-- 
Technical Director
Leonix Solutions (Pte) Ltd
18 Boon Lay Way
#09-95 TradeHub 21
Singapore 609966
Telephone:+65 6316 9968
Fax: +65 6316 9208