Filippo Valsorda
37a17fe027
AnyOverlap and InexactOverlap implement checks for the aliasing requirements defined by the crypto/cipher interfaces. Apply them to all implementations as the actual requirement could be architecture-dependent and user code should not rely on undefined behavior. Updates golang/go#21624 Change-Id: I465de02fb3fec4e0c6f1fdee1ef6ae7ed5abff10 Reviewed-on: https://go-review.googlesource.com/112236 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
31 lines
1.2 KiB
Go
31 lines
1.2 KiB
Go
// Copyright 2018 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// Package subtle implements functions that are often useful in cryptographic
|
|
// code but require careful thought to use correctly.
|
|
package subtle // import "golang.org/x/crypto/internal/subtle"
|
|
|
|
import "unsafe"
|
|
|
|
// AnyOverlap reports whether x and y share memory at any (not necessarily
|
|
// corresponding) index. The memory beyond the slice length is ignored.
|
|
func AnyOverlap(x, y []byte) bool {
|
|
return len(x) > 0 && len(y) > 0 &&
|
|
uintptr(unsafe.Pointer(&x[0])) <= uintptr(unsafe.Pointer(&y[len(y)-1])) &&
|
|
uintptr(unsafe.Pointer(&y[0])) <= uintptr(unsafe.Pointer(&x[len(x)-1]))
|
|
}
|
|
|
|
// InexactOverlap reports whether x and y share memory at any non-corresponding
|
|
// index. The memory beyond the slice length is ignored. Note that x and y can
|
|
// have different lengths and still not have any inexact overlap.
|
|
//
|
|
// InexactOverlap can be used to implement the requirements of the crypto/cipher
|
|
// AEAD, Block, BlockMode and Stream interfaces.
|
|
func InexactOverlap(x, y []byte) bool {
|
|
if len(x) == 0 || len(y) == 0 || &x[0] == &y[0] {
|
|
return false
|
|
}
|
|
return AnyOverlap(x, y)
|
|
}
|