Subject: gitosis: expects ssh key comment to be in u...@host format
Package: gitosis
Version: 0.2+20080825-2
Severity: normal
*** Please type your report below this line ***
According to ssh.py, gitosis-init expects the "comment" field in the ssh key to
be in the "u...@host" format, as it is the
Package: openssh-client
Version: 1:4.6p1-5
Severity: wishlist
I'm currently concerned with possible attacks when forwarding the agent
to shared hosts. I believe that having ssh-agent logging key uses would
be a step to at least identifying misbehaving root users along the way.
Notifications via l
Package: apache-ssl
Version: 1.3.33-6sarge3
Followup-For: Bug #306101
I was faced his morning with the same problem, it looks the same as
Ian's, this is from error.log
gcache: gcache.c:152: HandleClient: Assertion `n == 1' failed.
[Fri Feb 2 05:31:58 2007] [notice] child pid 28386 exit signal A
Thank you very much for your reply.
I nearly forgot about the bug, so I ran a few tests today, using package
version 3.5.5a.dfsg.1-5 of kicker.
The behaviour has improved since my bug report:
- on "normal" i have on row of icons in the systray and on "large" two,
regardless of the order in whi
Package: cupsys
Version: 1.2.7-2
Followup-For: Bug #383091
I confirm too the presence of this bug on 2 systems (an etch and a sid,
updated this morning). The Cups server sees it when it's not configured,
however when I try printing, it says "Printer not connected, will retry
in 30 seconds".
I ha
Package: splashy
Version: 0.2.1
Followup-For: Bug #400598
RUNLEVEL is set by init(8) for all its children, but when init scripts
are run interactively, the variable isn't there anymore.
An alternative solution for finding the current runlevel might be the
use of runlevel(8), which outputs the eq
On Tue, 28 Nov 2006, Tim Dijkstra wrote:
> Op Mon, 27 Nov 2006 10:42:25 +0200
> schreef Ratiu Petru <[EMAIL PROTECTED]>:
>
> > Package: uswsusp
> > Version: 0.3~cvs20060928-3
> > Severity: normal
> >
> >
> > At first, i thought it's
Package: uswsusp
Version: 0.3~cvs20060928-3
Severity: normal
At first, i thought it's the same as #397667 , however I'm using a
"straight" Debian installation and i have both initscripts (2.86.ds1-35)
and mount (2.12r-15) packages, that's why I'm filing a separate bug.
During configure, I get th
Package: gresolver
Version: 0.0.5-1
Severity: important
On my system, gresolver dies with:
Can't locate Gtk2/GladeXML.pm in @INC (@INC contains: /etc/perl
/usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5
/usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8
/usr/local/lib/sit
; $DAEMON start
;;
--
And I believe "action" probably comes from:
--
# Source function library.
if
[ -f /etc/rc.d/init.d/functions ]
then
. /etc/rc.d/init.d/functions
fi
--
IANADD, but I believe this is a release-critical bug (although pretty
trivial to fix)
Package: apt-listbugs
Version: 0.0.54
Severity: important
For example, when running 'apt-listbugs list psi':
-- start --
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... 0% ... E: undefined local variable or method
`pkg' for Factory::BugsFactory:Mod
Package: kopete
Version: 4:3.5.4-2
Severity: normal
I noticed this when connecting via jabber with SSL both on jabber.org
and my private server which both happen to have CACert-signed
certificates. At login time kopete announces that the CA is
invalid (without offering details, but that's a separ
Package: kicker
Version: 4:3.5.4-2
Severity: minor
When kicker starts (on normal size), there is only one row of icons in
the systray. However, if I set the panel size on "large" to force
two-row systray, and then back on "normal", the icons remain on two
rows.
This state proves unstable, howeve
Package: harden-doc
Version: 3.5
Severity: normal
Although correct when viewed strictly from the security point of view,
default policy of DROP on the INPUT chain is very dangerous when
flushing the chain remotely, as I once found out myself, as a newbie :(
My suggestion would be:
a) either to a
Package: dosage
Version: 1.5.7-2
Severity: minor
Recently, the team at userfriendly.org started to blackhole IP addresses
that use intensive screen-scraping methods.
At least -cc might get someone banned, so I suggest that either the
UserFriendly module is removed altogether, or at least forced
I also experience the same problem.
Aparently /etc/vim/vimrc is not read when vim is invoked.
I copied it in ~/.vimrc and all seems to work normally, at least now
debian.vim and /etc/vim/vimrc.local are loaded.
--
Ratiu Petru <[EMAIL PROTECTED]>
System Administrator
System & Network
16 matches
Mail list logo
