right, i understand this; (and trust me, the directory is well secured) but
i can, say, if i'm using the perl5 Pg module, pass an unencrypted password
to Pg::connectdb and it still connects, with no encryption. i couldn't
find any calls to crypt() in the Pg source code, either.
On Wed, Dec 22,
Hi.
I am trying to do a interface from a web over my database postgresql
whit libpq.
I can't do a simple 'insert' from libpq.
I'm doing this:
sprintf(temp_string,"insert into clientes
values('fff','prueba','123','123','pepe gotera','jj','jjj')");
res1=PQexec(conn,temp_string);
tu
Hello,
On Wed, 22 Dec 1999, Nicolas Huillard wrote:
> The problem of the pg_passwd command (used to feed the password.dbname
> files) is that is only stores 8 characters from the username provided,
> even if you typed more, and even if the Postgres username have more
> characters. I don't know i
I'm trying to install PostgreSQL 6.5.3 on an SGI IRIX 6.5. I have
installed with succes GNU make 3.77 in /usr1/src/make-3.77 and GNU
readline in /usr/local/.
In the following directory (/usr1/src/postgresql-6.5.3/src/), I have run
this command :
sh ./configure --with-includes=/usr/local/include
The problem of the pg_passwd command (used to feed the password.dbname files) is that
is only stores 8 characters from the username provided, even if you typed more, and
even if the Postgres username have more characters.
I don't know if one can add the missing characters or create the file with
Hello,
On Tue, 21 Dec 1999, Tim Perdue wrote:
> There's got to be a way to create multiple
> databases and have each one protected by a
> different username/password. Right now, any
> authorized user can connect to any database. Grant
> only works on tables, which is not useful in this
> case (g
The workaround I use is via the pg_hba.conf file : my users connect remotely from
various locations. Each location is granted for one DB only :
hostthe_db 123.45.67.89255.255.255.255 password
This way, the problem is reversed : everyone can connect to "the_db", from the
"123.45.6
