https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3270
--- Comment #43 from Russell C. Sibley <lab@xxxxxxxxxxxxx> 2009-12-13 13:43:57 PST ---
(In reply to comment #42)
> (In reply to comment #41)
> > I think we can close this... agreed?
>
> Now, that bug would be fixed when a comment says which downloadable wireshark
> version it is fixed in, wouldn't it?
No, just the fact that (a) the bug was found, (b) a testable version proves it,
and (c) future releases will have it (see below).
> By the way, why the 1.0.x work? Is this bug not affecting 1.2.x?
The bug was in libgcrypt... Werner Koch posted to
(https://bugs.g10code.com/gnupg/issue1167) that the fix will be released in
1.4.5, so all subsequent releases of wireshark will have it.
> I am assuming it does because it would have been an horrible waste of time...
Not for me... I'm running w2k and later versions of ws simply won't run on that
platform. I'm stuck with 1.0.* for now, but that does fine for my needs.
> Thanks to all.
Cheers.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.