Folks,
My *personal* convention is the following:
SUN SNOOP : .snoop
Libpcap : .pcap
Unknown : .cap (or .pkts)
One should not restrict to stone age's 8.3 filename conventions :)
Regards,
Olivier
|-----Original Message-----
|From: Guy Harris
|
|
|RABRET Laurent FTRD/DAC/ISS said:
|> There's also a straight and forward way that does not
|require any access
|> to the registry: the ShellExecute(...) system call. Just one
|constraint:
|> you must call a valid file that extension is associated to Ethereal.
|> Hummm, it seems there's no such an association created in the nsis
|> script so I propose a patch to automatically do this with '.cap'
|> extensions. Thanks to check in.
|
|See my earlier mail on this thread for reasons why ".cap"
|isn't the right
|choice for libpcap-format capture files (too many network analyzers
|already use it, so it's *already* overloaded).
|
|WildPackets' ProConvert uses ".dmp"; Analyzer:
|
| http://analyzer.polito.it/
|
|appears to use ".acp" - I'd be inclined to make ".acp" the default, as
|Analyzer is another free packet analyzer with libpcap format
|as its native
|format, unless the Ethereal-derived Packetyzer:
|
| http://www.packetyzer.com/
|
|has a default suffix other than ".acp" *and* that suffix isn't
|the ".cap"
|that:
|
| the Windows version of Sniffer;
|
| Network Monitor;
|
| Shomiti Surveyor;
|
| Acterna Domino, Fireberd[sic] 500, and LinkView PRO;
|
| Fluke Protocol Inspector;
|
|already use (for file formats different from each other,
|although *maybe*
|all the Acterna products use the same format).
|
|_______________________________________________
|Ethereal-dev mailing list
|Ethereal-dev@xxxxxxxxxxxx
|http://www.ethereal.com/mailman/listinfo/ethereal-dev
|