Brian May writes:
> In March I had 10 hours allocated, and I used all 10 hours on the
> following tasks:
In March I was given another 5.75 hours in addition to the 10 hours in
my previous report, and I used 5.75001 hours on:
* Following up on various bits from previous work.
* Creating and
On Monday 26 March 2018 04:14 PM, Gero Treuner wrote:
> Hi Abhijith,
>
> On Fri, Mar 23, 2018 at 07:39:58PM +0530, Abhijith PA wrote:
>> I couldn't find php plugin for uwsgi in wheezy. What are the other ways
>> to test around it.
>
> You are absolutely right - it can't be tested because ... it
Hi everybody,
I uploaded version 1:2.1.7-7+deb7u2 of dovecot to:
https://people.debian.org/~alteholz/packages/wheezy-lts/dovecot/
It contains patches for CVE-2017-14461, CVE-2017-15130 and CVE-2017-15132.
Please give it a try and tell me about any problems you met.
Thanks!
Thorsten
Antoine Beaupré writes:
> I'm not sure. The security team marked that as "no-dsa (minor issue)"
> for jessie and stretch, and fixed in pycryptodome 3.4.11-1... Couldn't
> we reuse the fixes from cryptodome to get this working properly? Or is
> this what you say breaks API compatibility?
I don't
El 2018-03-26 a las 16:43 +0100, Ben Hutchings escribió:
> On Mon, 2018-03-26 at 15:53 +0200, Camaleón wrote:
> > CC'ing also "debian-lts@lists.debian.org"
> >
> > Hello there,
> >
> > Any updates on this?
> >
> > http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2018-February/015447.ht
On Mon, 2018-03-26 at 19:05 +0530, VigneshDhanraj G wrote:
> Hi,
>
> After microcode update, for signature=0x306a9 upgraded revision should be
> 0x1f but dmesg shows wrong revision any ideas what went wrong.
>
> i have upgraded microcode using apt-get install iucode_tool.
[...]
That's a tool for
Hi Ben et al.,
> > However, irssi for amd64 arch is at version 0.8.15-5+deb7u5 and debsecan
> > bugs me daily about available security update, which is not true.
[…]
> It's a bug in irssi. The source package is broken and could not be
> built automatically because the patch for CVE-2018-7051 is m
Package: ftp.debian.org
Severity: normal
See #815060 for the license issue.
The Linux kernel ABI in jessie was changed in January as a result of
the mitigation of the Meltdown security issue. This package would
need to be updated to build new compatible modules, but that should
not be done due t
On Mon, 2018-03-26 at 15:53 +0200, Camaleón wrote:
> CC'ing also "debian-lts@lists.debian.org"
>
> Hello there,
>
> Any updates on this?
>
> http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2018-February/015447.html
That advice is still valid.
Ben.
--
Ben Hutchings
When in doubt, us
On Sun, 2018-03-25 at 12:56 +0200, Matus UHLAR - fantomas wrote:
> Hello,
>
> I have debsecan on debian 7 installed.
>
> my architecture is i386 and I have irssi installed, in current version
> 0.8.15-5+deb7u4 available for i386.
>
> However, irssi for amd64 arch is at version 0.8.15-5+deb7u5 an
On 26.03.18 19:05, VigneshDhanraj G wrote:
After microcode update, for signature=0x306a9 upgraded revision should be
0x1f but dmesg shows wrong revision any ideas what went wrong.
according to the log, firmware was updated from 0x17 to 0x1b
which version of intel-microcode do you have installed
On 2018-02-20 07:33:27, Brian May wrote:
> Any comments? Where should we go from here?
I'm not sure. The security team marked that as "no-dsa (minor issue)"
for jessie and stretch, and fixed in pycryptodome 3.4.11-1... Couldn't
we reuse the fixes from cryptodome to get this working properly? Or is
CC'ing also "debian-lts@lists.debian.org"
Hello there,
Any updates on this?
http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2018-February/015447.html
Thanks!
--
Camaleón
Hi,
After microcode update, for signature=0x306a9 upgraded revision should be
0x1f but dmesg shows wrong revision any ideas what went wrong.
i have upgraded microcode using apt-get install iucode_tool.
In intel release notes, came across the below notes which says that it
should upgraded to 0x1f
14 matches
Mail list logo
