<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>That sounds right.</div><div><br></div><div><br></div>On Oct 31, 2013, at 3:20 AM, Steve Crook <<a href="mailto:steve@mixmin.net">steve@mixmin.net</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>Hi Tom,<br><br>Thanks for your description of the Tagging Attack. If I understand<br>correctly, there are a number of steps to resolving it:-<br><br>1) Include pad bytes when calculating header digests.<br>2) Add a digest within each intermediate header for the encrypted next-hop<br> header.<br>3) Add a digest within each header for the encrypted payload.<br><br>All of these digests to be calculated by the client during encoding.<br>_______________________________________________<br>Remops mailing list<br><a href="mailto:Remops@lists.mixmin.net">Remops@lists.mixmin.net</a><br><a href="http://lists.mixmin.net/mailman/listinfo/remops">http://lists.mixmin.net/mailman/listinfo/remops</a></div></blockquote></div><br></body></html>