Re: [dtn-security] Re(4): Including fragment offset in the correlator doesn't prevent all fragment collisions.

"Burleigh, Scott C (313B)" <> Sun, 14 April 2013 00:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1B7D621F8DDF for <>; Sat, 13 Apr 2013 17:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cTX2UcXZLp4x for <>; Sat, 13 Apr 2013 17:25:08 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id BCCA121F8A6B for <>; Sat, 13 Apr 2013 17:25:08 -0700 (PDT)
Received: from ( []) by (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3E0P5ew005688 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Sat, 13 Apr 2013 17:25:05 -0700
Received: from AP-EMBX-SP40.RES.AD.JPL ([]) by ap-ehub-sp01.RES.AD.JPL ([]) with mapi id 14.02.0342.003; Sat, 13 Apr 2013 17:25:04 -0700
From: "Burleigh, Scott C (313B)" <>
To: Amy Alford <>, Elwyn Davies <>
Thread-Topic: [dtn-security] Re(4): Including fragment offset in the correlator doesn't prevent all fragment collisions.
Thread-Index: AQHOKA4AwAq0n0zXUkuQfuDcUCFv7Zi3S36AgB2+HgCAAEOkAP//rp7y
Date: Sun, 14 Apr 2013 00:25:03 +0000
Message-ID: <A5BEAD028815CB40A32A5669CF737C3B235B2E1E@ap-embx-sp40.RES.AD.JPL>
References: <> <> <> <> <> <> <> <1365876632.5273.8820.camel@mightyatom>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_A5BEAD028815CB40A32A5669CF737C3B235B2E1Eapembxsp40RESAD_"
MIME-Version: 1.0
X-AUTH: Authorized
Cc: dtn-security <>
Subject: Re: [dtn-security] Re(4): Including fragment offset in the correlator doesn't prevent all fragment collisions.
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Security." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 14 Apr 2013 00:25:10 -0000

Amy, I certainly agree on the potential for Bad Things happening when fragmentation and security aren't cleanly nested.  Can you say a little more about how the proposed new BSP draft's support for security sources could expose nodes to these problems?

From: [] on behalf of Amy Alford []
Sent: Saturday, April 13, 2013 3:12 PM
To: Elwyn Davies
Cc: dtn-security
Subject: Re: [dtn-security] Re(4): Including fragment offset in the correlator doesn't prevent all fragment collisions.

If you think about a "fragmentation path" similar to a security path, whenever fragmentation paths and security paths overlap (instead of one nesting inside the other), Bad Things (TM) are probably going to happen in DTN2.

If it's fragment -> add bsp -> defragment -> remove bsp, you're up against the fact that defragmentation doesn't necessarily preserve enough info to validate the BSP blocks.  Even if it does, DTN2 currently doesn't recognize that a set of valid BSP blocks that cover the payload are enough to satisfy policy requirements.

If it's add bsp -> fragment -> remove bsp -> defragment, you're obviously sunk because you can't validate the BSP blocks which apply to the whole payload when you only have a fragment.  In this case, you obviously need to reconstitute the bundle before you remove the BSP blocks.

This doesn't even touch the headaches involved with multiple BSP instances and multiple fragmentation.

BiB will need to deal with the second case (the easy one - DTN2 will probably handle this with no changes), but avoids the first case because an encapsulated fragment is not itself a fragment (so it can't be reconstituted until after it's been decapsulated).

The new BSP draft may not sidestep these problems though, because it still allows security sources and hop-by-hop ciphersuites still need to be able to handle non-security-aware nodes in the middle.

On Sat, Apr 13, 2013 at 2:10 PM, Elwyn Davies <<>> wrote:

It just occurred to me that the way DTN2 handles fragment payloads
probably gets very screwed up if two paths either with different
encrypted security tunnels or with one encrypted and one unencrypted
converge at some point after fragmentation.  I haven't looked in detail
into the code, but I suspect that there are some cases in which order
of delivery via the two different paths might lead to  the payload
getting a mix of data from the two sources and becoming unintelligible.

Not certaim if I am right, but may be another argument for using b-i-b


On Mon, 2013-03-25 at 15:58 -0400, Amy Alford wrote:
> On Sat, Mar 23, 2013 at 5:32 PM, Peter Lovell <<>> wrote:
>         Hi Amy,
>         Amy Alford <<>> wrote:
>         >Yes, my example was assuming a PIB ciphersuite that used two
>         blocks
>         >(similar to BAB).  That case is the most problematic, because
>         when the
>         >bundle is fragmented, the two blocks will end up in separate
>         fragments.
>         > Otherwise, the correlator collision isn't a problem as long
>         as reassembly
>         >happens at the destination.
>         PIB is, in some ways, a more difficult scenario than PCB. When
>         a bundle with PCB arrives at the security-dest, the payload is
>         decrypted (and other blocks as appropriate) and the PCB itself
>         is deleted. But some folks want to have PIBs remain even after
>         verification, as evidence I guess. That is messy.
> Leaving PIBs on after verification is problematic anyway, if the PIB
> was added after a PCB.  Once the PCB reaches it's security
> destination, the PIB is invalid anyhow.
>         Is there a specific reason for a two-block PIB?
> 6257 mentions the idea of PIB ciphersuites that use a trailing block
> similar to BAB.  I assume you'd still want an up front block to warn
> nodes that are doing one pass processing that they need to start
> hashing.
>         >> As you can see, this is a quite involved process. A couple
>         of things are
>         >> worthy of note:
>         >> 1. correlators are local to their bundle
>         >> 2. a block with a correlator may be encapsulated, with PCB
>         for example.
>         >> The original correlator is hidden until decapsulation
>         occurs (not shown
>         >> above for sake of brevity :)
>         >> 3. reassembly is a very, very complex process.
>         >>
>         >I was pondering how to support these sorts of cases (which
>         end up needing
>         >validation and reassembly interleaved somehow).  In thinking
>         about it, I
>         >started running into scenarios that aren't supportable.  The
>         example I gave
>         >is one (which I think shows that bundles with two block PIBs
>         need to have
>         >the do not fragment flag set).
>         It may be sufficient to apply the
>         replicate-key-info-in-every-block rule. I don't know without
>         thinking about it some more.
> I think it would fix the example I gave.  The last fragment would
> contain both the leading and trailing PIB blocks.  The leading block
> could be used to match this up with the corresponding fragment (which
> also has a leading PIB block but is missing the trailing one).  It
> would be a pain in terms of processing, since defragmentation would
> need to match up the corresponding fragments by comparing their
> leading PIB blocks.
>         >Additionally, in general, if an intermediate node reassembles
>         fragments
>         >that have had BSP blocks added after fragmentation, we can't
>         validate.  Too
>         >much information is lost on reassembly (even if it's done
>         sensibly).  5050
>         >allows intermediate nodes to reassemble, but doesn't mandate
>         a procedure
>         >for reassembling the extension blocks (so it may not be done
>         sensibly).
>         It's not just an issue of reassembling/reordering extension
>         blocks. As the final example shows, any attempt to
>         reassemble-first is doomed to failure because the two parts
>         were encrypted under different second-stage keys.
>         It's clear to me that reassembly of bundles containing
>         security blocks must be done in concert with security
>         processing. This needs to be incorporated into any update to
>         5050. And, as you say, there are cases that aren't supportable
>         with the capabilities we now have.
> Yes.  In general, nodes shouldn't reassemble a bundle if they don't
> understand all the extension blocks.  BSP aware nodes shouldn't
> reassemble fragments except in concert with security processing.
>         Regards.....Peter
> _______________________________________________
> dtn-security mailing list