Skip to content

Releases: awnumar/memguard

v0.16.3

27 Jun 10:03
42a26f9
Compare
Choose a tag to compare

It is now possible to construct a LockedBuffer object directly from an io.Reader.

Added

func NewBufferFromReader(r io.Reader, size int) *LockedBuffer { /* ... */ }
func NewBufferFromReaderUntil(r io.Reader, delim byte) *LockedBuffer { /* ... */ }

Reading from standard input is now trivially:

b := NewBufferFromReaderUntil(os.Stdin, '\n')

v0.16.2

17 Jun 19:49
4b075c2
Compare
Choose a tag to compare

v0.16.1

17 Jun 13:53
7df3159
Compare
Choose a tag to compare

Patch a bug in the computation of the canary size. Related: #86

v0.16.0

03 Jun 15:32
0799fe7
Compare
Choose a tag to compare

This release includes breaking changes.

The highlight of this version is the ability to store sensitive information in encrypted form, decrypting it when and where it is immediately needed. There are lots of other changes introduced in this version. See the documentation for more details: https://godoc.org/github.com/awnumar/memguard

v0.15.1

11 May 01:16
Compare
Choose a tag to compare

Replaced MADV_DONTDUMP with MADV_NOCORE on FreeBSD systems. Related issue: #82

v0.15.0

28 Apr 15:32
f431f51
Compare
Choose a tag to compare
  • Re-add the WipeBytes function with a warning of its potential limitations added to its documentation.

v0.14.0

02 Apr 22:07
2c77d7d
Compare
Choose a tag to compare

This release adds support for extra datatypes, i.e. alternative ways of representing the data stored in a LockedBuffer. This is accomplished via the following new methods:

func (b *LockedBuffer) Uint8() ([]uint8, error)
func (b *LockedBuffer) Uint16() ([]uint16, error)
func (b *LockedBuffer) Uint32() ([]uint32, error)
func (b *LockedBuffer) Uint64() ([]uint64, error)

func (b *LockedBuffer) Int8() ([]int8, error)
func (b *LockedBuffer) Int16() ([]int16, error)
func (b *LockedBuffer) Int32() ([]int32, error)
func (b *LockedBuffer) Int64() ([]int64, error)

v0.13.3

12 Feb 19:34
5d9ab46
Compare
Choose a tag to compare
  • We now use the MAP_NOCORE flag when mmaping on FreeBSD.
  • When allocating memory, we fill the entire region with 0xdb bytes to allow for easier debugging of issues related to uninitialized data.
  • Switched to using golang/dep for dependency management.

v0.13.2

18 Nov 03:23
b482b0c
Compare
Choose a tag to compare
  • Fix issue raised in #45 by handling OpenBSD syscalls explicitly.
  • Use MAP_PRIVATE on Unixesque systems.

v0.13.1

23 Oct 12:46
Compare
Choose a tag to compare
  • Use internal methods to avoid mutex conflicts in the future.
  • Encourage vendoring dependencies. Recommend Glide.