From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] ethereal and wireshark
Date: Wed, 07 Jul 2010 09:32:15 -0400 [thread overview]
Message-ID: <4C3481DF.8090103@tresys.com> (raw)
In-Reply-To: <201007070751.17682.russell@coker.com.au>
On 07/06/10 17:51, Russell Coker wrote:
> http://en.wikipedia.org/wiki/Wireshark
>
> Given that Ethereal was renamed to Wireshark I think we shouldn't have both
> ethereal.te and wireshark.te in the policy.
>
> If nothing else the fact that the rename was due to trademark issues
> suggests
> that we should remove ethereal.* to avoid trademark problems.
Agreed. Done.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2010-07-07 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:51 [refpolicy] ethereal and wireshark Russell Coker
2010-07-07 13:32 ` Christopher J. PeBenito [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3481DF.8090103@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.