[prev in list] [next in list] [prev in thread] [next in thread] 

List:       majordomo-users
Subject:    Re: Setting changes
From:       horen <horen () fto ! nsw ! gov ! au>
Date:       2000-11-23 6:46:20
[Download RAW message or body]

Thanks for your time and expertise Dan, I appreciate it. I have also been 
advised to check out my cron files, so I'll let you know how that all 
goes.

Cheers

Nick Hore

>I have a few suggestions again.
>
>Send majordomo@your.domain a config command to get a copy of the current
>configuration file for your list(s).
>
>config <listname> <list_passwd>
>passwd <listname> <old_passwd> <new_passwd>
>
>Edit this .config that gets sent back to you in the "majordomo results"
>email message to change "admin_passwd = <empty>".  Be careful of line
>wrapping when returning this file.  Either disable line wrap or set it
>to something high like 132.
>
>Send this .config file back to majordomo@your.domain with the newconfig
>command.
>
>newconfig <listname> <new_passwd>
>
>If this does not stop the config regression to older versions, someone
>definately has access to the file system and is able to modify your 
>majordomo configs at the OS level, or at least has the capability to 
>read your password settings and make the changes via email.  If you 
>have OS level shell access to the files, you will want to archive the
>listname.old.config and listname.config.save files, then delete them.
>
>Files related to your list that are acceptable in the lists directory
>are; listname listname.config listname.closed listname.private 
>listname.passwd listname.intro listname.info listname.strip and 
>listname.hidden.  The .closed .private .strip and .hidden files act
>as if your .config file had specific access rights restricted with
>internal settings, filters, or functions.  You probably to NOT want
>any of these except .config .passwd .intro and .info.  Make sure the
>.passwd file is not a link to somewhere else.
>
>Dan Liston
>
>horen wrote:
>> 
>> Thanks for your response Dan. It certainly is messing with my un-unix
>> head. I'm pretty sure that the list hasn't been hacked - it has only been
>> recently set up, and the hacker is doing the same old thing, each
>> evening. I'm sure they'd be having more fun than this by now. Another
>> thing that I have noticed, though, is that the config files for the two
>> lists I'm looking after seem to have dissappeared from the
>> /usr/local/majordomo/lists folder. Instead there is a listname.old.config
>> and a listname.config.save for one of the lists and a listname.old.config
>> for the other. It appears to work despite this, but it is weird, no?
>> 
>> Nick Hore
>> 
>> >It sounds like you have an rdist issue or a sysadm that is messing
>> >with your head.  Time to talk to the owner of the box.  It is also
>> >possible that your list has been hacked, and someone now has the
>> >admin password and is periodicly sending an old config file back
>> >to the server.
>> >
>> >Dan Liston
>> >
>> >horen wrote:
>> >>
>> >> I'm  having a problem maintaining my settings, particularly aliases,
>> >> admin passwords, the subscription policy and the command rights and
>> >> access command settings. I'll set them and they seem fine for a short
>> >> while, but then by the next day they have often reset. Any suggestions?


----------------------------------------------------------
Nick Hore, New Media, NSW Film and Television Office
GPO Box 1744, Sydney NSW 1043 Tel: +61 2 9264 6400 Fax: +61 2 92644388  
email: horen@fto.nsw.gov.au   web: http://www.fto.nsw.gov.au

[prev in list] [next in list] [prev in thread] [next in thread]