On Do, 15 Mai 2008, Steinar H. Gunderson wrote:
No. Any key who had a single DSA signature created by the flawed version of
OpenSSL should be considered compromised. DSA requires a secret, random
Does this extend to gpg keys and its signatures? That would make quite
an impact.
Best wishes
On Thu, 2008-05-15 at 08:09 +0200, Norbert Preining wrote:
On Do, 15 Mai 2008, Steinar H. Gunderson wrote:
No. Any key who had a single DSA signature created by the flawed version of
OpenSSL should be considered compromised. DSA requires a secret, random
Does this extend to gpg keys and
On Thu, May 15, 2008 at 05:11:27AM +0200, Goswin von Brederlow wrote:
The DSA signing uses (secret key + random) in the signature and that
sum is trivial to compute given the signed message and public key. The
security of DSA relies solely on the fact that random can't be guessed
so you can't
On Thu, 15 May 2008 08:09:02 +0200
Norbert Preining [EMAIL PROTECTED] wrote:
On Do, 15 Mai 2008, Steinar H. Gunderson wrote:
No. Any key who had a single DSA signature created by the flawed version of
OpenSSL should be considered compromised. DSA requires a secret, random
Does this extend
On Thursday 15 May 2008 11:24, Olivier Berger wrote:
I guess openssh-blacklist is only available on stable/updates and not in
testing/updates ... any reason why not ?
It is currently available in unstable; I have no doubt that the release
managers will push it into testing as soon as possible.
Hello,
I just reassigned a bug to acpid and discovered how badly maintained it
is. Despite a new maintainer in january this year, the BTS still shows
many RC bugs and a bunch with patches.
Hopefully this mail will draw some attention to the problem and some
volunteers will step up to help
Hi.
I guess openssh-blacklist is only available on stable/updates and not in
testing/updates ... any reason why not ?
Thanks in advance.
--
Olivier BERGER [EMAIL PROTECTED] (*NEW ADDRESS*)
http://www-inf.it-sudparis.eu/~olberger/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Hi,
Considering recent issues, http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.
Discussion as below. Do I need to make rt thingy? I am not yet
familiar with it.
On Wed, May 14, 2008 at 07:50:29PM +0200, Luk Claes wrote:
Osamu Aoki wrote:
Hi,
Recent
Steinar H. Gunderson [EMAIL PROTECTED]:
On Thu, May 15, 2008 at 05:11:27AM +0200, Goswin von Brederlow wrote:
Also if you have 2 messages signed with the same random number you can
compute the secret key. It is more complicated then this but
simplified boils down to is computing k given
On Thursday 15 May 2008 14:04, Martin Uecker wrote:
If I understand this correctly, this means that not only should keys
generated with the broken ssl lib be considered compromised, but all
keys which were potentially used to create DSA signatures by those
broken libs.
In this case, the
On Thu, 15 May 2008, Osamu Aoki wrote:
Considering recent issues, http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.
My mail to d-i-a said that you need to use RSA keys. You have read
that, right?
The page on db.d.o will get updated eventually, for now think of
On Wed, May 14, 2008 at 08:13:53PM -0400, Filipus Klutiero wrote:
Your second parenthesis is wrong. Just like LKM-s when the stock kernels'
ABINAME is bumped, applications need to be rebuilt when the ABI of one of the
libraries they link to changes in a way which is not backwards-compatible.
Dear all,
it is almost one year that sbackup was modified to use a group ID that
exists on Ubuntu but not on Debian systems. As suggested on
[EMAIL PROTECTED], I have increased the severity of the bug to
'serious' three weeks ago. (#427697)
sbackup is a native Debian package whose maintainer is
On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader wrote:
On Thu, 15 May 2008, Osamu Aoki wrote:
Considering recent issues, http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.
My mail to d-i-a said that you need to use RSA keys. You have read
that,
* Michal Čihař:
GnuPG does not use OpenSSL, so it should be safe. But generally it
could be possible to use same key for both GnuPG and OpenSSL and then
you would have a problem.
There is no benefit from doing that, so this is highly unlikely. It
requires manual key conversion, too.
--
To
Hi Brian,
On Thu, May 15, 2008 at 03:33:41PM +1000, Brian May wrote:
Apparently, Heimdal in Debian also is affected. I am not aware of any
solution other then to manually regenerate all keys.
Could you give some details here? Password based principals aren't
affected? For those using a keytabs
Martin Uecker [EMAIL PROTECTED] writes:
In this case, the security advisory should clearly be updated. And all
advise about searching for weak keys should be removed as well, because
it leads to false sense of security. In fact, *all* keys used on Debian
machines should be considered
Guido Günther [EMAIL PROTECTED] writes:
On Thu, May 15, 2008 at 03:33:41PM +1000, Brian May wrote:
Apparently, Heimdal in Debian also is affected. I am not aware of any
solution other then to manually regenerate all keys.
Could you give some details here? Password based principals aren't
On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader [EMAIL PROTECTED]
wrote:
On Thu, 15 May 2008, Osamu Aoki wrote:
Considering recent issues, http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.
My mail to d-i-a said that you need to use RSA keys.
Am Donnerstag, den 15.05.2008, 15:20 +0200 schrieb Thijs Kinkhorst:
On Thursday 15 May 2008 14:04, Martin Uecker wrote:
If I understand this correctly, this means that not only should keys
generated with the broken ssl lib be considered compromised, but all
keys which were potentially used
On Thu, 15 May 2008, Mike Hommey wrote:
On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader [EMAIL PROTECTED]
wrote:
On Thu, 15 May 2008, Osamu Aoki wrote:
Considering recent issues, http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.
My mail
On Thu, May 15, 2008 at 05:11:30PM +0200, Peter Palfrader [EMAIL PROTECTED]
wrote:
On Thu, 15 May 2008, Mike Hommey wrote:
On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader [EMAIL
PROTECTED] wrote:
On Thu, 15 May 2008, Osamu Aoki wrote:
Considering recent issues,
On Do, 15 Mai 2008, Mike Hommey wrote:
I beg to differ. This particular mail is important enough to be sent to
d-d-a instead of d-i-a.
I agree, dia is not what I would be subscribed to under normal
circumstances, and with all the caos that type of announce is for dda.
Best wishes
Norbert
On Thursday 15 May 2008 16:47, Martin Uecker wrote:
You mean less likely than once in 15 years? We're open to your
suggestions.
Something as bad as this might be rare, still, if something can be
improved, it should.
Upstream complained about the extensive Debian patching. I think this
is
On Thu May 15 2008 06:20:10 Thijs Kinkhorst wrote:
You mean less likely than once in 15 years? We're open to your suggestions.
Leaving millions of systems open to crackers for 2 years out of 15
is not a joke. I don't blame the DD - we have all made mistakes
and most of us are lucky they weren't
On Thu May 15 2008 08:33:54 Thijs Kinkhorst wrote:
I welcome change and review of our processes, but taking one extreme
incident as the base on which to draw conclusions seems not the wise thing
to do. If you're interested in for example changing the level to which
software is patched in
Am Donnerstag, den 15.05.2008, 17:33 +0200 schrieb Thijs Kinkhorst:
On Thursday 15 May 2008 16:47, Martin Uecker wrote:
You mean less likely than once in 15 years? We're open to your
suggestions.
Something as bad as this might be rare, still, if something can be
improved, it should.
On Thursday 15 May 2008 18:26, Martin Uecker wrote:
Why not? A plane crash is a very rare incident. Still every single
crash is investigated to make recommendations for their future
avoidance.
Maybe that wasn't clear from my first mail, but I don't think that nothing can
be learned from this
Martin Uecker wrote:
Am Donnerstag, den 15.05.2008, 17:33 +0200 schrieb Thijs Kinkhorst:
If you're interested in for example changing the level to which software is
patched in Debian, I suggest to start with a representative review of what
gets patched and why it's done. That would give
Twas brillig at 10:30:44 15.05.2008 UTC-07 when Kevin B. McCarty did gyre and
gimble:
KBM Believe me, there are lots of upstreams for which extensive
KBM patching really is necessary. (I have no idea whether OpenSSL is
KBM one of those, as I have no familiarity with its code nor the
KBM
[Mike Bird]
but we should blame the process. And fix it.
it would probably have been better to devote less effort to the
scanner and more effort to documenting all the kinds of key
replacements
Serious efforts are needed
Second, we must ensure
This calls for a thorough investigation
Mikhail Gusarov [EMAIL PROTECTED] writes:
Probably the work then should be clearly labeled as fork (especially
given the other distro maintainers also share some patches)? It will
reduce the confusion, like oh, erm, our foo is not quite upstream
foo, we rewrote it from scratch, and left the
On Thu May 15 2008 10:34:01 Peter Samuelson wrote:
Who is this we? Whose serious efforts? Who is investigating? Most
importantly, should we assume that, as in the past, you, Mike Bird,
intend to do nothing but talk?
Debian is still one of the world's best distros and I hope it
continues as
[Mike Bird]
Nevertheless, non-DD's can and do help by filing bug reports and
patches (upstream is best), helping people on d-u, and offering
constructive advice to DDs.
Very well. I propose that anyone who wishes to give constructive
advice to developers, but who doesn't actually do any of
Hi,
Le 15 mai 08 à 20:17, Mike Bird a écrit :
Nevertheless, non-DD's can and do help by filing bug reports and
patches (upstream is best), helping people on d-u, and offering
constructive advice to DDs.
And maintaining packages! It can be long to find a sponsor for your
first package
Hi Mikhail,
Mikhail Gusarov wrote:
Twas brillig at 10:30:44 15.05.2008 UTC-07 when Kevin B. McCarty did gyre and
gimble:
KBM Believe me, there are lots of upstreams for which extensive
KBM patching really is necessary. (I have no idea whether OpenSSL is
KBM one of those, as I have no
On Thu, 15 May 2008, Norbert Preining wrote:
On Do, 15 Mai 2008, Mike Hommey wrote:
I beg to differ. This particular mail is important enough to be sent to
d-d-a instead of d-i-a.
I agree, dia is not what I would be subscribed to under normal
circumstances, and with all the caos that
Hi!
Noticing among others this bug report
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322751 and observing the
many packages depending on $MTA | mail-transport-agent with $MTA having
values like postfix, exim, exim4, sendmail, nullmailer and probably others.
And some packages just
On Thu May 15 2008 14:33:04 Sune Vuorela wrote:
The latter, just depending on mail-transport-agent, makes apt, at least
currently, pick the package first in the alphabet providing m-t-a. (A bit
ago, this was courier. now it is citadel). This definately needs fixing,
but why not sort everything
Le May 15, 2008 09:55:40 am Lennart Sorensen, vous avez écrit :
On Wed, May 14, 2008 at 08:13:53PM -0400, Filipus Klutiero wrote:
Your second parenthesis is wrong. Just like LKM-s when the stock kernels'
ABINAME is bumped, applications need to be rebuilt when the ABI of one of
the libraries
2008/5/15 Charles Plessy [EMAIL PROTECTED]:
Despite the fact that the maintainer of sbackup is actively blogging on
planet.d.o, I wonder if sbackup is maintained. From a user perspective
(and I am a user of sbackup, that is why I feel concerned), I think that
if there is no future for sbackup,
2) Introduce a default-mta package (currently) depending on exim4. All
packages requiring a MTA should depend on default-mta | mail-transport-agent.
This will have the extra advantage that we (and others like CDDs and derived
distros) easily could swap default MTA.
What concerns me about this
peter green [EMAIL PROTECTED] writes:
It seems to me that the ideal soloution would be to fix apt/the
repositry system so that the defaults for a virtual package can be
explicitly designed.
I have no idea how to do this and no time to help, but I think this would
be really cool and would
On Thu, May 15, 2008 at 11:39:36PM +0100, peter green wrote:
2) Introduce a default-mta package (currently) depending on exim4. All
packages requiring a MTA should depend on default-mta |
mail-transport-agent. This will have the extra advantage that we (and
others like CDDs and derived
Mike Bird [EMAIL PROTECTED] writes:
All of the MTA's provide mail-transport-agent. I had assumed that apt
would choose between them on the basis that exim4-daemon-light is the
only provider with priority standard, the others being optional or extra.
If apt does not consider package
On Thu, May 15, 2008 at 11:33:04PM +0200, Sune Vuorela wrote:
Noticing among others this bug report
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322751 and observing the
many packages depending on $MTA | mail-transport-agent with $MTA having
values like postfix, exim, exim4, sendmail,
15 травня 2008 о 16:24 -0700 Steve Langasek написав(-ла):
What concerns me about this approach is that it could easilly end up with
dist-upgrades swapping out users mail systems without warning. I would
consider such behaviour unacceptable as it could easilly cause mail loss
Er, no,
Le Fri, May 16, 2008 at 01:22:12AM +0300, Aigars Mahinovs a écrit :
The upstream situation is not as clear cut - I've been making every
effort to a new and enthusiastic developer (Ouattara Oumar Aziz) take
over the upstream development of SBackup peacefully.
I am discussing the future of
On Fri, May 16, 2008 at 02:10:39AM +0200, Eugeniy Meshcheryakov wrote:
15 травня 2008 о 16:24 -0700 Steve Langasek написав(-ла):
What concerns me about this approach is that it could easilly end up with
dist-upgrades swapping out users mail systems without warning. I would
consider
This one time, at band camp, Mike Bird said:
Yet Debian makes it hard for people to help. Like most software
engineers I simply don't have the time to waste on Debian's NM
process. Debian's processes are indisputably Debian's decision
alone, but Debian has to live with the consequences ...
Steve Langasek [EMAIL PROTECTED] writes:
On Thu, May 15, 2008 at 11:33:04PM +0200, Sune Vuorela wrote:
2) Introduce a default-mta package (currently) depending on exim4.
All packages requiring a MTA should depend on default-mta |
mail-transport-agent. This will have the extra advantage
On Fri, May 16, 2008 at 10:53:03AM +1000, Ben Finney wrote:
Steve Langasek [EMAIL PROTECTED] writes:
On Thu, May 15, 2008 at 11:33:04PM +0200, Sune Vuorela wrote:
2) Introduce a default-mta package (currently) depending on exim4.
All packages requiring a MTA should depend on default-mta
Steve Langasek [EMAIL PROTECTED] writes:
sensible-editor and sensible-browser are /commands/
Provided by the 'debianutils' package.
default-mta is not at all like this.
You're right, I'm wrong. Thanks for clearing my confusion.
--
\ Hey Homer! You're late for English! Pff! English,
Steve Langasek [EMAIL PROTECTED] writes:
On Fri, May 16, 2008 at 02:10:39AM +0200, Eugeniy Meshcheryakov wrote:
15 ÑÑÐ°Ð²Ð½Ñ 2008 о 16:24 -0700 Steve Langasek напиÑав(-ла):
What concerns me about this approach is that it could easilly end up
with
dist-upgrades swapping
On Friday 16 May 2008 10:20, Charles Plessy wrote:
Since the revitalisation of sbackup is expected after the freezing of
Lenny, we have to solve the most important bugs of the current version
of sbackup. I do not know enough of python for helping on bug #427697
(the gid of the backups). If
I notice that pwsafe is linked against openssl. Is it affected by the
recent debacle and if so, how? Do I need to regenerate all my
randomized passwords, or somehow re-encrypt the pwsafe database?
Thanks,
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Peter Samuelson [EMAIL PROTECTED] writes:
Who is this we? Whose serious efforts? Who is investigating? Most
importantly, should we assume that, as in the past, you, Mike Bird,
intend to do nothing but talk?
I think this is a common stylistic choice. I consider myself part of
the Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 08:10:08 +0200
Source: xfce4-quicklauncher-plugin
Binary: xfce4-quicklauncher-plugin
Architecture: source amd64
Version: 1.9.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Xfce Maintainers [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 08:48:41 +0200
Source: xfce4-panel
Binary: xfce4-panel xfce4-panel-dev xfce4-panel-dbg
Architecture: source amd64
Version: 4.4.2-5
Distribution: unstable
Urgency: low
Maintainer: Debian Xfce Maintainers [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 8 May 2008 10:17:20 +0100
Source: bum
Binary: bum
Architecture: source all
Version: 2.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Fabio Marzocca [EMAIL PROTECTED]
Changed-By: Fabio Marzocca [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 14 May 2008 21:20:39 +0200
Source: kdebase-runtime
Binary: kdebase-runtime kdebase-runtime-bin-kde4 kdebase-runtime-data
kdebase-runtime-data-common kde-icons-oxygen kdebase-runtime-dbg
Architecture: source all amd64
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 8 May 2008 11:40:47 +0100
Source: gtkorphan
Binary: gtkorphan
Architecture: source all
Version: 0.4.4-1
Distribution: unstable
Urgency: low
Maintainer: Fabio Marzocca [EMAIL PROTECTED]
Changed-By: Fabio Marzocca [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 09:53:02 +0200
Source: gst-plugins-ugly0.10
Binary: gstreamer0.10-plugins-ugly-doc gstreamer0.10-plugins-ugly
gstreamer0.10-plugins-ugly-dbg
Architecture: source all i386
Version: 0.10.7.3-1
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 10:39:48 +0100
Source: proguard
Binary: proguard
Architecture: source all
Version: 4.2-1
Distribution: unstable
Urgency: low
Maintainer: Sam Clegg [EMAIL PROTECTED]
Changed-By: Sam Clegg [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 12:43:43 +0200
Source: octave-statistics
Binary: octave-statistics
Architecture: source all
Version: 1.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 12:33:51 +0200
Source: octave-struct
Binary: octave-struct
Architecture: source all
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 09:36:48 +0800
Source: keynav
Binary: keynav
Architecture: source i386
Version: 0.20080509-1
Distribution: unstable
Urgency: low
Maintainer: Wen-Yen Chuang [EMAIL PROTECTED]
Changed-By: Wen-Yen Chuang [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 12:13:58 +0200
Source: libclass-meta-perl
Binary: libclass-meta-perl
Architecture: source all
Version: 0.61-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Krzysztof
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 12:38:29 +0200
Source: octave-strings
Binary: octave-strings
Architecture: source i386
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 13 May 2008 16:59:18 +0100
Source: gramadoir
Binary: gramadoir liblingua-ga-gramadoir-perl
Architecture: source all
Version: 0.6-3
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry [EMAIL PROTECTED]
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 20:51:33 +1000
Source: asterisk-sounds-extra
Binary: asterisk-sounds-extra
Architecture: source all
Version: 1.4.7-1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team [EMAIL PROTECTED]
Changed-By: Mark
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 13:05:29 +0200
Source: octave-specfun
Binary: octave-specfun
Architecture: source i386
Version: 1.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 13 May 2008 10:54:16 +0200
Source: italc
Binary: italc-master italc-client libitalc
Architecture: source i386
Version: 1:1.0.8-1
Distribution: unstable
Urgency: low
Maintainer: Patrick Winnertz [EMAIL PROTECTED]
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 12:47:15 +0200
Source: octave-splines
Binary: octave-splines
Architecture: source all
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 24 Apr 2008 12:39:41 +0200
Source: libcatalyst-modules-perl
Binary: libcatalyst-modules-perl
Architecture: source all
Version: 29
Distribution: unstable
Urgency: low
Maintainer: Debian Catalyst Maintainers [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 13:28:47 +0200
Source: octave-sockets
Binary: octave-sockets
Architecture: source i386
Version: 1.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 06:21:07 -0500
Source: audacious-plugins
Binary: audacious-plugins audacious-plugins-extra audacious-plugins-dev
Architecture: source i386
Version: 1.5.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 15:09:43 +0300
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.09-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 8 May 2008 02:03:34 +0300
Source: zaptel
Binary: zaptel libtonezone1 libtonezone-dev zaptel-source
Architecture: source all powerpc
Version: 1:1.4.10.1~dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 14:47:23 +0200
Source: octave-odebvp
Binary: octave-odebvp
Architecture: source all
Version: 1.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 14:28:40 +0200
Source: octave-signal
Binary: octave-signal
Architecture: source i386
Version: 1.0.7-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 15:24:10 +0200
Source: octave-sockets
Binary: octave-sockets
Architecture: source i386
Version: 1.0.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 18 Feb 2008 16:46:22 +
Source: asterisk-prompt-es
Binary: asterisk-prompt-es
Architecture: source all
Version: 1.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team [EMAIL PROTECTED]
Changed-By: Victor Seva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 14 May 2008 22:44:06 +0200
Source: directfb
Binary: libdirectfb-1.0-0 libdirectfb-1.0-0-udeb libdirectfb-bin
libdirectfb-bin-udeb libdirectfb-extra libdirectfb-dev
Architecture: source amd64
Version: 1.0.1-9
Distribution:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 14:36:42 +0200
Source: aufs
Binary: aufs-tools aufs-source linux-patch-aufs
Architecture: source all amd64
Version: 0+20080514-2
Distribution: unstable
Urgency: low
Maintainer: Julian Andres Klode [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 14 May 2008 22:44:23 -0700
Source: dhcp3
Binary: dhcp3-server dhcp3-server-ldap dhcp3-common dhcp3-dev dhcp3-client
dhcp3-client-udeb dhcp3-relay
Architecture: source i386
Version: 3.1.1-1
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 23:33:24 +0900
Source: dvi2ps
Binary: dvi2ps
Architecture: source i386
Version: 4.1j-1
Distribution: unstable
Urgency: low
Maintainer: OHURA Makoto [EMAIL PROTECTED]
Changed-By: OHURA Makoto [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 22:51:32 +0930
Source: vpb-driver
Binary: vpb-driver-source vpb-utils libvpb0 libvpb-dev libvpb-doc
Architecture: source all amd64
Version: 4.2.32-1
Distribution: unstable
Urgency: low
Maintainer: Ron Lee [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 15 May 2008 17:10:37 +0200
Source: fai
Binary: fai-client fai-server fai-doc fai-quickstart fai-nfsroot
Architecture: source all
Version: 3.2.6
Distribution: unstable
Urgency: medium
Maintainer: Thomas Lange [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 17:05:16 +0200
Source: libdc1394-22
Binary: libdc1394-22-dev libdc1394-22 libdc1394-22-dbg libdc1394-22-doc
libdc1394-utils
Architecture: source all amd64
Version: 2.0.2-1
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 08 May 2008 08:32:20 +0200
Source: freecol
Binary: freecol
Architecture: source all
Version: 0.7.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team [EMAIL PROTECTED]
Changed-By: Vincent Fourmond [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 17:00:29 +0900
Source: debiandoc-sgml
Binary: debiandoc-sgml
Architecture: source all
Version: 1.2.9
Distribution: unstable
Urgency: low
Maintainer: DebianDoc-SGML Pkgs [EMAIL PROTECTED]
Changed-By: Osamu Aoki [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 15:28:29 +0200
Source: pygtk
Binary: python-gtk2 python-gtk2-dev python-glade2 python-gtk2-doc
Architecture: source all i386
Version: 2.12.1-2
Distribution: unstable
Urgency: low
Maintainer: Sebastien Bacher [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 18:54:37 +0200
Source: sane-backends
Binary: sane-utils libsane libsane-dev libsane-dbg
Architecture: source amd64
Version: 1.0.19-9
Distribution: unstable
Urgency: low
Maintainer: Julien BLACHE [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 14 May 2008 17:03:45 -0700
Source: ale
Binary: ale
Architecture: source i386
Version: 0.7.1-2
Distribution: unstable
Urgency: low
Maintainer: QA Group [EMAIL PROTECTED]
Changed-By: Nick Rusnov [EMAIL PROTECTED]
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 19:09:50 +0200
Source: sane-backends-extras
Binary: libsane-extras libsane-extras-dev libsane-extras-dbg
Architecture: source amd64
Version: 1.0.19.7
Distribution: unstable
Urgency: low
Maintainer: Julien BLACHE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 19:01:21 +0200
Source: sqlalchemy
Binary: python-sqlalchemy python-sqlalchemy-doc
Architecture: source all
Version: 0.4.6-1
Distribution: unstable
Urgency: low
Maintainer: Piotr Ożarowski [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 17:40:23 +0200
Source: bzr-dbus
Binary: bzr-dbus
Architecture: source all
Version: 0.1~bzr35-4
Distribution: unstable
Urgency: low
Maintainer: Debian Bazaar Maintainers [EMAIL PROTECTED]
Changed-By: Jelmer Vernooij
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 15 May 2008 20:55:20 +0200
Source: tightvnc
Binary: tightvncserver xtightvncviewer
Architecture: source i386
Version: 1.3.9-2
Distribution: unstable
Urgency: low
Maintainer: Ola Lundqvist [EMAIL PROTECTED]
Changed-By: Ola
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 15 May 2008 21:11:18 +0200
Source: debian-edu-doc
Binary: debian-edu-doc
Architecture: source all
Version: 1.0~20080515
Distribution: unstable
Urgency: low
Maintainer: Debian Edu Developers [EMAIL PROTECTED]
Changed-By: Holger
1 - 100 of 112 matches
Mail list logo
