Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.lisp > #32798

Re: Buffer Overflow in LISP

Show all headers | View raw

On Thu, 25 Apr 2019 19:22:30 +0200
"Pascal J. Bourguignon" <pjb@informatimago.com> wrote:
> Barry Margolin <barmar@alum.mit.edu> writes:
> > C was created for writing an operating system. Efficiency is extremely 
> > important, so adding bounds checks to every memory access would impose 
> > an unacceptable performance penalty.
> 
> On the other hand, ensuring that the OS doesn't crash, or doesn't leak
> security holes WAS NOT important, since UNIx was essentially a
> single-user operating system on a small mini-computer.

It is always important that the operating system doesn't crash. But if it
crashes it's only inconvenient when it happens whereas if it's too slow ,
it's inconvenient *all* the time.

> Nowadays, unix
> runs computers mostly for single-user computers (phones, tablets,
> workstations), and very rarely for multiple users on big-iron.

Citation needed. In particular I note that a workstation in a business
or academic environment will likely have multiple users ; in general only
one user will be sitting in front of the computer but other users may
be remotely logged in or run background processes. And what about a web
server ? Does it count as <single user> or <multiple users> ?

> > C's data model also makes it hard to implement these checks
> > efficiently.
> 
> Who cares, when we have pipelined Intel processors?

If by "who cares" you mean that it's pointless to worry about safety on
the language level when running code on an modern Intel processor since
it has built-in vulnerabilities {en.wikipedia.org/wiki/Intel_Management_Engine} ,
I agree completely.

-- 
Hope that no one on a film set will ever again ask me where to get a ladder. (The answer
is the Grip Department. The answer is always the Grip Department).
  http://www.svnfilm.com/resources/general-content/278-the-seven-arts-of-working-in-film-a-necessary-guide-to-on-set-protocol.html

Back to comp.lang.lisp | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Buffer Overflow in LISP yara.huss.113@gmail.com - 2019-04-25 03:52 -0700
  Re: Buffer Overflow in LISP shcv@sdf.org - 2019-04-25 09:21 -0400
  Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-04-25 15:21 +0200
    Re: Buffer Overflow in LISP Barry Margolin <barmar@alum.mit.edu> - 2019-04-25 11:04 -0400
      Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-04-25 19:22 +0200
        Re: Buffer Overflow in LISP Spiros Bousbouras <spibou@gmail.com> - 2019-04-28 08:34 +0000
          Re: Buffer Overflow in LISP Barry Margolin <barmar@alum.mit.edu> - 2019-04-29 12:31 -0400
        Re: Buffer Overflow in LISP a.daniel.eliason@gmail.com - 2019-05-23 08:35 -0700
          Re: Buffer Overflow in LISP Kaz Kylheku <847-115-0292@kylheku.com> - 2019-05-23 17:02 +0000
            Re: Buffer Overflow in LISP Stefan Monnier <monnier@iro.umontreal.ca> - 2019-05-30 15:50 -0400
          Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-23 19:30 +0200
            Re: Buffer Overflow in LISP taruss@google.com - 2019-05-24 10:40 -0700
              Re: Buffer Overflow in LISP Paul Rubin <no.email@nospam.invalid> - 2019-05-24 10:45 -0700
                Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-24 23:27 +0200
                [OT] was: Buffer Overflow in LISP Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-05-24 22:46 +0100
                Re: [OT] was: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-25 01:00 +0200
                Re: [OT] was: Buffer Overflow in LISP Kaz Kylheku <847-115-0292@kylheku.com> - 2019-05-24 23:46 +0000
                Re: [OT] was: Buffer Overflow in LISP Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-05-25 01:35 +0100
                Re: Buffer Overflow in LISP Jason Cornez <jcornez@ravenpack.com> - 2019-05-29 16:10 +0200
                Re: Buffer Overflow in LISP "Pascal J. Bourguignon" <pjb@informatimago.com> - 2019-05-29 20:25 +0200
      Re: Buffer Overflow in LISP Vladimir Sedach <vsedach@oneofus.la> - 2019-09-22 21:26 -0700
        Re: Buffer Overflow in LISP Barry Margolin <barmar@alum.mit.edu> - 2019-09-23 00:45 -0400

csiph-web