That was it, working now.
Thank you Peter and everybody else who replied :)
For the future - would you recommend a list / forum better suited for
these kinds of questions?
On 11/01/2018 17:08, Peter Ludikovsky wrote:
Hi!
The change was possibly introduced in the latest release, with the
cha
versed DNS lookup) apart
from this single error message.
Connection is established fine when I replace *.example.com with an IP
address but that's not very scalable.
Can somebody possibly put me in the right direction?
Regards
Adam Weremczuk
Hello,
Our quarterly PCI compliance scan has just challenged us on the following:
https://vulners.com/nessus/OPENSSH_76.NASL
Also referred to as OSVDB-166706.
As it's quite new I can't find much information on it online in terms of
potential hotfixes and workarounds.
There is no openssh ver
fix as 7.5 only appears to be
available in unstable releases (buster and sid)?
In Debian world - what's the relation / difference between OSVDBs and CVEs ?
Regards
Adam
On 09/08/2017 09:36, Salvatore Bonaccorso wrote:
Hi
On Wed, Aug 09, 2017 at 09:21:42AM +0100, Adam Weremczuk wrote:
Hello,
Could somebody confirm the status of the following:
CVE-2014-1692
CVE-2014-2532
CVE-2015-5352
CVE-2015-5600
CVE-2015-6563
CVE-2015-6564
CVE-2015-6565
CVE-2016-10009
CVE-2016-10010
CVE-2016-10011
CVE-2016-10012
OSVDB-144000
in 6.0p1-4+deb7u6 ?
I've searched for references in
/usr/share/
5 matches
Mail list logo
