Re: [Firebird-devel] Odp: execute statement on external role

2015-02-07 Thread Geoff Worboys
liviusliv...@poczta.onet.pl wrote: > Hi, > what security risk do you see with context vars? > Context vars are stored on server side - what i am missing > here? > This so secure as secure is sending password at conection > start time ;-) > I you secure transmision what problem? > regards, > Karol

Re: [Firebird-devel] Odp: execute statement on external role

2015-02-07 Thread Geoff Worboys
Alex Peshkoff wrote: > On 02/07/15 03:20, Geoff Worboys wrote: >> Simple? Well, I guess it is if I don't have any care about >> security. But context variables are not the way to do this >> sort of thing, load on demand from a secured table is a less >> open way of dealing with such private data.

Re: [Firebird-devel] Odp: execute statement on external role

2015-02-07 Thread Alex Peshkoff
connection time when SRP is used. > I you secure transmision what problem? > > regards, > Karol Bieniaszewski > > -Oryginalna wiadomość- > From: Geoff Worboys > Sent: Saturday, February 07, 2015 1:20 AM > To: For discussion among Firebird Developers > Subject: R

Re: [Firebird-devel] Odp: execute statement on external role

2015-02-07 Thread liviuslivius
: Geoff Worboys Sent: Saturday, February 07, 2015 1:20 AM To: For discussion among Firebird Developers Subject: Re: [Firebird-devel] Odp: execute statement on external role Simple? Well, I guess it is if I don't have any care about security. But context variables are not the way to do this

Re: [Firebird-devel] Odp: execute statement on external role

2015-02-07 Thread Alex Peshkoff
On 02/07/15 03:20, Geoff Worboys wrote: > Simple? Well, I guess it is if I don't have any care about > security. But context variables are not the way to do this > sort of thing, load on demand from a secured table is a less > open way of dealing with such private data. In FB3 one also can rathe

Re: [Firebird-devel] Odp: execute statement on external role

2015-02-06 Thread Geoff Worboys
Simple? Well, I guess it is if I don't have any care about security. But context variables are not the way to do this sort of thing, load on demand from a secured table is a less open way of dealing with such private data. But I got exactly what I wanted, without spreading passwords around, with