Bug#932456: Is there any progress on this bug

2021-01-01 Thread Rajko Albrecht
I have the same problems since upgraded to 10.x - and it is frustrating that I 
cannot do automated VM backups because I don't want to (temporary) shutdown AA 
in a script. So I start the backup script by hand every time.

Is this due a change by maintainer or is this an upstream bug (with fedora and 
selinux I don't see such problems). I'm asking because nothing happens on this 
bug but I think this is urgent for one using debian as KVM host.

R


Bug#840566: bash: Bash as root login shell ends with xmalloc error

2016-10-12 Thread Rajko Albrecht
Package: bash
Version: 4.4-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Tried to login on server or "su -" but got only 

-su: xmalloc: cannot allocate 80008 bytes (1626112 bytes allocated)

so login isn't possible as root anymore. When running just "su" eg. bash not as 
login shell it first works. 


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

1. Flushed .bash_history of user root - login works. But now no execution of 
any command is possible, ends with the xmalloc error.
2. run bash not as login-shell. Now all is working. 
3. tried as normal user. There is no problem.


   * What was the outcome of this action?

Root user may just use other shell like dash as login shell

   * What outcome did you expect instead?

Expect that root-user may use bash as login-shell


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bash depends on:
ii  base-files   9.6
ii  dash 0.5.8-2.3
ii  debianutils  4.8
ii  libc62.24-3
ii  libtinfo56.0+20160917-1

Versions of packages bash recommends:
ii  bash-completion  1:2.1-4.3

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information



Bug#767195: live-boot: Encrypted persistence not possible at boot time

2014-10-30 Thread Rajko Albrecht
Ok,

Yes, then this is a bug in live-build not boot.

I tried a lot since yesterday getting this parameter into initram build
but no chance until now. No ideas anymore meanwhile (without patching
the live builds itself)


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



Bug#767195: Encrypted persistence not possible at boot time

2014-10-30 Thread Rajko Albrecht
Ok, I tried a lot, but with current live-build without patching
live-update-initramfs it is not possible getting a live system which
supports encrypted partitions at boot time for persistence.

So it must get fixed in live build tools, eg in live-update-initramfs.

Or cryptsetup changes the default - disabling security as default is a
somewhat strange idea.

I'd replaced the call to original update-initramfs with this line

CRYPTSETUP=y /usr/sbin/update-initramfs.orig.initramfs-tools ${@}


(line 89 only)

Yes, of course, it must be configure-able.


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



Bug#767195: live-boot: Encrypted persistence not possible at boot time

2014-10-29 Thread Rajko Albrecht
Package: live-boot
Version: 4.0.1-1
Severity: important
Tags: d-i

Dear Maintainer,

I tried a while getting a live system working with encrypted persistence on
boot time. When doing

live-persistence activate /dev/sdx2

it ask for password and setup the encryption, thats ok. But boot time
persistence works only for unencrypted storage.

Snippet from boot.log of live-boot:

+ LIVE_BOOT_CMDLINE=BOOT_IMAGE=/live/vmlinuz boot=live noeject keyboard-
layouts=de components persistence persistence-encryption=luks,none
initrd=/live/initrd.img debug=true
+ Cmdline_old
+ PERSISTENCE=true
+ export PERSISTENCE
+ PERSISTENCE_ENCRYPTION=luks,none
+ export PERSISTENCE_ENCRYPTION
+ [ -z  ]
+ [  = /dev/nfs ]
+ [  = /dev/cifs ]
+ [ -z  ]
+ MODULE=filesystem
+ export MODULE
+ [ -z  ]
+ UNIONTYPE=aufs
+ export UNIONTYPE
+ [ -z luks,none ]
+ is_in_comma_sep_list luks luks,none
+ local element
+ element=luks
+ shift
+ is_in_list_separator_helper , luks luks,none
+ local sep element list
+ sep=,
+ shift
+ element=luks
+ shift
+ list=luks,none
+ echo luks,none
+ grep -qe ^\(.*,\)\?luks\(,.*\)\?$
+ modprobe dm-crypt
+ [ ! -x /lib/cryptsetup/askpass ]
+ log_warning_msg cryptsetup is unavailable
+ _log_msg Warning: cryptsetup is unavailable\n
+ [ n = y ]
+ printf Warning: cryptsetup is unavailable\n
Warning: cryptsetup is unavailable


As you can see, /lib/cryptsetup/askpass isn't executable (but installed via
package list as described in your documentation)


