Bug#614374: pg_upgradecluster fails when datdba is a role without login privilege

2011-02-21 Thread Rafał Kupka
Package: postgresql-common
Version: 114
Severity: minor

Hi,

Script /usr/bin/pg_upgradecluster fails (silently drops data) on
databases which has datdba set as a role without login access.

I can narrow this bug to use of pg_user view in query:
select datname, datallowconn, pg_catalog.pg_encoding_to_char(encoding),
usename from pg_database, pg_user where datdba = usesysid
in line 375.

Not all roles/groups are shown in this view, I think that on postgresql
versions 8.1+ it's better to use query like this:
select datname, datallowconn, pg_catalog.pg_encoding_to_char(encoding),
rolname from pg_database, pg_authid where datdba = pg_authid.oid

Spotted on upgrade from 8.4 to 9.0 on debian/lenny (with backports) but
this database query is identical to official debian/stable (or sid)
package version.

Roles and privileges:
CREATE ROLE pol_admin;
ALTER ROLE pol_admin WITH NOSUPERUSER NOINHERIT NOCREATEROLE NOCREATEDB NOLOGIN;
GRANT pol_admin TO some_login_user;
ALTER DATABASE pol OWNER TO pol_admin;

Then pg_upgradecluster omit data (schema is created correctly) on pol
database.

Best regards,
Kupson




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#595366: portmap: Chroot(2) option brings no additional security due to implementation bug

2010-09-03 Thread Rafał Kupka
Hello,

I was wrong with openat() syscall, portmap daemon holds no open
directories outside chroot dir. But access to files outside /var/empty
is much easier -- use regular open(2) and relative pathnames.

Proof:
# lsof -n -p 7892
COMMAND  PID   USER   FD   TYPE DEVICESIZENODE NAME
portmap 7892 daemon  cwdDIR9,14096   2 /
portmap 7892 daemon  rtdDIR9,14096  295046 /var/empty
...

# gdb -p 7892
...
(gdb) print creat(./tmp/,0)
$1 = 8
(gdb) shell ls -l /tmp/
-- 1 daemon daemon 0 Sep  3 15:32 /tmp/

So, no security benefits from chroot(2).

Regards,
Kupson




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#520742: udev: udevd is started even when policy-rc.d says no, and fails with debootstrap.

2009-05-15 Thread Rafał Kupka
Hello,

I have following idea to solve that problem. Please check if it's good
solution.

Lets add additional test similar to chrooted() in post install script.

forbidden() {
  if [ -x /usr/sbin/policy-rc.d ];
/usr/sbin/policy-rc.d check_udevd start
case $? in
  0|1|100|105)
# action allowed:
#   0 - action allowed
#   1 - unknown action (therefore, undefined policy)
# 100 - unknown initscript id
# 105 - behaviour uncertain, policy undefined.
return 1
  ;;
  *)
# action forbidden
return 0
  ;;
esac
  fi
  # policy-rc.d missing, return false
  return 1
}

In chroot(2) or similar condition like debootstrap, xen-tools
etc. /usr/sbin/policy-rc.d prevents start of all daemons, so it will
deny fake initscript check_udevd too. More sophisticated policy-rc.d
scripts will return status 100 (unknown initscript) in this forbidden()
check and udevd will start as today.

Regards,
Rafal Kupka




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#512572: munin-cgi-graph don't work, wrong semget() return code check

2009-01-26 Thread Rafał Kupka
Dnia 2009-01-23, pią o godzinie 20:18 +0100, Holger Levsen pisze:
Hi,

 thanks for your bugreport and patch! What are the consequences of that bug?

Perl script munin-cgi-graph executes die() function and terminates
without producing graphic data. Browser don't show any munin charts.

Http server (lighttpd) error.log fragment:
Creating semaphore:  at /usr/lib/cgi-bin/munin-cgi-graph line 128.

Regards,
Kupson




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#419994: Missing memory in Xen due to wrong detection of e820 memory map in grub

2007-04-19 Thread Rafał Kupka
Dnia 19-04-2007, czw o godzinie 12:10 +0200, Rafal Kupka napisał:
Hello,

 I think that problem is located in do { } while (cont) loop at file
 stage2/common.c around line 181.
 It looks like while loop is optimized away (gone) during compilation.

