[nsp-sec] unsubscribing

[Smith, Donald]

You mean something like this:)
I developed these a while back and have published them on the ops-trust wiki.


= Creative Commons Style Sharing signatures =
 1. Author permission required.
  i. This is confidential to this list do not forward or share with anyone outside of this list without specific permission from all of the authors involved.
 1. Author permission required except internally,  anonymize. 
  i. This is confidential to this list do not forward or share with anyone outside of this list except on a need to know basis with  fellow employees to notify or mitigate the issue involved. 
  i. All references to the author and this list must be removed before sharing internally.
 1. Author permission required except to closed vetted lists, anonymize. 
  i. This is confidential to this list do not publish but you may share with other vetted closed security professional lists. 
  i. All references to the author and this list must be removed before sharing.

 1. Author permission required except to closed vetted lists.
  i. This is confidential to this list do not publish but you may share with other vetted closed security professional lists. 

 1. Author permission required except within your organization or those you trust. 
  i. This is not confidential to this list you may share within your origination or among those you trust but you may not publish. 

 1. Public  anonymize. 
  i. This is public share as you desire. All references to the author and this list must be removed before sharing.

 1. Public attribute.
  i. This is public share as you desire but you must attribute this work to the ori

> -----Original Message-----
> From: Rob Lowe [mailto:rlowe at redhat.com]
> Sent: Wednesday, September 05, 2012 5:30 AM
> To: Smith, Donald
> Cc: nsp-security at puck.nether.net
> Subject: Re: [nsp-sec] unsubscribing
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Donald,
> 
> On 05/09/12 02:01, Smith, Donald wrote:
> > Rob, I meant that Rodolfo shouldn't have forwarded emails
> > internally to someone not vetted to the list.
> 
> Apologies for my misinterpretation.
> 
> > If I proxy your posting in order to clean up downstreams without
> > mentioning you specifically is that acceptable?
> 
> I do, fwiw. If I post a list of bad ips which I'm requesting action
> from NSP-SEC, I implicitly trust the judgement of members to get this
> in to appropriate hands (without attribution), regardless of whether
> those hands belong to people in that same organisation or not.
> 
> > If so should we change the charter to cover that? I lean towards
> > YES!
> >
> > ... I just don't think our current sharing framework allows for
> > it.
> 
> Good points, with which I agree and also lean toward YES.
> 
> A possible work around (but less preferable) to changing the charter
> is that senders can be more explicit in the handling instructions they
> have for the data they share.
> 
> Regards,
> Rob
> 
> - --
> Rob Lowe                      | Red Hat Asia-Pacific
> Information Security Analyst  | http://www.redhat.com
> Phone: +61 (0)7 35148244      | rlowe at redhat.com
> 5272 504B 6A97 415C 2EB2  E7B9 EDE4 0A83 CD9F E7A4
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
> 
> iQIcBAEBAgAGBQJQRzeoAAoJEO3kCoPNn+ekn9MP/0zELGJTAmcMYjiczus3yYz3
> K7p1Snp7gXEp/mOMrLJmqMmvnDSE0VOM/xUH4VlFtie01rxwA5Sg19jVR4YI2waI
> WmNuvqCWrF4oUnheoQCj3sA3mz1sekXjD0Ug4UDAizKPdo/sp1Cs3ai9MqVZqjov
> pwc579oHORbxKyTaa30B08YnwNf8G6KarKtZdcMAEPDT1/IVnOzelvdKzcuLqELN
> 8aWH+X+qlVyxki/Ftd14xA1KpKJe9bM7l74PkM5/9wprX5GlKlOmlKxjBT0hDVPV
> P93MIdJkicnECYS8imY5ZT7bq6rtD7NfQ//59Nt/d8U2I3jb70iAf4v9kH0sZPPQ
> LjmSJ99wvDx3G/O9zXjhBp4lDDvl7ZsV6hb39KR4CCJQI8p+c/JcBghlGgTYVJb8
> rPLrRWP0TcfHkK+mTdyFLcZRtTXbkqoqMckbpj51Sx1wbAVzzAX4PX8N5PVFONHh
> l5rO4VKq14HqNPBwv1SF8YhedZWo9PTBg6N8TK0d5I+sw7733twyh35LyUnwLFVs
> 7xYn0kRDmQ0F1jopmDIRQ3XrAyzdvLEU341THY16u4y5ls5QaU6QLqnJmo8JG2VQ
> J+W47bZ3aMyhHWDzzenBJcb3sgOoUwGKLj2UpmRWPQPv83xw5328hXc6a3WMx8KN
> c4WtLl1VVYq9/smagT3w
> =Xw2F
> -----END PGP SIGNATURE-----