[slackware-sparcdevel] Loss of rsync access

From: David Cantrell (david@slackware.com)
Date: Wed Nov 01 2000 - 06:08:12 PST


Some of you may have noticed that the rsync server is not allowing anyone
to connect. I did this because I noticed connections from people other
than people on this list. I feel obligated to state a few things now:

Toby Freaksoft (is that his name?) <freaksoft@yahoo.com> is no longer a
beta tester. He was responsible for the post to Slashdot and has also
handed out access information to the rsync server to at least one person,
but I imagine that has spread a bit. If he contacts anyone on this list
regarding the SPARC port, please ignore it.

When I saw the post of Slashdot, I couldn't believe it. This mailing list
does not contain Slashdot news. Please don't take it there. The post has
generated a lot of emails from people I'd rather not have using the SPARC
port at this point in time. I trust that everyone agrees with me and will
keep this private mailing list private.

Lastly, I feel I must state this, given what has happened recently. This
mailing list and the rsync server are to be kept private, among us. The
port is not in a state for public consumption, nor should any news be
distributed regarding the port. You can say that the port "is being
worked on." That is all.

Please do not give out access information to the rsync server either. I
did not want to have to have some obscure authentication and registration
method for everyone, but now I'm thinking that was a bad idea.

I did not make everyone sign NDAs, but now I'm rethinking my decision on
that one. Can I trust everyone to keep this -current branch private and
the contents of the mailing list private. When it's ready for the public,
it'll be ready for the public.

--
David Cantrell | david@slackware.com
        KG6CII | Slackware Linux Project



This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT