From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8939 invoked by alias); 22 Jan 2003 13:40:41 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 8931 invoked from network); 22 Jan 2003 13:40:40 -0000 Received: from unknown (HELO jifvik.dyndns.org) (62.253.130.87) by 172.16.49.205 with SMTP; 22 Jan 2003 13:40:40 -0000 Received: from eCosCentric.com (garibaldi.jifvik.org [172.31.1.2]) by jifvik.dyndns.org (Postfix) with ESMTP id A3AED3748D; Wed, 22 Jan 2003 13:40:25 +0000 (GMT) Message-ID: <3E2E9F47.4020400@eCosCentric.com> Date: Wed, 22 Jan 2003 13:40:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021203 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Jason Molenda Cc: overseers@sources.redhat.com Subject: Re: Status of FOM as I head off to bed References: <3E2E1FB8.1090608@eCosCentric.com> <20030121234408.A18687@molenda.com> <20030122011030.A30159@molenda.com> In-Reply-To: <20030122011030.A30159@molenda.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00178.txt.bz2 Jason Molenda wrote: > I've asked jifl, the maintainer of the ecos > database, to see if he can get to that install page. If that > doesn't work for him, I'll see about forcing new admin passwords > or whatever is necessary. Sorry, was asleep :-). Yes I can get to the install page - the old login/password worked fine, and after I went through all the checklist on the install page (not just the define configuration parameters appears) it is all happy. Thanks for working on this Jason! > FOM stores hashes of each user's password in one of its config files. > In 2.709 these hashes were crypt() strings. Now they're 128-bit > md5 hashes. I _suspect_ that FOM will update the passwords as users > log in, but I don't know that for certain. (I looked over all the > release notes foreach release and found no mention of this problem) > > If anyone logs in as an admin, keep this caveat from one of the > release notes in mind for that first install-login: > > WHEN YOU UPGRADE TO 2.714, YOU MUST BE CERTAIN TO PASS THROUGH > THE "Define Configuration Parameters" PAGE. > > You shouldn't have to actually define any parameters; the defaults > are fine if you use GNU RCS. But you must pass through that page > to get the args defined; otherwise RCS will get called with empty > options and will end up making a mess of things. (A reversible > mess, but a mess nonetheless.) I don't know if it made a mess because the faq was online before I went through the configuration parameters. Probably not - at the very least it looks okay from the outside regardless. > If, when you upgrade, you consistently follow the directions (go > to the installer page and check off the newly-unchecked boxes), > you'll be fine. I discovered this problem because I cheated and > just checked the "Mark the config file as upgraded" box, to make > the "admin must run installer" message go away. :v) I got 100 or so of those :-). At the very least it's stopped sending them now! Thanks again for getting this going again Crash. You're a star. Jifl -- eCosCentric http://www.eCosCentric.com/ --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine