https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15659
--- Comment #10 from Ross Jacobs ---
@Guy: It looks like the link you provided
(https://gist.github.com/XVilka/8346728) from the source code states
to check the $COLORTERM variable for
values "truecolor" or "24bit". This is implemented
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15659
--- Comment #9 from Dave Goodell ---
(In reply to Guy Harris from comment #5)
> (In reply to Ross Jacobs from comment #2)
> > Picture on Macos for comparison:
> > http://blog.goodell.io/images/tshark-wireshark-color.png
>
> That was
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11567
--- Comment #2 from LiquidMe ---
Wrong names on the outer side of the connection can happen and have been used
in the part to help tor bypassing restrictions via domain fronting, but the
benefit outweighs the problem of wrong data.
Maybe
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15454
--- Comment #9 from Maksim Salau ---
Hi Guy
(In reply to Guy Harris from comment #8)
> Either Flex & Bison/BYACC (if there's any .y file in the Wireshark source
> that works only with Bison, not Berkeley YACC, that's a bug), or Flex &
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15659
--- Comment #8 from Guy Harris ---
(In reply to Ross Jacobs from comment #7)
> In terms of the SGR support, I think it's worthwhile to negotiate
> to verify whether it's supported.
Negotiate with *what*?
With Windows, there
