1. 18 Aug, 2016 3 commits
    • Josh Bleecher Snyder's avatar
      cmd/vet: allow any printf verb with any interface · 11e93aa2
      Josh Bleecher Snyder authored
      fmt treats interfaces as being transparent.
      As a result, we cannot say with confidence
      that any particular verb is wrong.
      
      This fixes the following vet false positives
      in the standard library:
      
      database/sql/sql_test.go:210: arg dep for printf verb %p of wrong type: sql.finalCloser
      fmt/fmt_test.go:1663: arg nil for printf verb %s of wrong type: untyped nil
      go/ast/commentmap.go:328: arg node for printf verb %p of wrong type: ast.Node
      net/http/transport_test.go:120: arg c for printf verb %p of wrong type: net.Conn
      net/http/httptest/server.go:198: arg c for printf verb %p of wrong type: net.Conn
      net/http/httputil/dump_test.go:258: arg body for printf verb %p of wrong type: io.Reader
      reflect/set_test.go:81: arg x for printf verb %p of wrong type: io.Writer
      reflect/set_test.go:141: arg bb for printf verb %p of wrong type: io.Reader
      
      Updates #11041
      Updates #16314
      
      Change-Id: I76df01abb3c34a97b6960f551bed9c1c91377cfc
      Reviewed-on: https://go-review.googlesource.com/27127
      Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarRob Pike <r@golang.org>
      11e93aa2
    • Alex Brainman's avatar
      debug/pe: revert CL 22720 · 0ece9c4b
      Alex Brainman authored
      CL 22720 hid all recently added functionality for go1.7.
      Make everything exported again, so we could use it now.
      
      Updates #15345
      
      Change-Id: Id8ccba7199422b554407ec14c343d2c28fbb8f72
      Reviewed-on: https://go-review.googlesource.com/27212
      Run-TryBot: Alex Brainman <alex.brainman@gmail.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarDavid Crawshaw <crawshaw@golang.org>
      0ece9c4b
    • Adam Langley's avatar
      crypto/x509: support PSS signatures. · e41b0e2b
      Adam Langley authored
      Although the term “RSA” is almost synonymous with PKCS#1 v1.5, that
      standard is quite flawed, cryptographically speaking. Bellare and
      Rogaway fixed PKCS#1 v1.5 with OAEP (for encryption) and PSS (for
      signatures) but they only see a fraction of the use of v1.5.
      
      This change adds support for creating and verifying X.509 certificates
      that use PSS signatures. Sadly, every possible dimension of flexibility
      seems to have been reflected in the integration of X.509 and PSS
      resulting in a huge amount of excess complexity. This change only
      supports one “sane” configuration for each of SHA-{256, 384, 512}.
      Hopefully this is sufficient because it saves a lot of complexity in the
      code.
      
      Although X.509 certificates with PSS signatures are rare, I'm inclined
      to look favourably on them because they are sufficiently superior.
      
      Fixes #15958.
      
      Change-Id: I7282e0b68ad0177209f8b2add473b94aa5224c07
      Reviewed-on: https://go-review.googlesource.com/24743
      Run-TryBot: Adam Langley <agl@golang.org>
      Reviewed-by: 's avatarBrad Fitzpatrick <bradfitz@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      e41b0e2b
  2. 17 Aug, 2016 29 commits
  3. 16 Aug, 2016 8 commits