220 40405 <1aa6c911-439e-4469-806d-bdc39989ad40@isocpp.org> article Path: news.gmane.org!.POSTED!not-for-mail From: =?UTF-8?Q?Micha=C5=82_Gawron?= Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: more security concerns Date: Tue, 9 Oct 2018 00:25:48 -0700 (PDT) Lines: 156 Approved: news@gmane.org Message-ID: <1aa6c911-439e-4469-806d-bdc39989ad40@isocpp.org> References: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1965_1321297405.1539069948469" X-Trace: blaine.gmane.org 1539069825 10229 195.159.176.226 (9 Oct 2018 07:23:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 9 Oct 2018 07:23:45 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCRMZK6MQMOBB7NP6HOQKGQEMV3NS6Y@isocpp.org Tue Oct 09 09:23:41 2018 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yb1-f198.google.com ([209.85.219.198]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9mMm-0002Xd-Br for gclcip-std-proposals@m.gmane.org; Tue, 09 Oct 2018 09:23:40 +0200 Original-Received: by mail-yb1-f198.google.com with SMTP id s190-v6sf179373ybf.8 for ; Tue, 09 Oct 2018 00:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=pIB71DSvGHxxBuVmv47j1cCdLrhiN3CV777JrHMgIZ0=; b=aiAunvFmzUnEiO2up+hZS4LhsqDip+Oh0emnZ3Mv1gHaE5AmN158R1v5C+NzL0t0PI bni1EL9yj4UOBWzkInmWCXwzY6K/MCQmVJmZbYkPzgXF5/FHCwKa7pEtVr08PxxB9aLj u0OJiK87gmA9o0PDqUciT7H17lCpEzP22+MtHeVd3FPMQwajQjRx0qP9BlZGAfQ0C1bR 9tU2x+ARweqKREP9pWse+UiSLt9b8mIqZXzTOKNo+9/krFFam3lv9ijvsEh0iPl3lREC 9hFsNQW1YG+Dhoof0yWHtU1k3fAHacfBfpZgYQZaWAfWEFciNsmmB4L33Es+ALuW6Uru 6jnw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=pIB71DSvGHxxBuVmv47j1cCdLrhiN3CV777JrHMgIZ0=; b=b/XU+ELwkuDSW9yIrGUvaL1xE7pRhJRiaga6CjLjYWst3Nh2C60LY85Id0nqv8tz5K p8bQ9gdVXdZo8S9L2H8KpqnLa+EhbJLe2K5RjRk38S9wnb1toLApMq8gKjuulWi2U7HC hgW0XSla/ZwpdfN8o8QXojwL96Y82qz29S/v3p+ul46oDxof4DvJkH64PsBbejU4q9Kl EkOvCoZgDHhTgw90JpXbXjLBiYEap/MgSRg2MwgsO4olixLa5vt6TW5kiz7QbBYVDtcm 4XV9aYnny1nlk/tZ7B3zzgGo2XrHnhDsNV9/xs+PgD18aQv3mebbHkJ30dKXRMKWLJvV isTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=pIB71DSvGHxxBuVmv47j1cCdLrhiN3CV777JrHMgIZ0=; b=LltiERpEmUdFwqjioYNHAvJ7ZoBCgmzRZN4Byb8Lx5oTEHU3BXSjdgCkGOTsKoRCWU kNgExjHMUSsRdHJZ4RuJe6JZofBybYK/iFlvzYND24gvQAkMAtoZMSqHYizIaTdStLTF PFuZRishIWXV7JlYpYi1Rm+xfVrKOqM7IE6kjIcQPh/I5PTt6keYP97pLv5e+kDjTQyR c+HFByJ4qdPnAs4WMB37KnvYOhlCeNhRFhTIOHtP0ZduNrwJYpbrzxM9/iL/iJgIO6f9 yNnL6BWZB5iSJtSLnh2RdNNZ8uph2R15g4wt+4CtClRX3FX0+ZeI0fDdefFnGExULDkF fogQ== X-Gm-Message-State: ABuFfogIB3JChrSXUiDYHYs9IpVozaDEe5iiUIFBXDFxdCHDgBuPiRr9 1Suj5esoGyyT+mJLpJ5lScGqww== X-Google-Smtp-Source: ACcGV600xtEuLpVA25q3B+kPbmBqCDZIFpYvwfCZW2LimF8gU8oHTb9kN9U5bSR6R0RB6cYRG0mJ9w== X-Received: by 2002:a25:8143:: with SMTP id j3-v6mr13585430ybm.70.1539069950633; Tue, 09 Oct 2018 00:25:50 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 2002:a25:512:: with SMTP id 18-v6ls689092ybf.2.gmail; Tue, 09 Oct 2018 00:25:49 -0700 (PDT) X-Received: by 2002:a25:d90a:: with SMTP id q10-v6mr325040ybg.0.1539069949131; Tue, 09 Oct 2018 00:25:49 -0700 (PDT) In-Reply-To: X-Original-Sender: mcvsama@gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Spam-Checked-In-Group: std-proposals@isocpp.org X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:40405 Archived-At: ------=_Part_1965_1321297405.1539069948469 Content-Type: multipart/alternative; boundary="----=_Part_1966_2029531398.1539069948470" ------=_Part_1966_2029531398.1539069948470 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Wouldn't something like this as a std:: function work? template inline add_volatile& make_volatile (T& t) { return t; } Then later: int a =3D 5; =E2=80=A6 make_volatile (a) =3D 0; std::best_regards(); On Tuesday, October 9, 2018 at 9:02:41 AM UTC+2, Miguel Ojeda wrote: > > Hi Daniel,=20 > > For this specific case (data that must be kept as secret as reasonably=20 > possible, like passwords, secrets, keying data...), I am proposing=20 > `secure_clear` (a memset_s-like function and function template) and=20 > `secure_val` (a new class template) in P1315 for the next mailing.=20 > Meanwhile that is out, please take a look at:=20 > > https://ojeda.io/cpp/secure_val=20 > > As long as your proposal allows to write functionality like=20 > `secure_clear` and `secure_val` as portably and easily as possible, it=20 > seems useful!=20 > > Cheers,=20 > Miguel=20 > --=20 You received this message because you are subscribed to the Google Groups "= ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. To view this discussion on the web visit https://groups.google.com/a/isocpp= ..org/d/msgid/std-proposals/1aa6c911-439e-4469-806d-bdc39989ad40%40isocpp.or= g. ------=_Part_1966_2029531398.1539069948470 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Wouldn't something like this as a std:: function work?=

temp= late<class= T>
=C2=A0 =C2=A0 inline add_volatile<T>&
=C2=A0 =C2=A0 make_volatile (T& t)
=C2=A0 =C2=A0 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 return t;
=C2=A0 =C2=A0 }

Then la= ter:

int a =3D 5;
=E2=80=A6
make_volatile (a) =3D 0;


std::best_regards();

On Tuesday, Oc= tober 9, 2018 at 9:02:41 AM UTC+2, Miguel Ojeda wrote:
Hi Daniel,

For this specific case (data that must be kept as secret as reasonably
possible, like passwords, secrets, keying data...), I am proposing
`secure_clear` (a memset_s-like function and function template) and
`secure_val` (a new class template) in P1315 for the next mailing.
Meanwhile that is out, please take a look at:

=C2=A0 https://ojeda.io/cpp/secure_val

As long as your proposal allows to write functionality like
`secure_clear` and `secure_val` as portably and easily as possible, it
seems useful!

Cheers,
Miguel

--
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.= com/a/isocpp.org/d/msgid/std-proposals/1aa6c911-439e-4469-806d-bdc39989ad40= %40isocpp.org.
------=_Part_1966_2029531398.1539069948470-- ------=_Part_1965_1321297405.1539069948469-- .