public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"vit9696@protonmail.com" <vit9696@protonmail.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 0/1] Add PCD to disable safe string constraint assertions
Date: Wed, 8 Jan 2020 16:35:22 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B9E59389@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <B003EFCC-6748-4B2D-93F5-D438530D6112@protonmail.com>

Hi Vitaly,

Thanks for the additional background.  I would like
a couple extra day to review the PCD name and the places
the PCD might potentially be used.

If we find other APIs where ASSERT() behavior is only
valuable during dev/debug to quickly identify misuse 
with trusted data and the API provides predicable
return behavior when ASSERT() is disabled, then I would
like to have a pattern we can potentially apply to all 
these APIs across all packages.

Thanks,

Mike

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On
> Behalf Of Vitaly Cheptsov via Groups.Io
> Sent: Monday, January 6, 2020 10:44 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: devel@edk2.groups.io
> Subject: Re: [edk2-devel] [PATCH v3 0/1] Add PCD to
> disable safe string constraint assertions
> 
> Hi Mike,
> 
> Yes, the primary use case is for UEFI Applications. We
> do not want to disable ASSERT’s completely, as
> assertions that make sense, i.e. the ones signalising
> about interface misuse, are helpful for debugging.
> 
> I have already explained in the BZ that basically all
> safe string constraint assertions make no sense for
> handling untrusted data. We find this use case very
> logical, as these functions behave properly with
> assertions disabled and cover all these error
> conditions by the return statuses. In such situation is
> not useful for these functions to assert, as we end up
> inefficiently reimplementing the logic. I would have
> liked the approach of discussing the interfaces
> individually, but I struggle to find any that makes
> sense from this point of view.
> 
> AsciiStrToGuid will ASSERT when the length of the
> passed string is odd. Functions that cannot, ahem,
> parse, for us are pretty much useless.
> AsciiStrCatS will ASSERT when the appended string does
> not fit the buffer. For us this logic makes this
> function pretty much equivalent to deprecated and thus
> unavailable AsciiStrCat, except it is also slower.
> 
> My original suggestion was to remove the assertions
> entirely, but several people here said that they use
> them to verify usage errors when handling trusted data.
> This makes good sense to me, so we suggest to support
> both cases by introducing a PCD in this patch.
> 
> Best wishes,
> Vitaly
> 
> > 6 янв. 2020 г., в 21:28, Kinney, Michael D
> <michael.d.kinney@intel.com> написал(а):
> >
> >
> > Hi Vitaly,
> >
> > Is the use case for UEFI Applications?
> >
> > There is a different mechanism to disable all
> ASSERT()
> > statements  within a UEFI Application.
> >
> > If a component is consuming data from an untrusted
> source,
> > then that component is required to verify the
> untrusted
> > data before passing it to a function that clearly
> documents
> > is input requirements.  If this approach is followed,
> then
> > the BaseLib functions can be used "as is" as long as
> the
> > ASSERT() conditions are verified before calling.
> >
> > If there are some APIs that currently document their
> ASSERT()
> > behavior and we think that ASSERT() behavior is
> incorrect and
> > should be handled by an existing error return value,
> then we
> > should discuss each of those APIs individually.
> >
> > Mike
> >
> >
> >> -----Original Message-----
> >> From: devel@edk2.groups.io <devel@edk2.groups.io> On
> >> Behalf Of Vitaly Cheptsov via Groups.Io
> >> Sent: Friday, January 3, 2020 9:13 AM
> >> To: devel@edk2.groups.io
> >> Subject: [edk2-devel] [PATCH v3 0/1] Add PCD to
> disable
> >> safe string constraint assertions
> >>
> >> REF:
> >> https://bugzilla.tianocore.org/show_bug.cgi?id=2054
> >>
> >> Requesting for merge in edk2-stable202002.
> >>
> >> Changes since V1:
> >> - Enable assertions by default to preserve the
> original
> >> behaviour
> >> - Fix bugzilla reference link
> >> - Update documentation in BaseLib.h
> >>
> >> Vitaly Cheptsov (1):
> >>  MdePkg: Add PCD to disable safe string constraint
> >> assertions
> >>
> >> MdePkg/MdePkg.dec                   |  6 ++
> >> MdePkg/Library/BaseLib/BaseLib.inf  | 11 +--
> >> MdePkg/Include/Library/BaseLib.h    | 74
> >> +++++++++++++-------
> >> MdePkg/Library/BaseLib/SafeString.c |  4 +-
> >> MdePkg/MdePkg.uni                   |  6 ++
> >> 5 files changed, 71 insertions(+), 30 deletions(-)
> >>
> >> --
> >> 2.21.0 (Apple Git-122.2)
> >>
> >>
> >> -=-=-=-=-=-=
> >> Groups.io Links: You receive all messages sent to
> this
> >> group.
> >>
> >> View/Reply Online (#52837):
> >> https://edk2.groups.io/g/devel/message/52837
> >> Mute This Topic:
> https://groups.io/mt/69401948/1643496
> >> Group Owner: devel+owner@edk2.groups.io
> >> Unsubscribe: https://edk2.groups.io/g/devel/unsub
> >> [michael.d.kinney@intel.com]
> >> -=-=-=-=-=-=
> >
> 
> 
> 


  parent reply	other threads:[~2020-01-08 16:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 17:12 [PATCH v3 0/1] Add PCD to disable safe string constraint assertions Vitaly Cheptsov
2020-01-03 17:12 ` [PATCH v3 1/1] MdePkg: " Vitaly Cheptsov
2020-01-06 18:28 ` [edk2-devel] [PATCH v3 0/1] " Michael D Kinney
2020-01-06 18:43   ` Vitaly Cheptsov
2020-01-06 22:54     ` Sean
2020-01-08 16:35     ` Michael D Kinney [this message]
2020-01-27  9:47       ` Vitaly Cheptsov
2020-02-10 11:12         ` Vitaly Cheptsov
2020-02-14 11:54           ` Vitaly Cheptsov
2020-02-14 17:00             ` Michael D Kinney
2020-02-14 17:37               ` Vitaly Cheptsov
2020-02-14 22:50                 ` Michael D Kinney
2020-02-14 23:04                   ` Vitaly Cheptsov
2020-02-15  0:02                   ` Andrew Fish
2020-02-15  3:31                     ` Vitaly Cheptsov
2020-02-15  6:26                       ` Andrew Fish
2020-02-15 11:53                         ` Vitaly Cheptsov
2020-02-15 12:02                           ` Vitaly Cheptsov
2020-02-15 19:38                         ` Michael D Kinney
2020-02-16 21:25                           ` Andrew Fish
2020-02-17  6:55                             ` Vitaly Cheptsov
2020-02-17  8:26                             ` Marvin Häuser
2020-02-19 23:55                               ` Andrew Fish
2020-02-20 10:18                                 ` Marvin Häuser
2020-03-03 19:38                                   ` Marvin Häuser
2020-03-04  0:19                                     ` Liming Gao
2020-03-03 20:27                                   ` Andrew Fish
     [not found]                             ` <15F4232304E080CF.5373@groups.io>
2020-02-17  9:36                               ` Marvin Häuser

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-list 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=E92EE9817A31E24EB0585FDF735412F5B9E59389@ORSMSX113.amr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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