Release v0.4.9

Changed

• Dependencies
  • built using Go 1.15.5
    • Statically linked
    • Windows
      • x86
      • x64
    • Linux
      • x86
      • x64
  • atc0005/go-ezproxy
    • v0.1.6 to v0.1.7

Fixed

• Fix CHANGELOG entries from v0.4.8 release
• Correct the version of Go noted for v0.4.8 release

References

• See the v0.4.9 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.8

Added

• Add support for limiting payloads to specific IPs

Changed

• Statically linked binary release

  • Built using Go 1.15.4
  • Windows
    • x86
    • x64
  • Linux
    • x86
    • x64

• Dependencies

  • actions/checkout
    • v2.3.3 to v2.3.4

Note: Windows builds are provided, but have not been tested. The current
developer does not have access to a Windows + EZproxy test environment. Please
open an issue to share your
experiences deploying tools from this project on a Windows EZproxy server.

References

• See the v0.4.8 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.7

Added

• Binary release
  • Built using Go 1.15.2
  • Statically linked (GH-193)
  • Windows
    • x86
    • x64
  • Linux
    • x86
    • x64

Note: Windows builds are provided, but have not been tested. The current
developer does not have access to a Windows + EZproxy test environment. Please
open an issue to share your
experiences deploying tools from this project on a Windows EZproxy server.

Changed

• Add -trimpath build flag
• Restore explicit exit code handling (GH-191)

Fixed

• Makefile build options do not generate static binaries (GH-189)

References

• See the v0.4.7 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.6

Added

• Binary release
  • Built using Go 1.15.2
  • Windows
    • x86
    • x64
  • Linux
    • x86
    • x64

Note: Windows builds are provided, but have not been tested. The current
developer does not have access to a Windows + EZproxy test environment. Please
open an issue to share your
experiences deploying tools from this project on a Windows EZproxy server.

Changed

• Emit version number as part of startup message

• Move subpackages into internal directory

• Dependencies

  • upgrade pelletier/go-toml
    • v1.8.0 to v1.8.1
  • upgrade actions/checkout
    • v2.3.2 to v2.3.3
  • upgrade actions/setup-node
    • v2.1.1 to v2.1.2

Fixed

• Misc linting errors raised by latest gocritic release included with
  golangci-lint v1.31.0

• Flag for setting desired log output does not appear to work

• Documentation mistake: log-output CLI flag incorrectly listed as log-out

• Makefile generates checksums with qualified path

• Debug messages are emitted before logging settings are applied which would
  (potentially) allow them to be emitted

References

• See the v0.4.6 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.5

Changed

• Dependencies
  • upgrade go.mod Go version
    • 1.13 to 1.14
  • upgrade atc0005/go-ezproxy
    • v0.1.5 to v0.1.6
  • upgrade atc0005/go-teams-notify
    • v1.3.1-0.20200419155834-55cca556e726 to v2.3.0
      • NOTE: This is a significant change reflecting a merge of required
        functionality from the atc0005/send2teams project to the
        atc0005/go-teams-notify project
  • upgrade Showmax/go-fqdn
    • v0.0.0-20180501083314-6f60894d629f to v1.0.0
  • upgrade apex/log
    • v1.7.0 to v1.9.0
  • upgrade actions/checkout
    • v2.3.1 to v2.3.2
  • upgrade atc0005/send2teams
    • v0.4.5 to v0.4.6
      • since removed

Fixed

• Add missing filename reference in error message

References

• See the v0.4.5 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.4

Added

• Docker-based GitHub Actions Workflows

  • Replace native GitHub Actions with containers created and managed through
    the atc0005/go-ci project.

  • New, primary workflow

    • with parallel linting, testing and building tasks
    • with three Go environments
      • "old stable" - currently Go 1.13.14
      • "stable" - currently Go 1.14.6
      • "unstable" - currently Go 1.15rc1
    • Makefile is not used in this workflow
    • staticcheck linting using latest stable version provided by the
      atc0005/go-ci containers

  • Separate Makefile-based linting and building workflow

    • intended to help ensure that local Makefile-based builds that are
      referenced in project README files continue to work as advertised until
      a better local tool can be discovered/explored further
    • use golang:latest container to allow for Makefile-based linting
      tooling installation testing since the atc0005/go-ci project provides
      containers with those tools already pre-installed
      • linting tasks use container-provided golangci-lint config file
        except for the Makefile-driven linting task which continues to use
        the repo-provided copy of the golangci-lint configuration file

  • Add Quick Validation workflow

    • run on every push, everything else on pull request updates
    • linting via golangci-lint only
    • testing
    • no builds

