[openssh-commits] [openssh] branch master updated (ae9c0d4 -> df82072)

Mon Jun 6 11:36:55 AEST 2016

This is an automated email from the git hooks/post-receive script.

dtucker pushed a change to branch master
in repository openssh.

      from  ae9c0d4   Update vis.h and vis.c from OpenBSD.
       new  a0cb777   upstream commit
       new  82f24c3   upstream commit
       new  7ec4946   upstream commit
       new  8c02e36   upstream commit
       new  0e059cd   upstream commit
       new  ac284a3   upstream commit
       new  cd9e1ea   upstream commit
       new  6c17171   upstream commit
       new  05c6574   Fix utf->utf8 typo.
       new  df82072   Add compat bits to utf8.c.

The 10 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.

Detailed log of new commits:

commit df820722e40309c9b3f360ea4ed47a584ed74333
Author: Darren Tucker <dtucker at zip.com.au>
Date:   Mon Jun 6 11:36:13 2016 +1000

    Add compat bits to utf8.c.

commit 05c6574652571becfe9d924226c967a3f4b3f879
Author: Darren Tucker <dtucker at zip.com.au>
Date:   Mon Jun 6 11:33:43 2016 +1000

    Fix utf->utf8 typo.

commit 6c1717190b4d5ddd729cd9e24e8ed71ed4f087ce
Author: schwarze at openbsd.org <schwarze at openbsd.org>
Date:   Mon May 30 18:34:41 2016 +0000

    upstream commit

    Backout rev. 1.43 for now.

    The function update_progress_meter() calls refresh_progress_meter()
    which calls snmprintf() which calls malloc(); but update_progress_meter()
    acts as the SIGALRM signal handler.

    "malloc(): error: recursive call" reported by sobrado at .

    Upstream-ID: aaae57989431e5239c101f8310f74ccc83aeb93e

commit cd9e1eabeb4137182200035ab6fa4522f8d24044
Author: schwarze at openbsd.org <schwarze at openbsd.org>
Date:   Mon May 30 12:57:21 2016 +0000

    upstream commit

    Even when only writing an unescaped character, the dst
     buffer may need to grow, or it would be overrun; issue found by tb@ with
     malloc.conf(5) 'C'.

    While here, reserve an additional byte for the terminating NUL
    up front such that we don't have to realloc() later just for that.

    OK tb@

    Upstream-ID: 30ebcc0c097c4571b16f0a78b44969f170db0cff

commit ac284a355f8065eaef2a16f446f3c44cdd17371d
Author: schwarze at openbsd.org <schwarze at openbsd.org>
Date:   Mon May 30 12:05:56 2016 +0000

    upstream commit

    Fix two rare edge cases: 1. If vasprintf() returns < 0,
     do not access a NULL pointer in snmprintf(), and do not free() the pointer
     returned from vasprintf() because on some systems other than OpenBSD, it
     might be a bogus pointer. 2. If vasprintf() returns == 0, return 0 and ""
     rather than -1 and NULL.

    Besides, free(dst) is pointless after failure (not a bug).

    One half OK martijn@, the other half OK deraadt@;
    committing quickly before people get hurt.

    Upstream-ID: b7bcd2e82fc168a8eff94e41f5db336ed986fed0

commit 0e059cdf5fd86297546c63fa8607c24059118832
Author: schwarze at openbsd.org <schwarze at openbsd.org>
Date:   Wed May 25 23:48:45 2016 +0000

    upstream commit

    To prevent screwing up terminal settings when printing to
     the terminal, for ASCII and UTF-8, escape bytes not forming characters and
     bytes forming non-printable characters with vis(3) VIS_OCTAL. For other
     character sets, abort printing of the current string in these cases.  In
     particular, * let scp(1) respect the local user's LC_CTYPE locale(1); *
     sanitize data received from the remote host; * sanitize filenames, usernames,
     and similar data even locally; * take character display widths into account
     for the progressmeter.

    This is believed to be sufficient to keep the local terminal safe
    on OpenBSD, but bad things can still happen on other systems with
    state-dependent locales because many places in the code print
    unencoded ASCII characters into the output stream.

    Using feedback from djm@ and martijn@,
    various aspects discussed with many others.

    deraadt@ says it should go in now, i probably already hesitated too long

    Upstream-ID: e66afbc94ee396ddcaffd433b9a3b80f387647e0

commit 8c02e3639acefe1e447e293dbe23a0917abd3734
Author: dtucker at openbsd.org <dtucker at openbsd.org>
Date:   Tue May 24 04:43:45 2016 +0000

    upstream commit

    KNF compression proposal and simplify the client side a
     little.  ok djm@

    Upstream-ID: aa814b694efe9e5af8a26e4c80a05526ae6d6605

commit 7ec4946fb686813eb5f8c57397e465f5485159f4
Author: dtucker at openbsd.org <dtucker at openbsd.org>
Date:   Tue May 24 02:31:57 2016 +0000

    upstream commit

    Back out 'plug memleak'.

    Upstream-ID: 4faacdde136c24a961e24538de373660f869dbc0

commit 82f24c3ddc52053aeb7beb3332fa94c92014b0c5
Author: djm at openbsd.org <djm at openbsd.org>
Date:   Mon May 23 23:30:50 2016 +0000

    upstream commit

    prefer agent-hosted keys to keys from PKCS#11; ok markus

    Upstream-ID: 7417f7653d58d6306d9f8c08d0263d050e2fd8f4

commit a0cb7778fbc9b43458f7072eb68dd858766384d1
Author: dtucker at openbsd.org <dtucker at openbsd.org>
Date:   Mon May 23 00:17:27 2016 +0000

    upstream commit

    Plug mem leak in filter_proposal.  ok djm@

    Upstream-ID: bf968da7cfcea2a41902832e7d548356a4e2af34

Summary of changes:
 Makefile.in                                   |   2 +-
 compat.c                                      |   2 +-
 progressmeter.c                               |   2 +-
 scp.c                                         |  45 ++--
 sftp-client.c                                 |   9 +-
 sftp.c                                        |  46 +++--
 sshconnect2.c                                 |  58 +++---
 sshd.c                                        |   7 +-
 utf8.c                                        | 286 ++++++++++++++++++++++++++
 openbsd-compat/regress/strduptest.c => utf8.h |  39 +---
 10 files changed, 388 insertions(+), 108 deletions(-)
 create mode 100644 utf8.c
 copy openbsd-compat/regress/strduptest.c => utf8.h (62%)

-- 
To stop receiving notification emails like this one, please contact
djm at mindrot.org.