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

Groups > comp.lang.c > #100315

Re: sscanf error checking

From Robert Wessel <robertwessel2@yahoo.com>
Newsgroups comp.lang.c
Subject Re: sscanf error checking
Message-ID <ll936cdvlo8dsc0fqjff20lgrvjqf3noth@4ax.com> (permalink)
References (2 earlier) <77a15075-1f22-405c-a896-061dda988473@googlegroups.com> <lnbmwdm1se.fsf@kst-u.example.com> <9fc98e35-35c8-49e5-b733-6868ca58c459@googlegroups.com> <ln8trglntm.fsf@kst-u.example.com> <856d347f-6931-4fc3-8370-c010b004ec5f@googlegroups.com>
Organization Forte - www.forteinc.com
Date 2016-12-26 17:25 -0600

Show all headers | View raw

On Thu, 15 Dec 2016 16:37:02 -0800 (PST), Malcolm McLean
<malcolm.mclean5@btinternet.com> wrote:

>On Friday, December 16, 2016 at 12:29:53 AM UTC, Keith Thompson wrote:
>> Malcolm McLean <malcolm.mclean5@btinternet.com> writes:
>>
>> > So there's not much point in putting in security measures.
>> 
>> Huh?
>> 
>If the environment is such that user can write, compile and run 
>arbitrary C code with the same privileges as your program, 
>then there's no point in having any security against a malicious
>user. Against malicious inputs that may be provided by someone
>else, yes.


Non-malicious users are constantly fooled into passing malicious input
to programs.

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

Thread

sscanf error checking BartC <bc@freeuk.com> - 2016-12-14 15:42 +0000
  Re: sscanf error checking John Gordon <gordon@panix.com> - 2016-12-14 15:58 +0000
    Re: sscanf error checking Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-12-14 11:14 -0500
  Re: sscanf error checking gazelle@shell.xmission.com (Kenny McCormack) - 2016-12-14 16:11 +0000
    Re: sscanf error checking BartC <bc@freeuk.com> - 2016-12-14 17:51 +0000
      Re: sscanf error checking gazelle@shell.xmission.com (Kenny McCormack) - 2016-12-14 18:09 +0000
      Re: sscanf error checking Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-12-14 19:49 +0000
        Re: sscanf error checking BartC <bc@freeuk.com> - 2016-12-14 20:43 +0000
  Re: sscanf error checking Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-12-14 16:40 +0000
  Re: sscanf error checking Keith Thompson <kst-u@mib.org> - 2016-12-14 09:34 -0800
  Re: sscanf error checking Robert Wessel <robertwessel2@yahoo.com> - 2016-12-14 14:52 -0600
    Re: sscanf error checking supercat@casperkitty.com - 2016-12-15 07:24 -0800
      Re: sscanf error checking Keith Thompson <kst-u@mib.org> - 2016-12-15 11:26 -0800
        Re: sscanf error checking Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-15 15:35 -0800
          Re: sscanf error checking Keith Thompson <kst-u@mib.org> - 2016-12-15 16:28 -0800
            Re: sscanf error checking Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-12-15 16:37 -0800
              Re: sscanf error checking Robert Wessel <robertwessel2@yahoo.com> - 2016-12-26 17:25 -0600
        Re: sscanf error checking supercat@casperkitty.com - 2016-12-15 16:38 -0800
      Re: sscanf error checking raltbos@xs4all.nl (Richard Bos) - 2016-12-15 20:20 +0000
        Re: sscanf error checking Keith Thompson <kst-u@mib.org> - 2016-12-15 12:33 -0800
  sscanf error checking asetofsymbols@gmail.com - 2016-12-16 01:49 -0800
    sscanf error checking asetofsymbols@gmail.com - 2016-12-16 01:53 -0800

csiph-web