The configuration last used is

lb config noauto\
--apt apt\
--bootstrap debootstrap\
--binary-images iso-hybrid \
--distribution testing\
--mirror-bootstrap http://ftp.debian.de/debian/ \
--mirror-binary http://ftp.debian.de/debian/ \
--memtest memtest86+ \
--mode debian\
--linux-packages linux-image linux-headers \
--system live\
--debian-installer false\
--bootappend-live boot=live noeject keyboard-layouts=de components
persistence persistence-encryption=luks,none\
--archive-areas main contrib non-free\
--apt-options --force-yes --yes\
--debconf-frontend dialog\
--firmware-binary true\
--firmware-chroot true\
${@}

and tried it with --binary-images hdd and a lot of other options, but nothing
works. Could not execute askpass at boot time. No idea, whats going wrong here.

It should work without any hard research, encrypted live systems are essential
for sysadmins (and others). I don't know if it would work with wheezy 'cause I
didn't try it (I require the newer kernel in jessie).



-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages live-boot depends on:
ii  live-boot-initramfs-tools [live-boot-backend]  4.0.1-1

Versions of packages live-boot recommends:
ii  live-boot-doc  4.0.1-1
ii  live-tools 4.0.1-1
ii  rsync  3.1.1-2
ii  uuid-runtime   2.25.1-5

Versions of packages live-boot suggests:
ii  cryptsetup2:1.6.6-2
pn  curlftpfs none
pn  httpfs2   none
pn  unionfs-fuse  none
ii  wget  1.15-1+b1
+ tailpid=123
+ tail -f boot.log
+ cat /proc/cmdline
+ LIVE_BOOT_CMDLINE=BOOT_IMAGE=/live/vmlinuz boot=live noeject 
keyboard-layouts=de components persistence persistence-encryption=luks,none 
initrd=/live/initrd.img debug=true
+ Cmdline_old
+ PERSISTENCE=true
+ export PERSISTENCE
+ PERSISTENCE_ENCRYPTION=luks,none
+ export PERSISTENCE_ENCRYPTION
+ [ -z  ]
+ [  = /dev/nfs ]
+ [  = /dev/cifs ]
+ [ -z  ]
+ MODULE=filesystem
+ export MODULE
+ [ -z  ]
+ UNIONTYPE=aufs
+ export UNIONTYPE
+ [ -z luks,none ]
+ is_in_comma_sep_list luks luks,none
+ local element
+ element=luks
+ shift
+ is_in_list_separator_helper , luks luks,none
+ local sep element list
+ sep=,
+ shift
+ element=luks
+ shift
+ list=luks,none
+ echo luks,none
+ grep -qe ^\(.*,\)\?luks\(,.*\)\?$
+ modprobe dm-crypt
+ [ ! -x /lib/cryptsetup/askpass ]
+ log_warning_msg cryptsetup is unavailable
+ _log_msg Warning: cryptsetup is unavailable\n
+ [ n = y ]
+ printf Warning: cryptsetup is unavailable\n
Warning: cryptsetup is unavailable
+ echo luks,none
+ sed -e s/\luks,\|,\?luks$//g
+ PERSISTENCE_ENCRYPTION=none
+ export PERSISTENCE_ENCRYPTION
+ [ -z  ]
+ PERSISTENCE_METHOD=overlay
+ export PERSISTENCE_METHOD
+ [ -z  ]
+ PERSISTENCE_STORAGE=filesystem,file
+ export PERSISTENCE_STORAGE
+ Debug
+ return 0
+ Read_only
+ return 0
+ Select_eth_device
+ egrep ^BOOT= /conf/initramfs.conf
+ tail -1
+ bootconf=
+ [  != BOOT=nfs ]
+ [ -z  ]
+ [ -z  ]
+ [ -z  ]
+ [ -z  ]
+ return
+ [ -e /conf/param.conf ]
+ [ ! -z  ]
+ [ ! -z  ]
+ [ ! -z  ]
+ [ ! -z  ]
+ [ -n  ]
+ [ -n  ]
+ [ -x /usr/bin/memdiskfind ]
+ i=0
+ [ 0 -lt 60 ]
+ find_livefs 0
+ timeout=0
+ [ -n  ]
+ [ ! -z  ]
+ removable_dev sys
+ 

