Whilst I'm being annoying I seem to remember a discussion about the session encryption password and adding it onto the session create/edit form. You agreed that since it was in plain text in the .ini it wouldn't really be any less secure on the form and you were going to add it on to save us having to hack the .ini file.

Any chance?

Roy Lambert

Roy,

<< Whilst I'm being annoying I seem to remember a discussion about the
session encryption password and adding it onto the session create/edit form.
You agreed that since it was in plain text in the .ini it wouldn't really be
any less secure on the form and you were going to add it on to save us
having to hack the .ini file. >>

It's still on the list.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


This is sort of related. To gain access to the live and development databases simultaneously, both of which are protected by the same encryption password I have to:

1. Create the session in EDBManager
2. BEFORE creating the databases open the ini file and change the local encryption password
3. Go back into EDBManager and set up the databases

I'd forgotten the sequence since Monday and it just took me 20 minutes of pratting about before I remembered


Roy Lambert

Dnia 28-09-2009 o 19:40:17 Roy Lambert <roy.lambert@skynet.co.uk>  =

napisa=B3(a):

> Whilst I'm being annoying I seem to remember a discussion about the  =

> session encryption password and adding it onto the session create/edit=
 =

> form. You agreed that since it was in plain text in the .ini it wouldn=
't  =

> really be any less secure on the form and you were going to add it on =
to  =

> save us having to hack the .ini file.
>
> Any chance?

You can always prepare and recompile your custom EDBManager

-- =

best regards,
Piotr Front