I was wrong, on another motherboard grub (same iso image) works
correctly. So, it's not missing code but something more machine/BIOS
specific. I'll try to get some more information.

Kupson




Bug#419994: More information about misdetection of e820 memory map

2007-04-19 Thread Rafał Kupka
Hello,

I make some more tests to find this bug.

--- grub-0.97/stage2/common.c   2004-03-27 17:25:44.0 +0100
+++ new/stage2/common.c 2007-04-19 16:00:00.0 +0200
@@ -181,6 +181,7 @@
   do
 {
   cont = get_mmap_entry ((void *) addr, cont);
+  printf(SMAP: addr:%x cont:%x\n, (unsigned long *) addr, cont);
 
   /* If the returned buffer's length is zero, quit. */
   if (! *((unsigned long *) addr))
@@ -190,6 +191,7 @@
   addr += *((unsigned long *) addr) + 4;
 }
   while (cont);
+  printf(mbi.mmap_length: %x\n, mbi.mmap_length);
 
   if (mbi.mmap_length)
 {

After applying above patch I've got this messages from grub:
SMAP: addr:54964 cont:1
SMAP: addr:5497c cont:2
SMAP: addr:54994 cont:3
SMAP: addr:549ac cont:4
SMAP: addr:549c4 cont:5
SMAP: addr:549dc cont:6
SMAP: addr:549f4 cont:7
SMAP: addr:54a0c cont:8
SMAP: addr:54a24 cont:9
SMAP: addr:54a3c cont:a
SMAP: addr:54a54 cont:0
mbi.mmap_length: 108

displaymem command works as expected, shows whole memory map.

But If I modify source to this version below, I just got:
mbi.mmap_length: 0
and there is no memory map in displaymem output.

--- grub-0.97/stage2/common.c   2004-03-27 17:25:44.0 +0100
+++ new/stage2/common.c 2007-04-19 16:00:00.0 +0200
@@ -181,6 +181,7 @@
   do
 {
   cont = get_mmap_entry ((void *) addr, cont);
+  /* printf(SMAP: addr:%x cont:%x\n, (unsigned long *) addr, cont); */
 
   /* If the returned buffer's length is zero, quit. */
   if (! *((unsigned long *) addr))
@@ -190,6 +191,7 @@
   addr += *((unsigned long *) addr) + 4;
 }
   while (cont);
+  printf(mbi.mmap_length: %x\n, mbi.mmap_length);
 
   if (mbi.mmap_length)
 {

I don't understand how mbi.mmap_length may have different value just by
commenting printf out. Something strange happens :(

Maybe this is some BIOS breakage, but Linux kernel always detect memory
correctly.

Motherboards affected:
 - MSI K9N SLI Platinum (with BIOS 1.5)
 - MSI K9N SLI-2F (BIOS version unknown)

Regards,
Kupson



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#415811: xen-tools: use /usr/sbin/policy-rc.d in chroot instead of {enable, disable}StartStopDaemon

2007-03-22 Thread Rafał Kupka
Package: xen-tools
Severity: wishlist


Hello,

I think that it is better to use /usr/sbin/policy-rc.d to prevent
start services in chrooted environment.

Quote from /usr/share/doc/sysv-rc/README.policy-rc.d.gz:
#v+
POLICY-RC.D   Policy layer (/usr/sbin/policy-rc.d) interface:
=

Most Debian systems will not have this script as the need for a policy
layer is not very common. Most people using chroot jails just need an
one-line script which returns an exit status of 101 as the jailed
/usr/sbin/policy-rc.d script.
#v-

That would be more Debian-way (but IANADD[1]) to create this exit 101
script at first, before other hooks execution. Last hook can remove it
to make chroot system normal again.

What do you think?

Regards,
Rafal Kupka
[1] IANADD: I am not an Debian developer.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#411645: hddtemp: rc-script try to kill not running daemon on shutdown

2007-02-20 Thread Rafał Kupka
Package: hddtemp
Version: 0.3-beta15-34
Severity: minor
Tags: patch

Hello,

Script /etc/init.d/hddtemp wrongly checks when to kill 
(not started before) hddtemp daemon:

olimp:~# invoke-rc.d hddtemp stop
Stopping disk temperature monitoring daemon: hddtempNo /usr/sbin/hddtemp found 
running; none killed.
.

Small patch to fix it:
--- a/etc/init.d/hddtemp2007-02-20 11:22:32.0 +0100
+++ b/etc/init.d/hddtemp2007-02-20 11:26:58.0 +0100
@@ -73,7 +73,7 @@
;;
   stop)
# master switch
-   if [ $RUN_DAEMON = true -o $RUN_DAEMON = yes -o $SYSLOG != 
0 ] ; then
+   if [ $RUN_DAEMON = true -o $RUN_DAEMON = yes -o $RUN_SYSLOG 
!= 0 ] ; then
log_daemon_msg Stopping $DESC $NAME
start-stop-daemon --stop --oknodo --exec $DAEMON --retry 30
log_end_msg $?

Regards,
Kupson

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-xen-vserver-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages hddtemp depends on:
ii  debconf [debconf-2.0]   1.5.11   Debian configuration management sy
ii  libc6   2.3.6.ds1-11 GNU C Library: Shared libraries
ii  lsb-base3.1-23   Linux Standard Base 3.1 init scrip

hddtemp recommends no packages.

-- debconf information:
  hddtemp/port: 7634
  hddtemp/interface: 127.0.0.1
* hddtemp/daemon: false
* hddtemp/syslog: 0
* hddtemp/SUID_bit: false



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#405463: dvdisaster: GLib-ERROR **: gmem.c:154: failed to allocate ... bytes error on DVD-ROM dual layer media

2007-01-19 Thread Rafał Kupka
On 17-01-2007, at 10:37 +0100, Daniel Baumann wrote:
Hello,

 can you retry with libdvdcss installed?

I have libdvdcss installed all the time.

ii  libdvdcss-dev 1.2.9+debian-1duo+etch1
ii  libdvdcss21.2.9+debian-1duo+etch1

Packages are from http://ftp.debian-unofficial.org etch/main.
It looks like dvdisaster don't use libdvdread3 [1]:
utemp:~$ ldd $(which dvdisaster) | grep dvd
utemp:~$

Other programs (like self-compiled mplayer) uses libdvdcss via
libdvdread and play CSS protected DVDs correctly.

Regards,
Kupson
[1] Programs should link with libdvdread, which dynamically loads
libdvdcss if present in system. Am I right?




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#405463: dvdisaster: GLib-ERROR **: gmem.c:154: failed to allocate ... bytes error on DVD-ROM dual layer media

2007-01-12 Thread Rafał Kupka
Dnia 11-01-2007, czw o godzinie 22:10 +0100, Carsten Gnörlich wrote:
Hello,

 thanks for the info - I have an idea now where the crash is located.
 However I still do not fully understand what is needed to cause the crash.
 
  I realize that with option --query-size drive or udf dvdisaster don't
  crash.
 
 That is interesting. If my theory is right, 
 
 ./dvdisaster --query-size=drive -v -s
 
 will reveal that the drive is reporting silly stuff during the query. Anyone 
 care to verify or disprove ;-)

Here is the command output:
utemp:~$ dvdisaster --query-size=drive -v -s
...
Device: /dev/hda, HL-DT-STDVDRAM GSA-4167B DL13
Skipping medium size determination from ECC header.
Skipping medium size determination from ISO/UDF filesystem.
* Warning: Different media sizes depending on query method:
*  READ CAPACITY:  4072605 sectors
*  READ DVD STRUCTURE: 8589541377 sectors
*  
*  Evaluation of returned medium sizes:
*  
*  Sector 4072604: readable
*  Sector 4072605: Illegal Request; Logical block address out of range.
*  - READ CAPACITY looks GOOD
*  
*  Sector -393216: Illegal Request; Logical block address out of range.
*  Sector -393215: Illegal Request; Logical block address out of range.
*  - READ DVD STRUCTURE is UNUSABLE
*  
*  Final decision: Using value from READ CAPACITY
*  
Medium: DVD-ROM, 4072605 sectors, 2 layer(s)

Scanning medium for read errors.
Waiting 5 seconds for drive to spin up...
Sector 608: Illegal Request; Read of scrambled sector without authentication. 
Skipping 15 sectors.
more Illegal requests

Greetings,
Kupson
PS: It looks like I misjudged severity of this bug. Can we lower it now?





Bug#405463: dvdisaster: GLib-ERROR **: gmem.c:154: failed to allocate ... bytes error on DVD-ROM dual layer media

2007-01-09 Thread Rafał Kupka
Dnia 04-01-2007, czw o godzinie 20:25 +0100, Carsten Gnörlich napisał:
Hello,

  temp:~$ dvdisaster -r
 Could you give us the full output of dvdisaster -v -r as well,
 for the medium that produces the crash?

Sure.
utemp:~$ dvdisaster -v -r
dvdisaster-0.70  Copyright 2004-2006 Carsten Gnoerlich.
This software comes with  ABSOLUTELY NO WARRANTY.  This
is free software and you are welcome to redistribute it
under the conditions of the GNU GENERAL PUBLIC LICENSE.
See the file COPYING for further information.

Device: /dev/hda, HL-DT-STDVDRAM GSA-4167B DL13

ExamineUDF(HL-DT-STDVDRAM GSA-4167B DL13)
 Examining the ISO file system...
  Sector 16:
   Volume descriptor type= 1
   Volume descriptor version = 1
   Standard identifier   = CD001
   - primary volume descriptor:
System identifier : ||
Volume identifier : |12_MONKEYS  |
Volume space size : 4072605 sectors
Volume set size   : 1
Volume sequence size  : 1
Logical block size: 2048
Path table size   : 42 bytes
L-Path table location : 257
Opt L-Path table location : 0
M-Path table location : 258
Opt M-Path table location : 0
Volume creation date/time : 06-09-2006 10:24:42.00
Volume modification d/t   : 00-00- 00:00:00.00
Volume expiration d/t : 00-00- 00:00:00.00
Volume effective d/t  : 00-00- 00:00:00.00
File structure version: 1
  Sector 17:
   Volume descriptor type= 255
   Volume descriptor version = 1
   Standard identifier   = CD001
   - volume descriptor set terminator;
  end of ISO file system parsing.
 Examining the UDF file system...
  not yet implemented.

udf/try_sector: trying sector 4072605
udf/try_sector: read error, trying next header
udf/try_sector: trying sector 4072455
udf/try_sector: no cookie, skipping current modulo

GLib-ERROR **: gmem.c:154: failed to allocate 18446744073709502468 bytes
aborting...
Przerwane

I realize that with option --query-size drive or udf dvdisaster don't
crash.

Sadly this dvd happens to be CSS encrypted so no ecc protection is
possible.

Regards,
Kupson





Bug#405463: dvdisaster: GLib-ERROR **: gmem.c:154: failed to allocate ... bytes error on DVD-ROM dual layer media

2007-01-03 Thread Rafał Kupka
Package: dvdisaster
Version: 0.70.3-1
Severity: important

Dvdisaster on DVD-ROM dual-layer media exits with message:

temp:~$ dvdisaster -r
dvdisaster-0.70  Copyright 2004-2006 Carsten Gnoerlich.
This software comes with  ABSOLUTELY NO WARRANTY.  This
is free software and you are welcome to redistribute it
under the conditions of the GNU GENERAL PUBLIC LICENSE.
See the file COPYING for further information.

Device: /dev/hda, HL-DT-STDVDRAM GSA-4167B DL13

GLib-ERROR **: gmem.c:154: failed to allocate 18446744073709502468 bytes
aborting...
Przerwane

This bug exists in version 0.70.2-2 too.
One layer DVD-ROMs works fine. I cannot test dual layer DVD±R(W) media at
this moment.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)

