golang-github-gorilla-securecookie 1.1.2-1 source package in Ubuntu
Changelog
golang-github-gorilla-securecookie (1.1.2-1) unstable; urgency=medium
* New upstream version 1.1.2
* Reorder fields in debian/control and debian/copyright
* Change Section from devel to golang
* Bump debhelper build-dependency to debhelper-compat (= 13)"
* Use dh-sequence-golang instead of dh-golang and --with=golang
* Invoke dh with --builddirectory=_build
* Add build-dependency on golang-github-google-gofuzz-dev
and set golang-any (>= 2:1.20~) as per go.mod
* Bump Standards-Version to 4.6.2 (no change)
* Drop -dev package’s unused dependency on ${shlibs:Depends}
* Remove manual "rm -r usr/bin" in override_dh_auto_install
as "dh_auto_install -- --no-binaries" does the job already
-- Anthony Fok <email address hidden> Fri, 08 Dec 2023 16:07:33 -0700
Upload details
- Uploaded by:
- Debian Go Packaging Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Go Packaging Team
- Architectures:
- all
- Section:
- golang
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Oracular | release | universe | misc | |
| Noble | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| golang-github-gorilla-securecookie_1.1.2-1.dsc | 2.3 KiB | d64e326c23a9cd3eef46a4c2ee40f4a7e552e7db61c82a8bfbda42a40f7c5328 |
| golang-github-gorilla-securecookie_1.1.2.orig.tar.gz | 11.9 KiB | 6a95562e0bf0b29033bfe75a55a28ca547d76b5472c0865f38ba9d8eb44c2ddf |
| golang-github-gorilla-securecookie_1.1.2-1.debian.tar.xz | 3.3 KiB | 4bbdb323c02435aa8b9d4982c6a316cd7d43cb976bc9e3ac0a8b4326e5ee9b89 |
Available diffs
- diff from 1.1.1-2 to 1.1.2-1 (36.7 KiB)
No changes file available.
Binary packages built by this source
- golang-github-gorilla-securecookie-dev: provides authenticated and encrypted cookie values
This package provides methods for encoding and decoding authenticated
cookie values for Go web applications. These values optionally be
encrypted.
.
Secure cookies are protected from forgery because their values are
validated using HMAC. When encrypted, the content is also kept private.
.
It is still recommended that sensitive data not be stored in cookies,
and that HTTPS be used to prevent cookie replay attacks.