Bug#737000: general: Most used german debian mirror (ftp.de.debian.org) has no IPV6

2014-01-29 Thread Rajko Albrecht
Package: general
Severity: normal
Tags: ipv6

Dear Maintainer,

*** Please consider answering these questions, where appropriate ***

I have to maintain serveral virtual maschines which has only IPV6 available due
serveral reasons.

When setting up debian testing it cost a lot of time to find a debian mirror
which supports IPV6 connections 'cause the first selection is ipv4 only.

I think, it should changed as soon as possible - or mark ipv6 enabled mirrors
in mirror selection tool on install please.




-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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



Bug#734004: network-manager-openvpn: NM-Openvpn ignores pushed IPV6 addresses/routes

2014-01-02 Thread Rajko Albrecht
Package: network-manager-openvpn
Version: 0.9.8.4-1
Severity: important
Tags: ipv6

Dear Maintainer,

   * What led up to the situation?
I'd try to connect to an openvpn server which is pushing ipv6 (and ipv4)
addresses to clients. When using openvpn on commandline (openvpn --config
client.conf) the interface got a IPV6 address from server assigned which is
full working. When doing the same from within Network-Manager the ipv4 is
assigned but not the ipv6 address/route

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
  Imported an existing working openvpn client configuration to network
manager openvpn module and created a config from scratch.
   * What was the outcome of this action?
  Working VPN with just an ipv4 address assigned from openvpn server. In
appended log you'll see, that it is real ignoring ipv6.

   * What outcome did you expect instead?
 A working openvpn connection having an IPV4 and an IPV6 address assigned
like running openvpn directly


Log:

