Differences

This shows you the differences between two versions of the page.

--- transition1 [2008/02/25 17:04]
4.245.75.44
+++ transition1 [2009/08/13 17:54] (current)
4.245.76.16 old revision restored
@@ Line 1: / Line 1: @@
 ====== Transition from michelob and dark to bud and budlight ======
+===== Status update 03/07/2008 =====
+As was previously announced SLUUG's bud server was reloaded on 03/02/08 because it had been compromised again.  While it is not certain, the appearance is that entry might have been by one or more unused accounts.  One possibility is that these accounts had weak passwords that hadn't been changed as required after the previous security problems.  As a result of this, login to bud has been disabled pending further security planning.  You can still access bud from your mail client to retrieve mail via POP or IMAP, with the encrypted protocl recommended.  You can also send mail via bud using your mail client the same as before.
+While the budlight and michelob servers were not affected this time, there is no reason to assume they are immune.  Please logon to budlight and michelob, and change your password on them.  Since login to bud is disabled, you can't change your password there.  Use good sense to use different passwords on each system.  Use seomething not easy to guess, not in the dictionary, at least eight characters long, include combinations of letters/numbers/symbols, etc.
+It was previously announced that mail was not working on budlight.  This was resolved a while back, so mail can be sent from budlight by programs, personal web site applications, and local mail clients such as mutt.  Since bud is the main mail server, mail sent from budlight will be routed to bud for delivery, and the default return address will be @sluug.org, so replies will go to your inbox on bud.  Budlight is configured to not receive mail.  If you have a mail client on a home system, such as Thunderbird or Outlook, it should use bud.
 ===== Status update 02/25/2008 =====
-Sending mail when logged onto budlight is working.  If you have web pages, cron jobs, etc. that send mail to a different system, they will should work normally.  Mail sent from budlight will be identified as coming from sluug.org be default, and all incoming mail should be sent to sluug.org or mail.sluug.org.  The configuration of budlight is for it not to accept incoming mail, and your inbox is on bud, which can be accessed by POP or IMAP using many mail clients, including "mutt".  Access to the bud server is limited to mail, and bud is not intended for normal user login activities.
+Sending mail when logged onto budlight is working.  If you have web pages, cron jobs, etc. that send mail to a different system, they will should work normally.  Mail sent from budlight will be identified as coming from sluug.org by default, and all incoming mail should be sent to sluug.org or mail.sluug.org.  The configuration of budlight is for it not to accept incoming mail, and your inbox is on bud, which can be accessed by POP or IMAP using many mail clients, including "mutt".  Access to the bud server is limited to mail, and bud is not intended for normal user login activities.
 The default editor on Linux systems, such as budlight, appears to be "nano" instead of "vi", so other commands that invoke the editor will probably invoke the wrong one if you normally use vi.  The solution modify your shell's profile script, such as ".profile" to set the EDITOR variable to vi, for example, "EDITOR=vi".

SLUUG Wiki

User Tools

Site Tools

Differences

Page Tools