Re: [Rds-wc1-propaganda] (no subject)

[Simon P. <sim...@ya...>]

Hi guys,

I don't know whether your DB security idea would work regulatre (I could be
totally wrong - I ain't no MySQL guru!) as if you set up a table in the DB
with sensitive data that was accessed by a page you'd need to create a
non-password DB user to get the required info.  As I say, I could be totally
wrong, I dunno.

On the suggestion of a Flash intro...please, please, no!!!! Flash is
brilliant, I love Flash, but only when usefully and effectively employed.
Intro movies (unless for a music or film site) are a) overkill b) prevent
users from getting straight to the content and c) annoy users (if they don't
annoy you then that's fine, but they annoy me and many other web users I
know!).  Woo, got that out my system!  Well there's my opinion on the
matter, make of it what you like :-p

Nimnr's site layout is quite similar to one that nerv and I thought was
reasonable (sorry I didn't mention it earlier)...

- Main Page
- About RDS-WC1
     -- Features
     -- Team
- Downloads
     -- CVS
     -- Source
     -- Binaries
- Documentation
     -- HTML
     -- Plaintext
- Forum
- Tutorials
- Best Cam Shots
- Links
     -- SourceForge

How does that sound?  A login box could be incorporated into the main
navigation and then users would granted to the relevant facilities as
appropriate (e.g. the team has access to admin, cms etc. and general users
only have access to the public forum and say a profile or something).

I'll need to discuss the admin section with you later nimnr, and also how to
connect the home and files section with the CMS you're developing.  I had
previously agreed to create the site templates (i.e. include();) from nerv's
designs.  I'm happy to still do this if that's OK with you.

Anyways, sorry for rambling on so much.

Catch ya l8r,
Simon

----- Original Message -----
From: <rd...@ex...>
To: <rds...@li...>
Sent: Friday, May 31, 2002 5:52 PM
Subject: [Rds-wc1-propaganda] (no subject)


>
>
> Ok, I've got some good news and some bad news... first the bad news:
> SF isn't interested in providing for security of sensitive files, such as
> those we'd like to publish on our website. see the ticket I submitted
> here:
>
>
http://sourceforge.net/tracker/?func=detail&atid=200001&aid=562752&group_id=
1
>
>
> The good news is I have an idea to overcome this shortcoming:
> Why not use our mysql database on SF to store the sensitive information.
> we could for instance create a table called "sensitive" and store
> sensitive shit there.
> Password=xxx
> username=xx
> othersecretstuff=xxx
> whatever...
>
> With minimal recoding of the sensitive file, we can make the PHP
> sourcefiles read in the sensitive information from our database.
>
> As soon as we all sync thoughts on this, I'd like to then reset our SF
> mysql password (because its already been exposed) at which time we
> can then implement this security table.
>
> I don't know the best way of implementing the details of this, so I'll let
> one of you mySQL gurus do the implementation =)
>
> remember: DO NOT create the security table UNTIL I've reset our MySQL
> password.
>
>
> Hasta luego
> Brad
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Rds-wc1-propaganda mailing list
> Rds...@li...
> https://lists.sourceforge.net/lists/listinfo/rds-wc1-propaganda