Changed

• README

  • Link badges to applicable GitHub Actions workflows results

• Linting

  • Local
    • Makefile
      • install latest stable golangci-lint binary instead of using a fixed
        version
  • CI
    • remove repo-provided copy of golangci-lint config file at start of
      linting task in order to force use of Docker container-provided config
      file

• Dependencies

  • upgrade apex/log
    • v1.6.0 to v1.7.0

Fixed

• gosec linting errors

  • G404: Use of weak random number generator (math/rand instead of
    crypto/rand)
    • fixed this, though our use of math/rand wasn't for cryptographic
      purposes and was likely OK as-is
  • G304: Potential file inclusion via variable
    • marked this as ignored due to the variable being one we are
      intentionally allowing the sysadmin to set

• Lock MailDev container to specific, proven stable version used previously
  in demos

  • intent: reduce "gotchas" in future demo sessions if a drastically
    different/newer version were to get pulled in while resetting the demo
    environment

• Email notifications do not include Session Termination Results section

  • this was included with existing Microsoft Teams notifications, but not
    email notifications

References

• See the v0.4.4 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.3

Changed

• Explicitly note notifications state

Fixed

• Email templates: MISSING VALUE - Please file a bug report!; use generated
  email summary instead of Record.Note

References

• See the v0.4.3 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.2

Changed

• Alert sender: Replace "received by" phrasing in file templates

• Dependencies

  • updated atc0005/go-ezproxy
    • v0.1.4 to v0.1.5

Fixed

• Documentation

  • Further work on EZproxy purpose
  • Add further information on integration with EZproxy, Splunk

• Reporting (monitoring) system referred to with "received by" phrasing
  instead of "received from"

• Deferred file close operations report "file already closed" error messages

  • note: the atc0005/go-ezproxy v0.1.5 release includes the same type of
    changes

References

• See the v0.4.2 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.1

Changed

• Dependencies

  • updated atc0005/go-ezproxy
    • v0.1.3 to v0.1.4
  • updated actions/setup-go
    • v2.1.0 to v2.1.1
  • updated actions/setup-node
    • v2.1.0 to v2.1.1

• Linting

  • golangci-lint: Disable default exclusions

• Logging

  • Update internal/fileutils.HasLine function to emit name
  • Update files.appendToFile function to emit func name
  • Update NewConfig function to emit name

Fixed

• Documentation

  • Add additional lead-in for docs/ezproxy.md to (hopefully) better explain
    what EZproxy is
  • Update main README to make majority of "EZproxy" references point to the
    updated docs/ezproxy.md doc

• Linting

  • Use filepath.Clean for all os.Open calls
    • even though this application is intended for use by sysadmins (who have
      no cause to try and exploit the system), it's better to go ahead and
      guard against potential exposure introduced by using externally-provided
      (e.g., config file or flags) filenames by sanitizing the paths
    • note: the atc0005/go-ezproxy v0.1.4 release includes the same type
      of changes
  • errcheck: Explicitly check file close return values
  • errcheck: Explicitly check writer flush return value

References

• See the v0.4.1 milestone for the issues associated with this release.
• See our CHANGELOG for more information.

Release v0.4.0

Added

• Email notifications
  • initial support

Changed

• CI/Linting

  • re-enable separate golint step to work around what appears to be a bug
    in golangci-lint (golangci/golangci-lint#1249)

• Dependencies

  • upgrade apex/log
    • v1.4.0 to v1.6.0
  • upgrade atc0005/send2teams
    • v0.4.4 to v0.4.5

• Demo content

  • upgrade Go version from v1.14.5 to v1.14.6
  • minor tweaks to output emitted by reset script

• Documentation

  • Cover new flags, environment variables and config file settings
  • Misc fixes for existing rate limit, number of retries and retry delay
  • Refresh existing setup/deploy steps to briefly cover email configuration

• Configuration

  • TOML config file
    • extended with new settings
    • rename some settings in an effort to better communicate intent

Fixed

• golint reporting several "should have comment or be unexported" linting
  issues

• in-place modification of client/alert request headers for Teams message
  formatting leads to unintentional "spillover" to email notifications

References

• See the v0.4.0 milestone for the issues associated with this release.
• See our CHANGELOG for more information.