-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "itojun" == itojun  <[EMAIL PROTECTED]> writes:
    >> I thought that we would decode an ESP secret that was in hex.
    >> It appears that we can only deal with secrets in literal binary.
    >> This isn't impossible to wedge into the command line (except for '\0', but it
    >> certainly isn't easy...
    >> Also, why do we check the length of some secrets, but not others?

    itojun>     i guess i'm guilty.  i should not have committed -E to tcpdump.org
    itojun>     repository, until we have some better resolution about interaction
    itojun>     with -x (-x dumps deciphered binary for parts after esp, which is not
    itojun>     trivial to understand).  -E needs a lot of enhancements/changes to
    itojun>     become useful.

  Actually, I find it works rather fine.
  Without -E one gets ciphertext, with -E one can get plaintext. In fact,
this is how I finally found the problem with the authheader not being
removed.

  I've committed some changes to the "mcr_dissect" branch, which I hope I
will be able to pull up soon. (I could do it now if we think we have all of
the 3.7 stuff worked out...)

  Please let me know what you think of the code.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [



-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Finger me for keys

iQCVAwUBO8sUJ4qHRg3pndX9AQFdDAQAo+/o/QiqwZ78COPOFVrEG2S/cyx3vy1u
IJCdiilkJT1m3rnCtyoEntB9bfmoDnTlSONwW6hK1+IhGH3FlMnjGMJ6Xd+Mx3LS
TxBgz7c4J4TEvFMT0gkbQKeOvZJ47QkUZsl/dcCQ2klBXnFoKLSFWU8KbynBbA6g
GW+ACV7epBQ=
=n8R3
-----END PGP SIGNATURE-----
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe

Reply via email to