[IMC-Tech] root access to groogroo

[Zach M]

The only thing apache2 is doing on port 8080 right now is
svn.cuwireless.net stuff. Please don't disturb that in the process of
porting other sites over.

On 7/9/06, Zachary C. Miller <zach at chambana.net> wrote:
> Note: apache2 is already installed and running on port 8080.
>
> "Upgrading" apache means moving the apache1 configs into apache2's
> more module format at /etc/apache2/sites-enabled
>
> Once all the sites are configured in /etc/apache2/sites-enabled (one
> config for each site) and we test them all on port 8080 then we can
> run apache2 on port 80.
>
> In the mean time you can configure the existing apache2 to do SSL
> stuff on the normal https port (443) as we are not running anything on
> that port.
>
> On 7/9/06, dan blah <dan.blah at gmail.com> wrote:
> > media wiki does this also (the one already installed).  i will work on
> > the ssl server as well as upgrading apache and hopefully fixing our
> > problem.  i was wondering what your uid was stephane so that i could
> > give you perms to the wiki directory.  this way you can install/manage
> > wiki extenstions that you needed
> > (http://meta.wikimedia.org/wiki/Category:MediaWiki_extensions).  with
> > extensions there are a whole list of security things that could be
> > implemented.
> >
> > On 7/6/06, Zachary C. Miller <zach at chambana.net> wrote:
> > > Trac will do this. It has a very good authentication system. If
> > > someone can set up an SSL webserver we can issue personal SSL
> > > certificates that identify individual users and with a simple 4 line
> > > patch Trac can use that identity internally with it's permission
> > > system (instead of the cookies it currently uses). This (Trac + SSL
> > > certs for authentication)  is what we use at work. Someone will have
> > > to set it up though.
> > >
> > > Trac is what is running at tech.chambana.net.
> > >
> > > On 7/6/06, Stephane Alnet <stephane at shimaore.net> wrote:
> > > > > oh i already did it before i left... must have forgot to tell
> > > > > everyone.  currently its at http://www.ucimc.org/wiki
> > > >
> > > > The questions that were still opened were around security and
> > > > restricting access to sections of the wiki. I've no experience with
> > > > mediawiki so I can't talk to these, but basically we don't want to
> > > > post internal finance documents on an open wiki.
> > > >
> > > > So we need a wiki that supports the notions of "group" (or ACLs or
> > > > whatever) and has the capability of restricting write _and_ read to
> > > > given pages.
> > > > Ideally we could also use some level of encryption, but that's optional.
> > > >
> > > > If MediaWiki can do it that's great, but I wasn't under the
> > > > impression it could.
> > > > S.
> > > >
> > > >
> > >
> >
> >
> > --
> > Daniel
> >
> >
>