Bug#882020: Info received (Bug#882020: Info received (Welcome To Amazon. XQUq))

2017-11-19 Thread Tony Qudsi 
Danke.

On Nov 19, 2017 9:36 AM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Laszlo Boszormenyi (GCS) 
>
> If you wish to submit further information on this problem, please
> send it to 882...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 882020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882020
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#882020: Info received (Welcome To Amazon. Z68ZUv)

2017-11-19 Thread Tony Qudsi 
Danke.

On Nov 19, 2017 9:27 AM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Laszlo Boszormenyi (GCS) 
>
> If you wish to submit further information on this problem, please
> send it to 882...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 882020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882020
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#882020: Info received (Welcome To Amazon. XQUq)

2017-11-19 Thread Tony Qudsi 
Danke.

On Nov 19, 2017 9:27 AM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Laszlo Boszormenyi (GCS) 
>
> If you wish to submit further information on this problem, please
> send it to 882...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 882020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882020
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#882020: Welcome To Amazon. XQUq

2017-11-19 Thread Tony Qudsi 
Danke.

On Nov 19, 2017 8:15 AM, "important notice"  wrote:

> important information
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sun, 19 Nov 2017 15:06:44 + with message-id and
> subject line Bug#882020: fixed in socat 1.7.3.2-2 has caused the Debian Bug
> report #882020, regarding socat: Fails to build on Hurd to be marked as
> done. This means that you claim that the problem has been dealt with. If
> this is not the case it is now your responsibility to reopen the Bug report
> if necessary, and/or fix the problem forthwith. (NB: If you are a system
> administrator and have no idea what this message is talking about, this may
> indicate a serious mail system misconfiguration somewhere. Please contact
> ow...@bugs.debian.org immediately.) -- 882020:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882020 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Andreas Henriksson 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Fri, 17 Nov 2017 18:59:28 +0100
> Subject: socat: Fails to build on Hurd
> Package: socat
> Version: 1.7.3.2-1
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
> It seems socat fails to build on hurd. This in turn affects util-linux
> which has a build-dependency on socat for tests. Rather than excluding
> socat specifically on hurd, I think it would be better to have socat
> building.
>
> Not a hurd expert myself so took the simplest possible way forward
> in the attached patch which I've confirmed to build on the hurd
> porterbox. Hopefully an actual hurd porter can improve on it if needed
> (and actually runtime test the results).  See also comments in patch
> header.
>
> Regards,
> Andreas Henriksson
>
>
>
> -- Forwarded message --
> From: Laszlo Boszormenyi 
> To: 882020-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sun, 19 Nov 2017 15:06:44 +
> Subject: Bug#882020: fixed in socat 1.7.3.2-2
> Source: socat
> Source-Version: 1.7.3.2-2
>
> We believe that the bug you reported is fixed in the latest version of
> socat, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 882...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Laszlo Boszormenyi (GCS)  (supplier of updated socat
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Sun, 19 Nov 2017 13:56:10 +
> Source: socat
> Binary: socat
> Architecture: source amd64
> Version: 1.7.3.2-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Laszlo Boszormenyi (GCS) 
> Changed-By: Laszlo Boszormenyi (GCS) 
> Description:
>  socat  - multipurpose relay for bidirectional data transfer
> Closes: 882020
> Changes:
>  socat (1.7.3.2-2) unstable; urgency=medium
>  .
>* Update Standards-Version to 4.1.1:
>  - change package priority to optional.
>* Remove dh-autoreconf build dependency.
>  .
>[ Andreas Henriksson  ]
>* Have compat.h define PATH_MAX if undefined (closes: #882020).
> Checksums-Sha1:
>  d986951fb520e3e522e86e2d9fce455312085447 1730 socat_1.7.3.2-2.dsc
>  a8e9b9b3bb47d7997a98bb1dbfa194c03bf2c6d3 9796
> socat_1.7.3.2-2.debian.tar.xz
>  237084697dd4347cccbb31e4709ae685130b5472 552672
> socat-dbgsym_1.7.3.2-2_amd64.deb
>  5f22645ee17761b90c71fb6407f2fdba59a1b565 6558 socat_1.7.3.2-2_amd64.
> buildinfo
>  aa30cac1e1145e57e18495da32670a36cb8c028c 357680 socat_1.7.3.2-2_amd64.deb
> Checksums-Sha256:
>  1872142f251e2bddc750fd033398554625111ab74273fcbad66885367c2d553b 1730
> socat_1.7.3.2-2.dsc
>  f0b62497913019a026deedf6727b9dc54aa4f5ad0ec1a4a298715da9b6456397 9796
> socat_1.7.3.2-2.debian.tar.xz
>  8abdf907256faa11d58a31b0c2256df8e7998c5f49a08cbb2fa4bfaaa8a383bb 552672
> socat-dbgsym_1.7.3.2-2_amd64.deb
>  c34a74e37b5a3de0b84d71b66c7032d2b09aa6cdab553122f35650e96893df6b 6558
> socat_1.7.3.2-2_amd64.buildinfo
>  43075db7598277bdfeca9adf6b43bc6592f2017fdfa3c7d61f923563d7e90853 357680
> socat_1.7.3.2-2_amd64.deb
> Files:
>  84daeb0f30e02debcac03979ac6e0fde 1730 net optional socat_1.7.3.2-2.dsc
>  d7ee38e0425cf1fe0c062caca962f4f5 9796 net optional
> socat_1.7.3.2-2.debian.tar.xz
>

Bug#882020: Welcome To Amazon. Z68ZUv

2017-11-19 Thread Tony Qudsi 
Danke.

On Nov 19, 2017 8:15 AM, "important notice"  wrote:

important information






















































































Your message dated Sun, 19 Nov 2017 15:06:44 + with message-id and
subject line Bug#882020: fixed in socat 1.7.3.2-2 has caused the Debian Bug
report #882020, regarding socat: Fails to build on Hurd to be marked as
done. This means that you claim that the problem has been dealt with. If
this is not the case it is now your responsibility to reopen the Bug report
if necessary, and/or fix the problem forthwith. (NB: If you are a system
administrator and have no idea what this message is talking about, this may
indicate a serious mail system misconfiguration somewhere. Please contact
ow...@bugs.debian.org immediately.) -- 882020: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=882020 Debian Bug Tracking System Contact
ow...@bugs.debian.org with problems

-- Forwarded message --
From: Andreas Henriksson 
To: Debian Bug Tracking System 
Cc:
Bcc:
Date: Fri, 17 Nov 2017 18:59:28 +0100
Subject: socat: Fails to build on Hurd
Package: socat
Version: 1.7.3.2-1
Severity: normal
Tags: patch

Dear Maintainer,

It seems socat fails to build on hurd. This in turn affects util-linux
which has a build-dependency on socat for tests. Rather than excluding
socat specifically on hurd, I think it would be better to have socat
building.

Not a hurd expert myself so took the simplest possible way forward
in the attached patch which I've confirmed to build on the hurd
porterbox. Hopefully an actual hurd porter can improve on it if needed
(and actually runtime test the results).  See also comments in patch
header.

Regards,
Andreas Henriksson



-- Forwarded message --
From: Laszlo Boszormenyi 
To: 882020-cl...@bugs.debian.org
Cc:
Bcc:
Date: Sun, 19 Nov 2017 15:06:44 +
Subject: Bug#882020: fixed in socat 1.7.3.2-2
Source: socat
Source-Version: 1.7.3.2-2

We believe that the bug you reported is fixed in the latest version of
socat, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated socat
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Nov 2017 13:56:10 +
Source: socat
Binary: socat
Architecture: source amd64
Version: 1.7.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 socat  - multipurpose relay for bidirectional data transfer
Closes: 882020
Changes:
 socat (1.7.3.2-2) unstable; urgency=medium
 .
   * Update Standards-Version to 4.1.1:
 - change package priority to optional.
   * Remove dh-autoreconf build dependency.
 .
   [ Andreas Henriksson  ]
   * Have compat.h define PATH_MAX if undefined (closes: #882020).
Checksums-Sha1:
 d986951fb520e3e522e86e2d9fce455312085447 1730 socat_1.7.3.2-2.dsc
 a8e9b9b3bb47d7997a98bb1dbfa194c03bf2c6d3 9796 socat_1.7.3.2-2.debian.tar.xz
 237084697dd4347cccbb31e4709ae685130b5472 552672
socat-dbgsym_1.7.3.2-2_amd64.deb
 5f22645ee17761b90c71fb6407f2fdba59a1b565 6558 socat_1.7.3.2-2_amd64.
buildinfo
 aa30cac1e1145e57e18495da32670a36cb8c028c 357680 socat_1.7.3.2-2_amd64.deb
Checksums-Sha256:
 1872142f251e2bddc750fd033398554625111ab74273fcbad66885367c2d553b 1730
socat_1.7.3.2-2.dsc
 f0b62497913019a026deedf6727b9dc54aa4f5ad0ec1a4a298715da9b6456397 9796
socat_1.7.3.2-2.debian.tar.xz
 8abdf907256faa11d58a31b0c2256df8e7998c5f49a08cbb2fa4bfaaa8a383bb 552672
socat-dbgsym_1.7.3.2-2_amd64.deb
 c34a74e37b5a3de0b84d71b66c7032d2b09aa6cdab553122f35650e96893df6b 6558
socat_1.7.3.2-2_amd64.buildinfo
 43075db7598277bdfeca9adf6b43bc6592f2017fdfa3c7d61f923563d7e90853 357680
socat_1.7.3.2-2_amd64.deb
Files:
 84daeb0f30e02debcac03979ac6e0fde 1730 net optional socat_1.7.3.2-2.dsc
 d7ee38e0425cf1fe0c062caca962f4f5 9796 net optional
socat_1.7.3.2-2.debian.tar.xz
 5c66936451a9cc6f0d706b16204ed654 552672 debug optional
socat-dbgsym_1.7.3.2-2_amd64.deb
 6a334c2d70d7bee6dc5fcb982536987c 6558 net optional socat_1.7.3.2-2_amd64.
buildinfo
 fb58b8c99be045183716a16c1a77a3bb 357680 net optional
socat_1.7.3.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ5

Bug#882051: Welcome To Amazon..LdAqAz

2017-11-19 Thread Tony Qudsi 
 شكرا.

On Nov 19, 2017 8:45 AM, "final notice"  wrote:

> important information
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Package: release.debian.org Severity: normal User:
> release.debian@packages.debian.org Usertags: binnmu debhelper 10.10.7
> fixed a regression in debhelper 10.10.6 that prevented dbgsym packages from
> being generated. There are probably several packages affected but I am not
> aware of any easy mechanism to determine which packages were built against
> debhelper 10.10.6 so I've just included a binNMU request for the two
> packages I'm aware of that were definitely affected by this. debhelper
> (10.10.7) unstable; urgency=medium * dh_strip: Fix a regression that caused
> debug symbols for executables to be discarded instead of included into
> debug packages. nmu xdg-desktop-portal_0.8-3 . amd64 arm64 i386 mips64el
> mips powerpc ppc64el s390x . unstable . -m "Rebuild to include dbgsym
> packages after debhelper 10.10.7 fix" nmu xdg-desktop-portal-gtk_0.7-3 .
> amd64 arm64 i386 mips64el mips powerpc ppc64el s390x . unstable . -m
> "Rebuild to include dbgsym packages after debhelper 10.10.7 fix" -- bye,
> pabs https://wiki.debian.org/PaulWise

Bug#882051: Welcome To Amazon..hmud

2017-11-19 Thread Tony Qudsi 
Danke.

On Nov 19, 2017 8:45 AM, "final notice"  wrote:

> important information
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Package: release.debian.org Severity: normal User:
> release.debian@packages.debian.org Usertags: binnmu debhelper 10.10.7
> fixed a regression in debhelper 10.10.6 that prevented dbgsym packages from
> being generated. There are probably several packages affected but I am not
> aware of any easy mechanism to determine which packages were built against
> debhelper 10.10.6 so I've just included a binNMU request for the two
> packages I'm aware of that were definitely affected by this. debhelper
> (10.10.7) unstable; urgency=medium * dh_strip: Fix a regression that caused
> debug symbols for executables to be discarded instead of included into
> debug packages. nmu xdg-desktop-portal_0.8-3 . amd64 arm64 i386 mips64el
> mips powerpc ppc64el s390x . unstable . -m "Rebuild to include dbgsym
> packages after debhelper 10.10.7 fix" nmu xdg-desktop-portal-gtk_0.7-3 .
> amd64 arm64 i386 mips64el mips powerpc ppc64el s390x . unstable . -m
> "Rebuild to include dbgsym packages after debhelper 10.10.7 fix" -- bye,
> pabs https://wiki.debian.org/PaulWise

Bug#882022: Congratulations Amazon Shopper! rA

2017-11-18 Thread Tony Qudsi 
Checkk!

On Nov 18, 2017 8:52 AM, "Thank you"  wrote:

Your $50 Reward



































































































































Your message dated Sat, 18 Nov 2017 16:18:11 +0100 with message-id
<20171118151811.zmc3avxjwvqml...@dinghy.sail.spinnaker.de> has caused the
report #882022, regarding fig2dev: buffer underwrite in get_line() to be
marked as having been forwarded to the upstream software author(s) Thomas
Loimer (NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.) -- 882022:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882022
Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

-- Forwarded message --
From: Roland Rosenfeld 
To: Thomas Loimer 
Cc: 882022-forwar...@bugs.debian.org
Bcc:
Date: Sat, 18 Nov 2017 16:18:11 +0100
Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
Hi Thomas!

I'm not sure, whether a string length of 0 or 1 can really happen
here, but you're deeper in the code than me...

- Forwarded message from Jakub Wilk  -

From: Jakub Wilk 
Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
To: sub...@bugs.debian.org
Date: Fri, 17 Nov 2017 19:00:56 +0100
Reply-To: Jakub Wilk , 882...@bugs.debian.org

Package: fig2dev
Version: 1:3.2.6a-6

The get_line() function in fig2dev/read.c does this:

  len = strlen(buf);
  buf = '\0';   /* strip trailing newline */
  if (buf == '\r')
  buf = '\0';   /* strip any trailing CRs */
  return 1;

If the string length is 0 (or 1 is some cases), this writes outside the
buffer.

--
Jakub Wilk


- End forwarded message -

Tscho

Roland

Bug#882022: Congratulations Amazon Shopper! VB

2017-11-18 Thread Tony Qudsi 
Thank you shopper!

On Nov 18, 2017 8:51 AM, "Thank you"  wrote:

> Your $50 Reward
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 18 Nov 2017 16:18:11 +0100 with message-id
> <20171118151811.zmc3avxjwvqml...@dinghy.sail.spinnaker.de> has caused the
> report #882022, regarding fig2dev: buffer underwrite in get_line() to be
> marked as having been forwarded to the upstream software author(s) Thomas
> Loimer (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.) -- 882022: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882022
> Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Roland Rosenfeld 
> To: Thomas Loimer 
> Cc: 882022-forwar...@bugs.debian.org
> Bcc:
> Date: Sat, 18 Nov 2017 16:18:11 +0100
> Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
> Hi Thomas!
>
> I'm not sure, whether a string length of 0 or 1 can really happen
> here, but you're deeper in the code than me...
>
> - Forwarded message from Jakub Wilk  -
>
> From: Jakub Wilk 
> Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
> To: sub...@bugs.debian.org
> Date: Fri, 17 Nov 2017 19:00:56 +0100
> Reply-To: Jakub Wilk , 882...@bugs.debian.org
>
> Package: fig2dev
> Version: 1:3.2.6a-6
>
> The get_line() function in fig2dev/read.c does this:
>
>   len = strlen(buf);
>   buf = '\0';   /* strip trailing newline */
>   if (buf == '\r')
>   buf = '\0';   /* strip any trailing CRs */
>   return 1;
>
> If the string length is 0 (or 1 is some cases), this writes outside the
> buffer.
>
> --
> Jakub Wilk
>
>
> - End forwarded message -
>
> Tscho
>
> Roland
>
>

Bug#882022: Congratulations Amazon Shopper! n0K1

2017-11-18 Thread Tony Qudsi 
Rewards 4 shopping!

On Nov 18, 2017 8:52 AM, "Thank you"  wrote:

> Your $50 Reward
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 18 Nov 2017 16:18:11 +0100 with message-id
> <20171118151811.zmc3avxjwvqml...@dinghy.sail.spinnaker.de> has caused the
> report #882022, regarding fig2dev: buffer underwrite in get_line() to be
> marked as having been forwarded to the upstream software author(s) Thomas
> Loimer (NB: If you are a system administrator and have no idea what this
> message is talking about, this may indicate a serious mail system
> misconfiguration somewhere. Please contact ow...@bugs.debian.org
> immediately.) -- 882022: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882022
> Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Roland Rosenfeld 
> To: Thomas Loimer 
> Cc: 882022-forwar...@bugs.debian.org
> Bcc:
> Date: Sat, 18 Nov 2017 16:18:11 +0100
> Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
> Hi Thomas!
>
> I'm not sure, whether a string length of 0 or 1 can really happen
> here, but you're deeper in the code than me...
>
> - Forwarded message from Jakub Wilk  -
>
> From: Jakub Wilk 
> Subject: Bug#882022: fig2dev: buffer underwrite in get_line()
> To: sub...@bugs.debian.org
> Date: Fri, 17 Nov 2017 19:00:56 +0100
> Reply-To: Jakub Wilk , 882...@bugs.debian.org
>
> Package: fig2dev
> Version: 1:3.2.6a-6
>
> The get_line() function in fig2dev/read.c does this:
>
>   len = strlen(buf);
>   buf = '\0';   /* strip trailing newline */
>   if (buf == '\r')
>   buf = '\0';   /* strip any trailing CRs */
>   return 1;
>
> If the string length is 0 (or 1 is some cases), this writes outside the
> buffer.
>
> --
> Jakub Wilk
>
>
> - End forwarded message -
>
> Tscho
>
> Roland
>
>