Re: [BUGS] Security problem in psql frontends

2000-11-13 Thread Tom Lane

[EMAIL PROTECTED] writes:
> I can connect to the database with a valid username and with a false
> password. Why ?

No doubt it's because you've got pg_hba.conf set to "trust" ...
passwords aren't checked unless pg_hba.conf specifies a password-
based authentication mechanism.  See
http://www.postgresql.org/users-lounge/docs/7.0/postgres/security.htm

regards, tom lane



[BUGS] JDBC driver DatabaseMetaData.getTables() unconditionally lowercases tableName pattern

2000-11-13 Thread pgsql-bugs

Dave Barnett ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
JDBC driver DatabaseMetaData.getTables() unconditionally lowercases tableName pattern

Long Description
According to Chapter 2 of the User's Guide, NAMES may be quoted to preserve case.  In 
the JDBC driver found in Postgres 7.0.2, jdbc2/DatabaseMetaData.java repeatedly 
converts the name pattern automatically to lowercase.  Removing these improper 
conversions provides usable behavior.

I think the driver shouldn't be doing anything to the pattern, so that the user may 
handle case conversions as needed.  Alternatively, the driver should simply not be 
doing this in the case that it is quoted.

Current workarounds:
1. modify driver code and recompile driver
2. provide a '%' tableName pattern and sift through all the tables in user code 
checking for proper matches

-Dave Barnett

Sample Code


No file was uploaded with this report




[BUGS] libpq dependencies in redhat binary rpm

2000-11-13 Thread thil

when I try to install the binary RPM for redhat 6.x,
the first rpm (postgresql-7*) say "dependencies error : libpq.so need".

I don't try --nodeps.

thank.



Re: [BUGS] libpq dependencies in redhat binary rpm

2000-11-13 Thread Lamar Owen

thil wrote:
> 
> when I try to install the binary RPM for redhat 6.x,
> the first rpm (postgresql-7*) say "dependencies error : libpq.so need".

Install -devel along with it.  I am updating the distributed RPM's now
to take care of this embarrassing typo.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11



[BUGS] PostgreSQL fails to build [ Solaris 8 ]

2000-11-13 Thread webmaster


I am getting a error while trying to compile
PostgreSQL on my Solaris Sparc 20.

Solaris 8

Attach is the error I'm getting when I ran gmake.

# uname -a
SunOS SPARC20 5.8 Generic sun4m sparc SUNW,SPARCstation-20


---
# gmake --version
GNU Make version 3.78.1, by Richard Stallman and Roland McGrath.
Built for sparc-sun-solaris2.8
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99
Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

Report bugs to <[EMAIL PROTECTED]>.

---
# ./configure  
loading cache ./config.cache
checking host system type... sparc-sun-solaris2.8
checking echo setting...
checking setting template to... solaris_sparc_gcc
checking whether to support locale... disabled
checking whether to support cyrillic recode... disabled
checking whether to support multibyte... disabled
checking setting DEF_PGPORT... 5432
checking setting DEF_MAXBACKENDS... 32
checking setting USE_TCL... disabled
checking setting USE_PERL... disabled
checking setting USE_ODBC... disabled
checking setproctitle... disabled
checking setting ASSERT CHECKING... disabled
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking whether gcc needs -traditional... (cached) no
- setting CPPFLAGS= 
- setting LDFLAGS= 
checking setting debug compiler flag... using default
checking for c++... (cached) c++
checking whether the C++ compiler (c++   ) works... yes
checking whether the C++ compiler (c++   ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking for include  in C++... yes
checking for namespace std in C++... yes
checking for a BSD compatible install... /usr/Data/TMP/postgresql-7.0.2/src/install-sh 
-c
checking for flex... (cached) flex
checking for yywrap in -lfl... (cached) yes
checking whether ln -s works... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
checking for ranlib... (cached) ranlib
checking for find... (cached) /usr/bin/find
checking for tar... (cached) /usr/sbin/tar
checking for split... (cached) /usr/bin/split
checking for etags... no
checking for xargs... (cached) /usr/bin/xargs
checking for gzcat... (cached) /usr/bin/gzcat
checking for perl... (cached) perl
checking for bison... (cached) /opt/sfw/bin/bison
- Using /opt/sfw/bin/bison -y -d
checking for main in -lsfio... (cached) no
checking for main in -lncurses... (cached) yes
checking for main in -ltermcap... (cached) yes
checking for main in -lreadline... (cached) yes
checking for using_history in -lreadline... (cached) yes
checking for main in -lbsd... (cached) no
checking for main in -lutil... (cached) no
checking for main in -lm... (cached) yes
checking for main in -ldl... (cached) yes
checking for main in -lsocket... (cached) yes
checking for main in -lnsl... (cached) yes
checking for main in -lipc... (cached) no
checking for main in -lIPC... (cached) no
checking for main in -llc... (cached) no
checking for main in -ldld... (cached) no
checking for main in -lln... (cached) no
checking for main in -lld... (cached) no
checking for main in -lcompat... (cached) no
checking for main in -lBSD... (cached) no
checking for main in -lcrypt... (cached) yes
checking for main in -lgen... (cached) yes
checking for main in -lPW... (cached) no
checking for ANSI C header files... (cached) no
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking for arpa/inet.h... (cached) yes
checking for crypt.h... (cached) yes
checking for dld.h... (cached) no
checking for endian.h... (cached) no
checking for float.h... (cached) yes
checking for fp_class.h... (cached) no
checking for getopt.h... (cached) no
checking for history.h... (cached) no
checking for ieeefp.h... (cached) yes
checking for limits.h... (cached) yes
checking for netdb.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for readline.h... (cached) no
checking for readline/history.h... (cached) yes
checking for readline/readline.h... (cached) yes
checking for sys/select.h... (cached) yes
checking for termios.h... (cached) yes
checking for unistd.h... (cached) yes
checking for values.h... (cached) yes
checking for sys/param.h... (cached) yes
checking for pwd.h... (cached) yes
checking for working const... (cached) yes
checking for inline... (cached) inline
checking for preprocessor stringizing operator... (cached) yes
checking for uid_t in sys/types.h... (cached) yes
checking for mode_t... (cached) yes
checking for off_t... (cached) yes
checking for size_t... (cached) yes
checking 

[BUGS] no meaningful way to determine fe or be version?

2000-11-13 Thread pgsql-bugs

Paul M. Aoki ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
no meaningful way to determine fe or be version?

Long Description
both the odbc and jdbc drivers seem to hardcode the database version, e.g., 
org/postgresql/jdbc2/DatabaseMetaData.java always returns "6.5.2" when you call 
getDatabaseProductVersion().

it would be nice if the metadata routines were actually tied to something returned 
from the backend.

Sample Code


No file was uploaded with this report




[BUGS] no way in LargeObject API to detect short read?

2000-11-13 Thread pgsql-bugs

Paul M. Aoki ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
no way in LargeObject API to detect short read?

Long Description
org.postgresql.largeobject.LargeObject.read(byte[],int,int) returns void instead of 
int.  there's therefore no reliable, non-exceptional way to detect short reads.

the natural way to write blocked-read loops would be to assume that 
read(byte[],int,int) returned the number of bytes read or (e.g.) -1 on EOF.

Sample Code


No file was uploaded with this report