From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Scanning double sided documents and printing them the same.
Date: Thu, 10 Dec 2020 22:25:57 -0000 (UTC) [thread overview]
Message-ID: <rqu79l$jh2$3@ciao.gmane.io> (raw)
In-Reply-To: 4074691.ejJDZkT8p0@lenovo.localdomain
On 2020-12-10, Michael <confabulate@kintzios.com> wrote:
>
>> There's no need for the two-step process:
>>
>> $ convert scan1.png scan2.png scanned.pdf
>
> There was some vulnerability in ghostscript[1] which disabled the above
> conversion - but I can't find the BGO number. I thought it had been patched
> since then, but my system appears to not have been fixed:
>
> $ convert scan1.jpg scan2.jpg scan.pdf
> convert: attempt to perform an operation not allowed by the security policy
> `PDF' @ error/constitute.c/IsCoderAuthorized/422.
>
> [1] https://www.kb.cert.org/vuls/id/332928/
You're right. You have to adjust the ImageMagick config files to allow
converting to pdf. AFAICT, it's safe as long as you trust the input
you're converting. I figure photos I've taken are OK.
--
Grant
next prev parent reply other threads:[~2020-12-10 22:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 0:09 [gentoo-user] Scanning double sided documents and printing them the same Dale
2020-12-10 0:46 ` thelma
2020-12-10 1:29 ` thelma
2020-12-10 2:16 ` Dale
2020-12-10 8:27 ` Neil Bothwick
2020-12-10 9:20 ` Michael
2020-12-10 9:26 ` Neil Bothwick
2020-12-10 15:21 ` [gentoo-user] " Grant Edwards
2020-12-10 17:36 ` Michael
2020-12-10 22:25 ` Grant Edwards [this message]
2020-12-11 0:00 ` Dale
2020-12-11 0:04 ` Dale
2020-12-10 9:28 ` [gentoo-user] " J. Roeleveld
2020-12-10 10:49 ` Dr Rainer Woitok
2020-12-10 13:09 ` J. Roeleveld
2020-12-10 15:37 ` Rich Freeman
2020-12-10 17:58 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='rqu79l$jh2$3@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox