Difference between revisions of "ASS"
Jump to navigation
Jump to search
Stillflame (talk | contribs) (→ASS Priorities: sentences, even) |
Stillflame (talk | contribs) (→ASS Priorities: emboldening) |
||
| Line 29: | Line 29: | ||
Here is a list of what ASSes should prioritize when making decisions. | 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. | + | *'''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 effective '''security'''; stop people from doing things that they shouldn't be doing. |
| − | *Maintain data integrity for our users and our systems. | + | *Maintain '''data''' integrity for our users and our systems. |
| − | *Do not violate or let be violated the privacy of your users. | + | *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) | + | *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. | + | *Minimize and mitigate any '''downtime''' that happens or is necessary to have. |
| − | *Be | + | *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. | + | *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). | + | *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 soon 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. | + | *Do what it takes to '''understand''' the implications of your actions before taking them, so that you can knowingly apply these priorities. |
== Ongoing Tasks == | == Ongoing Tasks == | ||
Revision as of 12:39, 29 September 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):
- Martin Chase
- Michael Westwind
- Richard Seymour
- wren ng thornton
- Dave Haskins
- Kenny
- Joren
- Jeff
- Paul Brett
- Matteo
- Vagrant
- Stacy
Vancouver, BC, Canada ASSes:
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 soon 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 - once per month or sooner if critical security holes
- freekbox dist-upgrade - weekly chroot into /usr/local/clones/freekbox/ and do and update/dist-upgrade
- 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
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
Some folks at Free Geek or in our extended community are CA Cert Assurers. See the page.