Ubuntu Core Channels Blocking Shell Accounts. Discussion.

[Robert Wall]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/16/2010 01:47 AM, Matt Darcy wrote:
> I'd like to propose a blanket ban on all unmanaged, or managed shell
> servers that do not fit in with an agreed managment policy for the
> ubuntu core channels.

In general, I think this is a good idea, with one caveat. I expect that
there are a small number of legitimate users that use these hosts. It
may be worth considering whether to +e them or just recommend they move
to a different host, and whether to have a list somewhere of compliant
hosts to make moving easier.

(Personally, I think +e'ing users on request would work well, though I'm
not sure how many requests you'd get, so I don't know if it'd cause too
much overhead.)

> The same cannot be said for the bshellz admin team, who where not
> actually bothered about abuse on their services, or policing them. They
> where not being negative in any way, that just isn't their policy to
> manage the shell users, and they don't want to police the servers to
> stop trouble users from opening up multiple/repeat accounts, which is
> there call.

As a former bshellz user, I'm not really surprised. They have a hard
enough time responding to queries from their own users, in my experience.

> We currently block tor

freenode's current tor restrictions are detailed on
http://freenode.net/irc_servers.shtml#tor . As far as I know, #ubuntu
doesn't have any additional restrictions.

> My proposal is
> 
> a.) come up with an agreed set of requirements for server shell hosts to
> have to be allowed to use the ubuntu core channels, eg: the ability and
> desire for them to block users from their service, the ability/desire to
> administrate their service and a desire to work with external resources,
> such as the Ubuntu irc team to resolve any issues.
> 
> b.) Any who don't fall within a.) AND have shown to be a source of abuse
> (such as bshellz) get a blanket ban on the core channels.

+1

~ Robert Wall (rww)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBCAAGBQJMaP/HAAoJELZQE6STdV4Ixz0H/j6ATPT6sT8LPfF52amgcFPp
mgANKN/CnssSZfifyi8ZIzfRyzLVsWyqtbLt+LEOAkEBKnHHAFfnwdTPx2Zy6HR2
Kt18pO+Y2mciNSY4dxFQbjiM8nQOQG2NbniZMdXVcUgl7T116OgDDCP395vxa8nz
mpLGl2btFyQTvrpjv+HuHrUZslh2eoCblLGzCJTVcUsej2+xg3Rj3B48V9OJKYUQ
LPP0mX+TkUGoevdEc+qnsP3tVwBzWodO9lDZIu8qVpP5NAyEmQuJ4lVBT/Ql2OM6
Zws6U3tR4edc0V5F2vDRUPVseA6FX2tInxBqVVtGQxFJ2hwyEUUgT+me2LIdvwk=
=YT/n
-----END PGP SIGNATURE-----