Difference between revisions of "ASS"

Revision as of 17:56, 21 December 2007

ASS is an acronym representing "Administrators of Systems and Security".

The ASSes are the oldest working group at Free Geek. They are the people who design and manage the network at Free Geek, and are responsible for developing our IT security policy.

You'd think this would mean we'd have a better wiki section =:)

Members

(ASSes, please list yourselves here):

Vancouver, BC, Canada ASSes:

agent humble

Joining

Talk to one of the people listed above. Sign up on our email list. Attend a meeting. This will get you involved with the group, and put you in a place where you can start to help us. This is referred to as being a Half-ASS. From here, keep working with us and prove yourself to be trustworthy and competent in the eyes of 3 ASSes, and you will be accepted as an ASS-Whole.

ASS Priorities

Here is a list of what ASSes should prioritize when making decisions.

Communicate effectively with your users. Communicate with other ASSes about what you're doing.
Maintain effective security; stop people from doing things that they shouldn't be doing.
Maintain data integrity for our users and our systems.
Do not violate or let be violated the privacy of your users.
Keep all your services in working order (e.g. research a new version before upgrading to it)
Minimize and mitigate any downtime that happens or is necessary to have.
Be efficient, paying attention to requests of more importance before minor issues.
Uphold our local organizational policies as well as the accepted laws related to your work.
Do not abuse Free Geek's resources, and help to prevent others from doing the same (excessive network traffic, excessive printing).
Try not to be annoying; people will complain much sooner and louder if something bothers them than if something is just broken.
Do what it takes to understand the implications of your actions before taking them, so that you can knowingly apply these priorities.

Ongoing Tasks

RootMail Cleanup - Often (Matteo)
Tape Swapping - Weekly (Richard)
Test UPSes in server room - once per week/ASS meeting/month
apt-get upgrade - check nagios, or once per month
Reporting debian bugs
$ reportbug PACKAGENAME - or - $ reportbug --no-check-available PACKAGENAME

http://www.debian.org/Bugs/Reporting

http://www.debian.org/Bugs/Access
updating netboot
http://ftp.debian.org/dists/ * /main/installer-i386/current/images/netboot/

http://archive.ubuntu.com/ubuntu/dists/ * /main/installer-i386/current/images/netboot/
Services provided to other groups

More fun

Some folks at Free Geek or in our extended community are CA Cert Assurers. See the page.

What services do we provide

@@ Line 2: / Line 2: @@
 ''ASS is an [[Wikipedia:Initialisms|acronym]] representing '''"Administrators of Systems and Security".'''''
-The ASSes are the oldest working group at Free Geek. They are the people who design and manage the network at Free Geek, and are responsible for developing our IT security policy.  They have [http://lists.freegeek.org/listinfo/ass an email list].
+The ASSes are the oldest working group at Free Geek. They are the people who design and manage the network at Free Geek, and are responsible for developing our IT security policy.
 You'd think this would mean we'd have a better wiki section =:)
@@ Line 24: / Line 24: @@
 Vancouver, BC, Canada ASSes:
 *[[User:humble|agent humble]]
+==Joining==
+Talk to one of the people listed above.  Sign up on our [http://lists.freegeek.org/listinfo/ass email list].  Attend a meeting.  This will get you involved with the group, and put you in a place where you can start to help us.  This is referred to as being a Half-ASS.  From here, keep working with us and prove yourself to be trustworthy and competent in the eyes of 3 ASSes, and you will be accepted as an ASS-Whole.
 ==ASS Priorities==
@@ Line 37: / Line 40: @@
 *Uphold our local organizational '''policies''' as well as the accepted laws related to your work.
 *Do not '''abuse''' Free Geek's resources, and help to prevent others from doing the same (excessive network traffic, excessive printing).
-*Try not to be '''annoying'''; people will complain much soon if something bothers them than if something is just broken.
+*Try not to be '''annoying'''; people will complain much sooner and louder if something bothers them than if something is just broken.
 *Do what it takes to '''understand''' the implications of your actions before taking them, so that you can knowingly apply these priorities.
@@ Line 44: / Line 47: @@
 * Tape Swapping - Weekly <small>(Richard)</small>
 * Test UPSes in server room - once per week/ASS meeting/month
-* apt-get upgrade - once per month or sooner if critical security holes
+* apt-get upgrade - check nagios, or once per month
-* freekbox dist-upgrade - weekly chroot into /usr/local/clones/freekbox/ and do and update/dist-upgrade
 * Reporting debian bugs
 *: <code>$ reportbug PACKAGENAME</code> - or - <code>$ reportbug --no-check-available PACKAGENAME</code>
@@ Line 54: / Line 56: @@
 *: http://archive.ubuntu.com/ubuntu/dists/ * /main/installer-i386/current/images/netboot/
 * [[Service List|Services provided to other groups]]
-== Projects ==
-=== LDAP ===
-To integrate our account management and make it possible to change email passwords.
-;So far we have:
-* the ldap server itself is built, with ldap and sldap installed
-* we did a test run for authenticating a user on a remote machine which "worked"
-;What we need:
-* to better define how we will use ldap
-* to create better schema for our purposes
-* possibly put the ldap server into the dmz, if we want to authenticate mail with it.
-* review and update the security on the server (passwords, webmin, &c.)
 == More fun ==