Bug#485562: Preparation of next package and : Re: Bug#485562: twiki: configure script access badly protected

2008-06-28 Thread Christian Perrier
Quoting Olivier Berger ([EMAIL PROTECTED]):

> I guess that if you provide a 4.2 package soon, at the same time as the
> patch for 4.1.2 is prepared, uploading by your sponsor should be
> coordinated with Christian Perrier's one, to avoir locking each-other.
> I'd propose 4.1.2-3.2 to be going to testing/testing-security real fast
> (via unstable), and 4.2 be kept in experimental in the meantime maybe...

That sounds to be a good plan. Having the "polished" 4.1.* version go
its way through testing and then have 4.2 follow the same way.

(if 4.2 introduce changes tha impact debconf l10n, we could even do a
translation update round for it even while it is sitting in
experimental).

So, to summarize:

- Olivier polishes 4.1.2-3.2 (ou -4 depeds on whether this is still
considered an NMU or not), including debconf templates wording
- He sends me at least the templates file and the full patch to Sven
- I post a call for translation for 4.1.2
- translators have 10 days to update
- I summarize translator's work (usually with a big tarball of
debian/po as I check every incoming PO file)
- Olivier prepares 4.1.2-3.2 (or -4) with that
- I sponsor it


While I work on 4.1.2 l10n, Sven adopts Olivier's changes and prepares
a 4.2 upload. If that needs changes to debconf templates, we review
them and I send *another* call for translation updates juste after the
above 10 days delay (so that translations sent for 4.1 can be reused
as a basis for 4.2). Then, summary and  upload to experimental (I can
sponsor here, again).

And, once 4.1 reaches testing, you guys can upload 4.2 to unstable.




signature.asc
Description: Digital signature


Bug#485562: Preparation of next package and : Re: Bug#485562: twiki: configure script access badly protected

2008-06-28 Thread Olivier Berger
(keeping [EMAIL PROTECTED] out of the CCs as I think
this becomes quite specific to twiki's packaging and not so much about
translations)

Le samedi 28 juin 2008 à 18:04 +1000, Sven Dowideit a écrit :

> I would suggest using 'TWiki Configure User & Password' and setting the
> configure save pwd to the same thing. 

I see your point.

Well... in the proposed patch for an NMU I haven't (yet) tried and do
something about the configure script's internal save password I
don't know actually how this is encrypted and such.

That would make sense to change it from the package's scripts too... but
leads to more testing and less time to market considering a security
issue (we already added more delay with templates discussions) :-/

> (and making the username for it
> 'admin')
> 

Of course providing a better transition path for next package would be
better.

I guess the 'configuser' debconf variable should probably be renamed as
'adminuser' and its default value in template 'admin' then.

I'll provide an updated patch for Christian real soon now so that the
templates are dispatched to translators (btw, I fixed some minor issue
with the password resetting I hadn't noticed in previous tests :( ).

> That way it will not need to change for the 4.2.x package, where there
> is an internal admin user, whose password is the same as the configure
> save password, and will also be used to authenticate to get to the
> configure script.
> 
> 
> I might still hammer out a 4.2.0 package tomorrow, but no breath holding
> please.
> 

I guess that if you provide a 4.2 package soon, at the same time as the
patch for 4.1.2 is prepared, uploading by your sponsor should be
coordinated with Christian Perrier's one, to avoir locking each-other.
I'd propose 4.1.2-3.2 to be going to testing/testing-security real fast
(via unstable), and 4.2 be kept in experimental in the meantime maybe...
just to be sure it's mature enough for the freeze... I'd better welcome
a 4.1.2 more secure and tested in lenny, than a not yet fully tested
4.2... but you may have a better view of the advantages of 4.2 of
course.

Anyway, good luck for that new package.

Best regards,

> 
> Sven
> 
> Justin B Rye wrote:
> > Olivier Berger wrote:
> >> *Should be "apache" in all three.*
> >>
> >> By "apache user", I mean something which relates to Require user in the
> >> apache.conf section of the 'configure' script... of course, this assumes
> >> that it's running apache and no other web server ;)
> >>
> >> In any case, that's meant to differenciate from "TWiki users", which are
> >> managed "inside twiki".
> > 
> > I'm still not quite convinced by the expression "apache user", but I
> > can't decide what alternative I'd suggest.
> > 
> > The trouble with "apache user" is that it might mean the local
> > system's www-data, or maybe the owner of the computer, rather than
> > a browser-user authenticated via mod_auth_basic...
> > 
> >  _Description: User allowed access to 'configure' script
> >   Please enter the name of the  user who will be allowed
> >   to run the configure script at ${site}/cgi-bin/configure.
> > 
> >  _Description: Password for ${configuser}:
> >   Please enter the password of the  user who will be allowed
> >   to run the configure script at ${site}/cgi-bin/configure.
> > 
> > Where "" is... "HTTP"?  "authenticated"?  "htpasswd"?
> 

-- 
Olivier BERGER <[EMAIL PROTECTED]>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]