Processing commands for cont...@bugs.debian.org:
> fixed 928944 1.9.7-3+deb9u1
Bug #928944 {Done: Xavier Guimard }
[liblemonldap-ng-portal-perl] CVE-2019-12046: lemonldap-ng tokens allows
anonymous session when stored in session DB
Marked as fixed in versions lemonldap-ng/1.9.7-3+deb9u1.
> thank
على ١٠/٩/١٤٤٠ هـ ٥:١٣ م، كتب Salvatore Bonaccorso:
> Hi Afif,
>
> On Wed, May 15, 2019 at 10:57:49PM +0200, Salvatore Bonaccorso wrote:
>> Then there is nothing further to be done.
>
> Oh, actually there is an open point: Is it confirmed that 3.0.3 is not
> affected by the CVE? Did you got
على ١٠/٩/١٤٤٠ هـ ٤:٥٧ م، كتب Salvatore Bonaccorso:
>>> Could you furthermore check, is this only introduced in the 3.1.0
>>> series really or just are those the versions checked for the issue,
>>> but earlier versions might be affected as well?
>>>
>> I filed an unblock request to hopefully r
Hi Axel,
considering that Evolvotron (the version in subject) was working before, it
seems that the cause of the bug is related to some library like Qt5 or
Boost that has been updated, so the application can't find the correct
calls downside, leading to segmentation fault...
Is there any possibil
Le 15/05/2019 à 16:17, Xavier a écrit :
> Le 15/05/2019 à 16:13, Anthony Prades a écrit :
>> On 5/15/19 4:10 PM, Xavier wrote:
>>> I can't reproduce this exact issue. After the upgrade process (with
>>> actual Buster packages), sieve rules are inoperative, but lmtpd won't
>>> segfault:
>>> * Start
Hi Paul,
The changelog of the latest rsync package available in stretch does say
that these are fixed, but I can still see that stretch is shown as
vulnerable on the security tracker.
https://security-tracker.debian.org/tracker/CVE-2016-9840
If these are fixed, could you please get the security
Processing commands for cont...@bugs.debian.org:
> fixed 929007 intel-microcode/3.20190514.1~
Bug #929007 {Done: Markus Schade } [intel-microcode]
intel-microcode: Update intel-microcode to 20190514
The source intel-microcode and version 3.20190514.1~ do not appear to match any
binary packages
M
Processing commands for cont...@bugs.debian.org:
> found 929007 intel-microcode/0.20080131-1
Bug #929007 {Done: Markus Schade } [intel-microcode]
intel-microcode: Update intel-microcode to 20190514
Marked as found in versions intel-microcode/0.20080131-1.
> thanks
Stopping processing here.
Pleas
Your message dated Thu, 16 May 2019 05:45:51 +0200
with message-id
and subject line system-config-printer-kde has been removed from Debian
has caused the Debian Bug report #756492,
regarding system-config-printer-kde: Authentication Dialog cannot receive focus
to be marked as done.
This means tha
Two more things:
1. I have a few more samples in both categories, if needed
2. I do realize that this bears resemblance to #679581. However, there the
offending process was different.
On 16 May 2019 01:42:44 BST, "Bálint Kovács" wrote:
>Package: tracker-extract
>Version: 2.1.6-1
>Severity: cri
Thibaut Paumard writes:
> I'm checking your patch, which looks good (compiling guile for testing
> takes a lot o time but the patch itself is pretty straightforward and
> clean). Do you intend on NMUing this? Given the age of this RC bug, I
> think you should.
I'm not certain, but I'm planning t
Your message dated Thu, 16 May 2019 01:03:36 +
with message-id
and subject line Bug#928726: fixed in cjson 1.7.10-1.1
has caused the Debian Bug report #928726,
regarding json: CVE-2019-11834 CVE-2019-11835
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Processing commands for cont...@bugs.debian.org:
> retitle 929034 evolvotron: Segfaults most of the time (ca. 80%) at startup
Bug #929034 [evolvotron] evolvotron: Evolvotron can't stat (segmentation fault)
Changed Bug title to 'evolvotron: Segfaults most of the time (ca. 80%) at
startup' from 'ev
Dear Maintainer,
I just tried to have a look and might found something.
As far as I see ldd searches the shared objects based on the RPATH in
the executable:
benutzer@debian:~$ ldd /usr/bin/CloudCompare | grep "not found"
libQCC_IO_LIB.so => not found
libQ
Hi,
thanks for the bug report.
Saverio Brancaccio wrote:
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
Please answer at least these tw
Hi Afif,
On Wed, May 15, 2019 at 10:57:49PM +0200, Salvatore Bonaccorso wrote:
> Then there is nothing further to be done.
Oh, actually there is an open point: Is it confirmed that 3.0.3 is not
affected by the CVE? Did you got any information why this is only
introduced in 3.1.0?
Regards,
Salvat
Processing commands for cont...@bugs.debian.org:
> tags 929034 + confirmed
Bug #929034 [evolvotron] evolvotron: Evolvotron can't stat (segmentation fault)
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
929034: https://bugs.debian.org/cgi-b
Processing commands for cont...@bugs.debian.org:
> notfound 929042 3.1.1+ds-1
Bug #929042 {Done: Afif Elghraoui }
[src:singularity-container] singularity-container: CVE-2019-11328
No longer marked as found in versions singularity-container/3.1.1+ds-1.
> thanks
Stopping processing here.
Please co
Hi Afif,
On Wed, May 15, 2019 at 08:54:03PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:singularity-container package:
>
> #929042: singularity-container: CVE-2019-11328
>
> It has been closed by Afif El
Your message dated Wed, 15 May 2019 16:51:24 -0400
with message-id <485aede8-7653-49da-97ec-be9fd454b...@debian.org>
and subject line Re: Bug#929042: singularity-container: CVE-2019-11328
has caused the Debian Bug report #929042,
regarding singularity-container: CVE-2019-11328
to be marked as done.
Source: singularity-container
Version: 3.1.1+ds-1
Severity: grave
Tags: security upstream
Hi,
The following vulnerability was published for singularity-container.
CVE-2019-11328[0]:
| An issue was discovered in Singularity 3.1.0 to 3.2.0-rc2, a malicious
| user with local/network access to the h
Package: evolvotron
Version: 0.7.1-2+b1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effe
Le 15/05/2019 à 19:32, Xavier Guimard a écrit :
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package cyrus-imapd
>
> Hi all,
>
> Buster has currently cyrus-imapd 3.0.8. Upstram last version is 3.0.9.
> This
Processing commands for cont...@bugs.debian.org:
> fixed 929007 3.20190514.1~
Bug #929007 {Done: Markus Schade } [intel-microcode]
intel-microcode: Update intel-microcode to 20190514
There is no source info for the package 'intel-microcode' at version
'3.20190514.1~' with architecture ''
Unable
Le 15/05/2019 à 16:17, Xavier a écrit :
> Le 15/05/2019 à 16:13, Anthony Prades a écrit :
>> On 5/15/19 4:10 PM, Xavier wrote:
>>> I can't reproduce this exact issue. After the upgrade process (with
>>> actual Buster packages), sieve rules are inoperative, but lmtpd won't
>>> segfault:
>>> * Start
Hi Michael,
Thank you for sharing your take.
On Sat, May 11, 2019 at 11:21:22AM +0200, Michael Biebl wrote:
Then there is the case, that I sometimes need to use software like
teamviewer (I know, bad proprietary software), which is not Wayland
ready. I need something cross-plattform though, an
Processing control commands:
> tags -1 +confirmed
Bug #928990 [dmarc-cat] dmarc-cat: attempts internet communication during build
Added tag(s) confirmed.
--
928990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 +confirmed
On 2019-05-14 20:47:26, Gianfranco Costamagna wrote:
> Hello, as said, the package attempts to do internet communication
> during build... this is forbidden by policy.
Agreed.
I don't know how to handle this in the package build... Maybe I should
just disable the test
Processing control commands:
> severity 928717 normal
Bug #928717 [src:asterisk] Build link error bundled pjproject : relocation
against symbol cant be used when shared object
Severity set to 'normal' from 'grave'
> tags 928717 unreproducible
Bug #928717 [src:asterisk] Build link error bundled pj
Le 15/05/2019 à 16:13, Anthony Prades a écrit :
> On 5/15/19 4:10 PM, Xavier wrote:
>> I can't reproduce this exact issue. After the upgrade process (with
>> actual Buster packages), sieve rules are inoperative, but lmtpd won't
>> segfault:
>> * Starting with a fresh stretch install, I create mail
On 5/15/19 4:10 PM, Xavier wrote:
> I can't reproduce this exact issue. After the upgrade process (with
> actual Buster packages), sieve rules are inoperative, but lmtpd won't
> segfault:
> * Starting with a fresh stretch install, I create mailboxes with and
>without dot in names.
> * In imap
Le 14/05/2019 à 11:00, Anthony Prades a écrit :
> Already done... Thank you Xavier.
>
> Anthony
>
> On 5/14/19 10:53 AM, Xavier wrote:
>> Le 09/05/2019 à 15:30, Xavier a écrit :
>>> Le 09/05/2019 à 15:13, Anthony Prades a écrit :
Hi,
I'll add this patch. We use it in production and
On Fri, 3 May 2019 23:09:33 +0300 Kari Pahula wrote:
> tags 926182 + patch
> thanks
>
> Hi.
>
> /usr/bin/guile uses alternatives system and the real binary is under
> /usr/lib, as well as providing /usr/bin/guile-2.2 as a symlink.
>
> My patch gives the same treatment for the binaries in guile-
Indeed, I had noticed so 2 months ago with 2.10.2
https://github.com/CloudCompare/CloudCompare/issues/861
And it was no problem with 2.10.1, back then. Trying to figure out what
the problem is...
Help is welcome.
Package: mutt
Version: 1.10.1-2
Severity: serious
Tags: security upstream fixed-upstream
The rfc2231.c file contains:
index = atoi (s);
where the string s is part of a RFC 2231 parameter in a header. For
instance, if in a message (invalid, but which can occur due to spam,
attack, etc.), on
Processing commands for cont...@bugs.debian.org:
> fixed 929007 3.20190514.1
Bug #929007 [intel-microcode] intel-microcode: Update intel-microcode to
20190514
Marked as fixed in versions intel-microcode/3.20190514.1.
> close 929007
Bug #929007 [intel-microcode] intel-microcode: Update intel-micro
Hi Otto
>If I don't get any more info on these bugs or precise steps on how to
>reproduce, I will just close this bug report. No point in keeping it
>hanging if nobody of the affected users supply more input.
Sorry, I've been in holiday and thereafter busy in other projects. I will
create a snap
Processing control commands:
> found -1 2.10.2-1
Bug #928986 [cloudcompare] CloudCompare: error while loading shared libraries:
libQCC_IO_LIB.so:
Marked as found in versions cloudcompare/2.10.2-1.
--
928986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928986
Debian Bug Tracking System
Con
Control: found -1 2.10.2-1
Hi,
On Tue, 14 May 2019 19:25:25 +0200 Johannes 'josch' Schauer
wrote:
> after installing the package, when attempting to start CloudCompare I
> get the following error message:
>
> CloudCompare: error while loading shared libraries: libQCC_IO_LIB.so:
> cannot open
Your message dated Wed, 15 May 2019 08:10:11 +
with message-id <20190515081011.ga13...@sarek.noreply.org>
and subject line Re: Bug#880047: postgrey doesn't start because it can't write
its pid
has caused the Debian Bug report #880047,
regarding postgrey doesn't start because it can't write its
Hi,
I'm still affected by this (must close timidity and restart pulseaudio
after a reboot), and judging from the comment
https://superuser.com/questions/1312163/dummy-output-instead-of-audio-device-on-debian-9/1346784?noredirect=1#comment2168375_1346784
I'm not the only person affected. So afaict
41 matches
Mail list logo