Versions of packages dvdisaster depends on:
ii  libatk1.0-0  1.12.3-1The ATK accessibility toolkit
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libcairo21.2.4-4 The Cairo 2D vector graphics libra
ii  libfontconfig1   2.4.1-2 generic font configuration library
ii  libglib2.0-0 2.12.4-2The GLib library of C routines
ii  libgtk2.0-0  2.8.20-3The GTK+ graphical user interface
ii  libpango1.0-01.14.8-4Layout and rendering of internatio
ii  libx11-6 2:1.0.3-4   X11 client-side library
ii  libxcursor1  1.1.7-4 X cursor management library
ii  libxext6 1:1.0.1-2   X11 miscellaneous extension librar
ii  libxfixes3   1:4.0.1-5   X11 miscellaneous 'fixes' extensio
ii  libxi6   1:1.0.1-4   X11 Input extension library
ii  libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii  libxrandr2   2:1.1.0.2-5 X11 RandR extension library
ii  libxrender1  1:0.9.1-3   X Rendering Extension client libra

Versions of packages dvdisaster recommends:
ii  dvdisaster-doc0.70.3-1   data loss/scratch/aging protection

-- no debconf information





Bug#403057: azureus: throws java.lang.NoSuchMethodError: fixedClassInitProc exception on startup (amd64 specific)

