ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Henning Hraban Ramm <texml@fiee.net>
Subject: Re: PDF viewer poll
Date: Sat, 19 Oct 2019 12:51:39 +0200	[thread overview]
Message-ID: <45f2f677-9378-1ce8-fc77-cc7276040403@xs4all.nl> (raw)
In-Reply-To: <C3078F30-ADD8-49AD-B2FF-298A4F98E74C@fiee.net>

On 10/19/2019 12:21 PM, Henning Hraban Ramm wrote:

> When I read "Java runs on millions of devices" I don’t feel that’s good advertising, but it remembers me that each of those devices is at risk.

The java updates keept telling that it runs on 3 billion devices but 
that message doesn't change over years. I always wonder about numbers. 
One can find similar huge numbers for tex usage but what defines usage 
(forced? ontime? for fun? lifelong? advanced or like any word processor 
usage?).

>> Just 2 cents from a JS programmer who actually thinks that JS is not the
>> worst Lisp dialect out there.
> 
> I didn’t say JS is bad. For me it’s a necessary evil.
> I don’t think my beloved Python would be a better choice for client scripts.
> Maybe Lua is, but every scriptable program is a risk.

The fact that it's simple kind of helps. One can disable by overloading.

> LuaTeX and write18 _are_ dangerous.

Sure, so can be crossing a street. Anyway, for quite a while there 
actually is a sandbox model in context which can limit its scope pretty 
much but it (being done a while ago) hasn't been tested that much (afer 
all I dont' need it).

> It would be very easy to spread malicious TeX code, since everyone uses CTAN (LaTeX) packages without checking them first.
> But it wouldn’t come far, I guess, for it needs a while for a package to become known and in wide use, and that still means only in a subset of the (La)TeX community, where there are enough expert hackers who would find this malicious code.
> And you can count the people on one hand who would be able to publish a malicious ConTeXt module… Malicious code snippets in our wiki or ML also wouldn’t come far.

Also, I tend to stay optimistic. If there were way more strict rules for 
software abuse (with hard penalties) it would be less of a problem, but 
for now we just have to trust. So, far we could trust texies.

> There was PDF malware (using JS or media stuff). There also was PostScript malware in its time. The latter didn’t make a lot of sense, except it could destroy RIP hardware. The RIP technician at the newspaper where I worked told me stories, e.g. there was an evil EPS (some faulty customer logo, no deliberate malware) that caused the deletion of important parts of the RIP software. At my time there was a PS ghost: somehow a page got installed on one of the printers and got printed at odd times. Reboot didn’t help, we never found the cause.
Writing could be restricted I guess, so wiping rip source is also bit of 
a bug in the rip i guess. Anyway, I do remember sending postscript to 
our printer just to find out that you ended up with an empty paperbin 
and a few lines per page with garbage ascii. In that respect pdf is a 
bit better: something or nothing gets printed.

This ghost: makes for nice debugging. Kind of a challenge.

(btw, this makes for a nice topic next meeting: security and documents 
and such)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-10-19 10:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13 10:43 Henning Hraban Ramm
2019-10-13 10:47 ` denis.maier
2019-10-13 14:50 ` Rudolf Bahr
2019-10-13 15:26   ` Henning Hraban Ramm
2019-10-13 15:50     ` Pablo Rodriguez
2019-10-14 17:09     ` Greedwolf DSS
2019-10-13 16:49 ` Pablo Rodriguez
2019-10-13 18:02   ` kaddour kardio
2019-10-13 18:28 ` Hans Åberg
2019-10-14  7:58 ` Taco Hoekwater
2019-10-14  9:17 ` Hans Hagen
2019-10-15  4:42   ` Henning Hraban Ramm
2019-10-15  6:17     ` Marcin Borkowski
2019-10-19 10:21       ` Henning Hraban Ramm
2019-10-19 10:51         ` Hans Hagen [this message]
2019-10-19 11:06           ` Henning Hraban Ramm
2019-10-20 20:15         ` Marcin Borkowski
2019-10-21  8:21           ` Hans Hagen
2019-10-15  8:11     ` Hans Hagen
2019-10-15  8:12     ` Taco Hoekwater
2019-10-15  8:21       ` Hans Hagen
2019-10-15  8:25         ` luigi scarso
2019-10-16  8:02   ` luigi scarso
2019-10-14 16:55 ` Marcin Borkowski
2019-10-15 15:40   ` Benct Philip Jonsson
2019-10-15  4:26 ` Alan Braslau
2019-10-15  4:58 ` Hamid,Idris
2019-10-19 19:27   ` Henning Hraban Ramm
2019-10-15  5:00 ` Otared Kavian
2019-10-15 11:58 ` luigi scarso
2019-10-16  9:30 ` context
2019-10-13 18:21 Damien Thiriet

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=45f2f677-9378-1ce8-fc77-cc7276040403@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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;
as well as URLs for NNTP newsgroup(s).