Wireshark improvements
From Linux NFS
(Difference between revisions)
Chucklever (Talk | contribs) |
|||
| Line 4: | Line 4: | ||
* General maintenance, bug-fixing | * General maintenance, bug-fixing | ||
| - | |||
| - | |||
| - | |||
| - | |||
* (probably hard) Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies. | * (probably hard) Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies. | ||
| + | |||
| + | Is all of this done now?: | ||
| + | |||
| + | * callback channel decoding: in 4.1 case, this is easy. In 4.0 case, requires seeing the setclientid call. | ||
| + | * Update to 4.1. (Mostly done: may still be some odds an ends missing, though. | ||
| + | * Add decoders for rpcbind protocol versions 3 and 4. (Done or not?) | ||
| + | * Test to make sure all existing NFS and RPC related decoders work nicely with IPv6. (?) | ||
| + | * Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies. | ||
Revision as of 22:32, 23 August 2010
Wireshark (previously known as Ethereal) is invaluable for understanding what's happening on the wire between a client and server, but it could be better. Some examples:
- General maintenance, bug-fixing
- (probably hard) Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies.
Is all of this done now?:
- callback channel decoding: in 4.1 case, this is easy. In 4.0 case, requires seeing the setclientid call.
- Update to 4.1. (Mostly done: may still be some odds an ends missing, though.
- Add decoders for rpcbind protocol versions 3 and 4. (Done or not?)
- Test to make sure all existing NFS and RPC related decoders work nicely with IPv6. (?)
- Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies.
