[Firebird-devel] [FB-Tracker] Created: (CORE-3878) DatabaseAccess default changed in 2.5+ unintentionally?

2012-06-25 Thread Helen Borrie (JIRA)
DatabaseAccess default changed in 2.5+ unintentionally? --- Key: CORE-3878 URL: http://tracker.firebirdsql.org/browse/CORE-3878 Project: Firebird Core Issue Type: Bug Components:

[Firebird-devel] [FB-Tracker] Created: (CORE-3877) isc_decode_timestamp() unconditionally sets tm_isdst to 0 in the output struct tm

2012-06-25 Thread Vadim Zeitlin (JIRA)
isc_decode_timestamp() unconditionally sets tm_isdst to 0 in the output struct tm - Key: CORE-3877 URL: http://tracker.firebirdsql.org/browse/CORE-3877 Project: Firebird

[Firebird-devel] strange gbak failure

2012-06-25 Thread Frank
Hi, we had two strange failures on one of our servers recently: 21.06.2012 22:53:33 Database mandant1/bvmp.fdb will be recreated! /usr/local/firebird/bin/gbak -user SYSDBA -password XXX -c /opt/BVMP/Daten/backup/mandant1/bvmp.fbk /opt/BVMP/Daten/mandant1/bvmp_7d53eddb10.fdb gbak: ERROR:database sh

Re: [Firebird-devel] Testing fix for CORE-3860 (Trace API)

2012-06-25 Thread Thomas Steinmaurer
>> downloaded todays snapshot build. While a faulty database filter doesn't >> crash the server anymore, I wonder if it is a security breach, when the >> physical path of the security database is transferred to the trace >> client. A typical trace output looks like that now: >> >> Trace session ID

Re: [Firebird-devel] Testing fix for CORE-3860 (Trace API)

2012-06-25 Thread Vlad Khorsun
> downloaded todays snapshot build. While a faulty database filter doesn't > crash the server anymore, I wonder if it is a security breach, when the > physical path of the security database is transferred to the trace > client. A typical trace output looks like that now: > > Trace session ID 1

[Firebird-devel] Testing fix for CORE-3860 (Trace API)

2012-06-25 Thread Thomas Steinmaurer
Hello, downloaded todays snapshot build. While a faulty database filter doesn't crash the server anymore, I wonder if it is a security breach, when the physical path of the security database is transferred to the trace client. A typical trace output looks like that now: Trace session ID 1 star