Jan  3 00:43:17 NB0890-L dbus[2195]: [system] Successfully activated service
'org.freedesktop.nm_dispatcher'
Jan  3 00:43:22 NB0890-L NetworkManager[2548]: info Starting VPN service
'openvpn'...
Jan  3 00:43:22 NB0890-L NetworkManager[2548]: info VPN service 'openvpn'
started (org.freedesktop.NetworkManager.openvpn), PID 12173
Jan  3 00:43:22 NB0890-L NetworkManager[2548]: info VPN service 'openvpn'
appeared; activating connections
Jan  3 00:43:22 NB0890-L NetworkManager[2548]: info VPN plugin state changed:
starting (3)
Jan  3 00:43:22 NB0890-L NetworkManager[2548]: info VPN connection 'client-
noproxy' (Connect) reply received.
Jan  3 00:43:22 NB0890-L nm-openvpn[12176]: OpenVPN 2.3.2 x86_64-pc-linux-gnu
[SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Nov 28
2013
Jan  3 00:43:22 NB0890-L nm-openvpn[12176]: WARNING: No server certificate
verification method has been enabled.  See http://openvpn.net/howto.html#mitm
for more info.
Jan  3 00:43:22 NB0890-L nm-openvpn[12176]: NOTE: the current --script-security
setting may allow this configuration to call user-defined scripts
Jan  3 00:43:22 NB0890-L nm-openvpn[12176]: UDPv4 link local: [undef]
Jan  3 00:43:22 NB0890-L nm-openvpn[12176]: UDPv4 link remote:
[AF_INET]188.40.43.245:1194
Jan  3 00:43:22 NB0890-L nm-openvpn[12176]: [] Peer Connection
Initiated with [AF_INET]XXX.XXX.XXX.245:1194
Jan  3 00:43:25 NB0890-L nm-openvpn[12176]: TUN/TAP device tun0 opened
Jan  3 00:43:25 NB0890-L nm-openvpn[12176]: /usr/lib/NetworkManager/nm-openvpn-
service-openvpn-helper tun0 1500 1542 10.8.0.4 255.255.255.0 init
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: warn
/sys/devices/virtual/net/tun0: couldn't determine device driver; ignoring...
Jan  3 00:43:25 NB0890-L NetworkManager[2548]:SCPlugin-Ifupdown: devices
added (path: /sys/devices/virtual/net/tun0, iface: tun0)
Jan  3 00:43:25 NB0890-L NetworkManager[2548]:SCPlugin-Ifupdown: device
added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown
configuration found.
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info VPN connection 'client-
noproxy' (IP4 Config Get) reply received from old-style plugin.
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info VPN Gateway:
XXX.XXX.XXX.245
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info Tunnel Device: tun0
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info IPv4 configuration:
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Internal Gateway:
10.8.0.1
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Internal Address:
10.8.0.4
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Internal Prefix: 24
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Internal Point-to-Point
Address: 0.0.0.0
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Maximum Segment Size
(MSS): 0
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Static Route:
172.16.31.0/24   Next Hop: 172.16.31.0
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Static Route:
10.9.0.0/24   Next Hop: 10.9.0.0
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Forbid Default Route:
no
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   Internal DNS:
172.16.31.1
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info   DNS Domain: '(none)'
Jan  3 00:43:25 NB0890-L NetworkManager[2548]: info No IPv6 configuration
Jan  3 00:43:25 NB0890-L nm-openvpn[12176]: Initialization Sequence Completed
Jan  3 00:43:26 NB0890-L NetworkManager[2548]: info VPN connection 'client-
noproxy' (IP Config Get) complete.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-openvpn depends on:
ii  libc6 2.17-97
ii  libdbus-1-3  

Bug#551816: Fixed upstream

2010-01-12 Thread Rajko Albrecht
This is fixed upstream in revision 2014
(http://kdesvn.alwins-world.de/changeset/2014) and comes with 1.5.1,
would nice if someone would store such bugs to the kdesvn tracker in
future :)




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



Bug#546154: Bug is fixed upstream

2010-01-12 Thread Rajko Albrecht
This bug is fixed in recent versions of kdesvn


signature.asc
Description: This is a digitally signed message part.


Bug#480156: Its not a bug of kdesvn

2010-01-12 Thread Rajko Albrecht
This messages is the simple output of the ssh layer subversion uses. Means, 
the question is asked by ssh not by kdesvn. So it can not fixed in kdesvn.


signature.asc
Description: This is a digitally signed message part.


Bug#394097: It doesn't work after upgrade to apache2 2.2.3 anymore

2006-11-06 Thread Rajko Albrecht
Here the same: just upgraded and auth_pam doesn't work anymore. 

If any one has it working, please tell, authn_pam isn't reachable, auth_pam 
doesn't work in debian, switch to another server isn't possible this moment - 
wonderfull.


Only that brainfucked clear error message in logfile:

Internal error: pcfg_openfile() called with NULL filename

Config as worked until:

AuthType Basic
AuthPAM_Enabled on
AuthName Subversion Repositories on 
Require group XXX
Require user 


it asks for username/password and than stops with that internal error bla


Would nice getting some information more if it works on your side, Robbert, 
and would great when this information (even them will work later on) would be 
n a README in package.

tnx


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



Bug#387580: Error with subversion and apache2 on long requests

2006-09-15 Thread Rajko Albrecht
Package: libapache2-svn
Version: 1.3.2-5+b1

When doing long requests like log on a repository served by apache2 and 
subversion module, it end with an error and inside apache2 error log 
following line appears:

[error] [client 127.0.1.1] Provider encountered an error while streaming a 
REPORT response.  [400, #0]


Not sure if it is the same like here:

 http://issues.apache.org/bugzilla/show_bug.cgi?id=34332

but there it seems fixed since more than a year. Next I had a line 

[error] A failure occurred while driving the update report editor [500, 
#190004]

- in subversion faq them tell that the apache/apr has reconfigured with 

ac_cv_func_poll=no; export ac_cv_func_poll

(see http://subversion.tigris.org/faq.html)

Would nice to get a newer version of subversion/apr modules in testing to get 
a working subversion-http-server.

tnx

Rajko


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



Bug#369809: Fixed

2006-07-19 Thread Rajko Albrecht
Hi,

(j4i - me the main author behind kdesvn) 

as in kdesvn-bugtracker described - this bug is now real fixed.

I'll test  it now shortly and I think I'll release ASAP 0.9.1 with that fix 
(and two Michael made).

tnx for exercise patience

Rajko


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