2006-12-14 Thread Rafał Kupka
Package: azureus
Version: 2.5.0.0+0-1
Severity: important

Hello,

I don't exactly know it's azureus or swt-gtk bug. Please reassign if
appropriate.

Azeurus throws this exception on start (with sun-java5-jre):
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.gudy.azureus2.ui.common.Main.directLaunch(Main.java:225)
at org.gudy.azureus2.ui.common.Main.main(Main.java:132)
Caused by: java.lang.NoSuchMethodError: fixedClassInitProc
at org.eclipse.swt.internal.Callback.bind(Native Method)
at org.eclipse.swt.internal.Callback.init(Callback.java:123)
at org.eclipse.swt.internal.Callback.init(Callback.java:78)
at org.eclipse.swt.internal.Callback.init(Callback.java:60)
at
org.eclipse.swt.widgets.Display.createDisplay(Display.java:807)
at org.eclipse.swt.widgets.Display.create(Display.java:781)
at org.eclipse.swt.graphics.Device.init(Device.java:145)
at org.eclipse.swt.widgets.Display.init(Display.java:452)
at org.eclipse.swt.widgets.Display.init(Display.java:443)
at
org.gudy.azureus2.ui.swt.mainwindow.SWTThread.init(SWTThread.java:82)
at
org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(SWTThread.java:61)
at
org.gudy.azureus2.ui.swt.mainwindow.Initializer.init(Initializer.java:110)
at org.gudy.azureus2.ui.swt.Main.init(Main.java:147)
at org.gudy.azureus2.ui.swt.Main.main(Main.java:162)
... 6 more
Start fails:
com.aelitis.azureus.core.AzureusCoreException: Azureus core already
instantiated
at
com.aelitis.azureus.core.impl.AzureusCoreImpl.create(AzureusCoreImpl.java:89)
at
com.aelitis.azureus.core.AzureusCoreFactory.create(AzureusCoreFactory.java:46)
at org.gudy.azureus2.ui.common.Main.main(Main.java:137)

I manage to fix it by recompiling swt-gtk source package
(java-gcj-compat javac) after setting env variable by
export SWT_PTR_CFLAGS=-DSWT_PTR_SIZE_64; dpkg-buildpackage ...
and installing result packages:
libswt-gtk-3.2-java_3.2.1-3_amd64.deb
libswt-gtk-3.2-jni_3.2.1-3_amd64.deb

Don't know if it's proper fix or it broke other packages.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)

Versions of packages azureus depends on:
ii  gij [java-virtual-machine]  4:4.1.1-13   The GNU Java bytecode interpreter
ii  gij-4.1 [java2-runtime] 4.1.1-17 The GNU Java bytecode interpreter
ii  java-gcj-compat 1.0.65-8 Java runtime environment using GIJ
ii  libcommons-cli-java 1.0-8API for working with the command l
ii  liblog4j1.2-java1.2.13-3 Logging library for java
ii  libseda-java3.0-3the Staged Event-Driven Architectu
ii  libswt-gtk-3.2-java 3.2.1-3  Standard Widget Toolkit for GTK Ja
ii  sun-java5-jre [java2-runtim 1.5.0-08-1.1 Sun Java(TM) Runtime Environment (

azureus recommends no packages.

-- no debconf information




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]