Package: azure-kms-pkcs11
Version: 0.0.0-3
Architecture: amd64
Maintainer: Jeremi Piotrowski <TODO>
Installed-Size: 1054
Depends: libc6 (>= 2.34), libcurl4 (>= 7.18.2), libgcc-s1 (>= 3.3.1), libjson-c5 (>= 0.15), libssl1.1 (>= 1.1.1), libstdc++6 (>= 11)
Filename: ./amd64/azure-kms-pkcs11_0.0.0-3_amd64.deb
Size: 341014
MD5sum: 8ab8ca6cfe90ad9871732bf47e674ee8
SHA1: 0de02bd08ac64a9298eb0070f8f2c6787b98caae
SHA256: 4de155e2d5d8e5665e3bc61e7431f7b0d0ffdb08ba5f22467089aa415b4ec924
Section: misc
Priority: extra

Package: azure-sdk-for-cpp
Version: 0.0.0-4
Architecture: amd64
Maintainer: Jeremi Piotrowski <TODO>
Installed-Size: 7
Filename: ./amd64/azure-sdk-for-cpp_0.0.0-4_amd64.deb
Size: 978
MD5sum: 148729fdbac8de2f94e7885132f11963
SHA1: 5303515afb8bf068e382d6ce20c11296d5286b6c
SHA256: 502b994ea1297487f1ccb960ad6ac78686404acbe2959751d17a0e2170491cb1
Section: misc
Priority: extra
Description: azure-sdk-for-cpp - libraries
 This package contains the shared libraries for the azure-sdk-for-cpp project.

Package: azure-sdk-for-cpp-dev
Source: azure-sdk-for-cpp
Version: 0.0.0-4
Architecture: amd64
Maintainer: Jeremi Piotrowski <TODO>
Installed-Size: 106892
Depends: azure-sdk-for-cpp (= 0.0.0-4), libcurl4-openssl-dev, libssl-dev, libxml2-dev
Filename: ./amd64/azure-sdk-for-cpp-dev_0.0.0-4_amd64.deb
Size: 23348712
MD5sum: d9012c1541618edb6a6be52abb54b9d2
SHA1: d32b2b288a06bc2218e3c141f23ec97922a29a9e
SHA256: 28ebb15a4bc60f6b8fc882d2bba78ff69fddafc78597c500ce88f9a247d87137
Section: misc
Priority: extra
Description: azure-sdk-for-cpp - development
 This package contains the development files for the azure-sdk-for-cpp project.

Package: azure-storage-azcopy
Version: 10.14.1-1
Architecture: amd64
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 16724
Depends: libc6 (>= 2.34)
Built-Using: go-md2man-v2 (= 2.0.0+ds-5), golang-1.17 (= 1.17-1ubuntu2), golang-blackfriday-v2 (= 2.0.1-3), golang-github-azure-azure-pipeline-go (= 0.2.2-2), golang-github-azure-azure-storage-blob-go (= 0.13.0+git20210914.2d6cd3e-1), golang-github-azure-azure-storage-file-go (= 0.6.0+git20201111.3c1754d-1), golang-github-azure-go-autorest (= 14.2.0+git20211214.a46566d-1), golang-github-golang-groupcache (= 0.0~git20200121.8c9f03a-1), golang-github-golang-jwt-jwt (= 4.3.0+git20220210.279dd19-1), golang-github-google-uuid (= 1.2.0-1), golang-github-googleapis-gax-go (= 2.0.5-1), golang-github-jeffreyrichter-enum (= 0.0~git20180725.2567042-1), golang-github-mattn-go-ieproxy (= 0.0~git20191113.7c0f686-2), golang-github-minio-minio-go (= 6.0.53-1), golang-github-minio-sha256-simd (= 0.1.1-1), golang-github-mitchellh-go-homedir (= 1.1.0-1), golang-github-pkg-errors (= 0.9.1-1), golang-github-shurcool-sanitized-anchor-name (= 1.0.0-1), golang-github-spf13-cobra (= 1.1.2-1), golang-github-spf13-pflag (= 1.0.5-2), golang-github-wastore-keyctl (= 0.3.1-1), golang-go.crypto (= 1:0.0~git20201221.eec23a3-1), golang-go.opencensus (= 0.22.4-2), golang-golang-x-net (= 1:0.0+git20210119.5f4716e+dfsg-4), golang-golang-x-oauth2 (= 0.0~git20190604.0f29369-2), golang-golang-x-sync (= 0.0~git20210220.036812b-1), golang-golang-x-sys (= 0.0~git20210124.22da62e-1), golang-golang-x-text (= 0.3.6-1), golang-google-api (= 0.28.0-2), golang-google-cloud (= 0.56.0-1), golang-google-genproto (= 0.0~git20200413.b5235f6-1), golang-google-grpc (= 1.29.1-0ubuntu1), golang-gopkg-ini.v1 (= 1.57.0-1), golang-goprotobuf (= 1.3.4-2), golang-yaml.v2 (= 2.4.0-1)
Filename: ./amd64/azure-storage-azcopy_10.14.1-1_amd64.deb
Size: 4742148
MD5sum: d92091b848fcf591192fb159e09c9ba2
SHA1: 31a7e03582a6b7e2640de4c751a8c683c2c3b25f
SHA256: 7f7158bb849747b6e6cd63e126d1dda4ea7b6e581011771d1cb4dc6bd6f5942e
Section: golang
Priority: optional
Homepage: https://github.com/Azure/azure-storage-azcopy
Description: The new Azure Storage data transfer utility - AzCopy v10 (program)
 AzCopy v10 AzCopy v10 is a command-line utility that you can use to copy
 data to and from containers and file shares in Azure Storage accounts.
 AzCopy V10 presents easy-to-use commands that are optimized for high
 performance and throughput.  Features and capabilities :whitecheckmark:
 Use with storage accounts that have a hierarchical namespace (Azure Data
 Lake Storage Gen2).
 .
 :whitecheckmark: Create containers and file shares.
 .
 :whitecheckmark: Upload files and directories.
 .
 :whitecheckmark: Download files and directories.
 .
 :whitecheckmark: Copy containers, directories and blobs between storage
 accounts (Service to Service).
 .
 :whitecheckmark: Synchronize data between Local <=> Blob Storage, Blob
 Storage <=> File Storage, and Local <=> File Storage.
 .
 :whitecheckmark: Delete blobs or files from an Azure storage account
 .
 :whitecheckmark: Copy objects, directories, and buckets from Amazon Web
 Services (AWS) to Azure Blob Storage (Blobs only).
 .
 :whitecheckmark: Copy objects, directories, and buckets from Google
 Cloud Platform (GCP) to Azure Blob Storage (Blobs only).
 .
 :whitecheckmark: List files in a container.
 .
 :whitecheckmark: Recover from failures by restarting
 previous jobs.  Download AzCopy The latest binary for
 AzCopy along with installation instructions may be found here
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10).
 Find help For complete guidance, visit any of these articles on the
 docs.microsoft.com website.
 .
 :eightspokedasterisk: Get started with AzCopy (download links here)
 (https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-v10)
 .
 :eightspokedasterisk: Upload files to Azure Blob storage by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-upload)
 .
 :eightspokedasterisk: Download blobs
 from Azure Blob storage by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-download)
 .
 :eightspokedasterisk: Copy blobs between
 Azure storage accounts by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-copy)
 .
 :eightspokedasterisk: Synchronize between Local File System/Azure
 Blob Storage (Gen1)/Azure File Storage by using AzCopy
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-synchronize)
 .
 :eightspokedasterisk: Transfer data with AzCopy and file storage
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-files)
 .
 :eightspokedasterisk: Transfer data with AzCopy and Amazon S3 buckets
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-s3)
 .
 :eightspokedasterisk: Transfer data with AzCopy and Google GCP buckets
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-google-cloud)
 .
 :eightspokedasterisk: Use data transfer tools in Azure Stack Hub Storage
 (https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-storage-transfer)
 .
 :eightspokedasterisk: Configure, optimize, and troubleshoot AzCopy
 (https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-configure)
 .
 :eightspokedasterisk: AzCopy WiKi
 (https://github.com/Azure/azure-storage-azcopy/wiki) Supported Operations
 The general format of the AzCopy commands is: azcopy [command] [arguments]
 --[flag-name]=[flag-value] • bench - Runs a performance benchmark by
 uploading or downloading test data to or from a specified destination•
 copy - Copies source data to a destination location. The supported
 directions are: • Local File System <-> Azure Blob (SAS or OAuth
 authentication)• Local File System <-> Azure Files (Share/directory SAS
 authentication)• Local File System <-> Azure Data Lake Storage (ADLS
 Gen2) (SAS, OAuth, or SharedKey authentication)• Azure Blob (SAS or
 public) -> Azure Blob (SAS or OAuth authentication)• Azure Blob (SAS or
 public) -> Azure Files (SAS)• Azure Files (SAS) -> Azure Files (SAS)•
 Azure Files (SAS) -> Azure Blob (SAS or OAuth authentication)• AWS S3
 (Access Key) -> Azure Block Blob (SAS or OAuth authentication)• Google
 Cloud Storage (Service Account Key) -> Azure Block Blob (SAS or OAuth
 authentication) [Preview]• sync - Replicate source to the destination
 location. The supported directions are: • Local File System <-> Azure
 Blob (SAS or OAuth authentication)• Local File System <-> Azure Files
 (Share/directory SAS authentication)• Azure Blob (SAS or public) ->
 Azure Files (SAS)• login - Log in to Azure Active Directory (AD)
 to access Azure Storage resources.• logout - Log out to terminate
 access to Azure Storage resources.• list - List the entities in a
 given resource• doc - Generates documentation for the tool in Markdown
 format• env - Shows the environment variables that you can use to
 configure the behavior of AzCopy.• help - Help about any command• jobs
 - Sub-commands related to managing jobs• load - Sub-commands related
 to transferring data in specific formats• make - Create a container
 or file share.• remove - Delete blobs or files from an Azure storage
 accountFind help from your command prompt For convenience, consider
 adding the AzCopy directory location to your system path for ease of
 use. That way you can type azcopy from any directory on your system.
 .
 To see a list of commands, type azcopy -h and then press the ENTER key.
 .
 To learn about a specific command, just include the name of the command
 (For example: azcopy list -h).
 .
 AzCopy command help example
 .
 If you choose not to add AzCopy to your path, you'll have to change
 directories to the location of your AzCopy executable and type azcopy
 or .\azcopy in Windows PowerShell command prompts.  Frequently asked
 questionsWhat is the difference between sync and copy?• The copy
 command is a simple transferring operation. It scans/enumerates the
 source and attempts to transfer every single file/blob present on the
 source to the destination.  The supported source/destination pairs
 are listed in the help message of the tool.• On the other hand,
 sync scans/enumerates both the source, and the destination to find
 the incremental change.  It makes sure that whatever is present in
 the source will be replicated to the destination. For sync,• If your
 goal is to simply move some files, then copy is definitely the right
 command, since it offers much better performance.  If the use case
 is to incrementally transfer data (files present only on source) then
 sync is the better choice, since only the modified/missing files will
 be transferred.  Since sync enumerates both source and destination to
 find the incremental change, it is relatively slower as compared to
 copyWill copy overwrite my files?  By default, AzCopy will overwrite
 the files at the destination if they already exist. To avoid this
 behavior, please use the flag --overwrite=false.  Will sync overwrite
 my files?  By default, AzCopy sync use last-modified-time to determine
 whether to transfer the same file present at both the source, and
 the destination.  i.e, If the source file is newer compared to the
 destination file, we overwrite the destination You can change this
 default behaviour and overwrite files at the destination by using the
 flag --mirror-mode=true Will 'sync' delete files in the destination
 if they no longer exist in the source location?  By default, the
 'sync' command doesn't delete files in the destination unless you use
 an optional flag with the command.  To learn more, see Synchronize files
 (https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-synchronize).
 How to contribute to AzCopy v10 This project welcomes contributions and
 suggestions.  Most contributions require you to agree to a Contributor
 License Agreement (CLA) declaring that you have the right to, and
 actually do, grant us the rights to use your contribution. For details,
 visit https://cla.microsoft.com.
 .
 When you submit a pull request, a CLA-bot will automatically determine
 whether you need to provide a CLA and decorate the PR appropriately
 (e.g., label, comment). Simply follow the instructions provided by the
 bot. You will only need to do this once across all repos using our CLA.
 .
 This project has adopted the Microsoft Open Source Code of
 Conduct (https://opensource.microsoft.com/codeofconduct/).
 For more information see the Code of Conduct FAQ
 (https://opensource.microsoft.com/codeofconduct/faq/) or contact
 opencode@microsoft.com (mailto:opencode@microsoft.com) with any additional
 questions or comments.

Package: bcc-lua
Source: bcc
Version: 0.24.0-4
Architecture: all
Maintainer: Brenden Blanco <bblanco@plumgrid.com>
Installed-Size: 691
Depends: libbcc (= 0.24.0-4)
Conflicts: bpfcc-lua
Provides: bpfcc-lua
Filename: ./all/bcc-lua_0.24.0-4_all.deb
Size: 321696
MD5sum: aab726eb91bcc342857cda4f0741da80
SHA1: 6efaf18adc26c46f81bb564aab279f8412d26dd8
SHA256: 4c90399fcac887d0be009e46a31fc3ee569cb60c8d4c2c09321249a6e6f7bae1
Section: misc
Priority: optional
Homepage: https://github.com/iovisor/bcc
Description: Standalone tool to run BCC tracers written in Lua

Package: bcc-tools
Source: bcc
Version: 0.24.0-4
Architecture: all
Maintainer: Brenden Blanco <bblanco@plumgrid.com>
Installed-Size: 2545
Depends: python3-bcc (= 0.24.0-4)
Conflicts: bpfcc-tools
Provides: bpfcc-tools
Filename: ./all/bcc-tools_0.24.0-4_all.deb
Size: 563690
MD5sum: 0d8492f1fd526a65736f6b4f27308778
SHA1: b224f0a496c4a5b9e20fa8645582b8bbc183ea5d
SHA256: 0f73b4af9d1589248637e2e87446efd9eb0039662ec55da046a4fd5836316ab9
Section: misc
Priority: optional
Homepage: https://github.com/iovisor/bcc
Description: Command line tools for BPF Compiler Collection (BCC)

Package: cvm-guest-attestation-client
Source: cvm-guest-attestation
Version: 1.0.3-1
Architecture: amd64
Maintainer: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Installed-Size: 119
Depends: libazguestattestation1, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libstdc++6 (>= 11)
Filename: ./amd64/cvm-guest-attestation-client_1.0.3-1_amd64.deb
Size: 41164
MD5sum: 5e8746e37de4f4edf6cb514360e0a3b8
SHA1: 36d64ff536a5cc1653d793772c50f509c4a3db42
SHA256: a494d4c1cebb8cafea7aeceb82c4c1be076e31679402796cd780f8bfa2b57b80
Section: misc
Priority: optional
Description: CVM Attestation Sample App

Package: golang-github-azure-azure-storage-blob-go-dev
Source: golang-github-azure-azure-storage-blob-go
Version: 0.13.0+git20210914.2d6cd3e-1
Architecture: all
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 1440
Depends: golang-github-azure-azure-pipeline-go-dev, golang-github-azure-go-autorest-dev, golang-github-google-uuid-dev, golang-gopkg-check.v1-dev
Filename: ./all/golang-github-azure-azure-storage-blob-go-dev_0.13.0+git20210914.2d6cd3e-1_all.deb
Size: 143808
MD5sum: d91ccb2eeb7ad19115fd87881078eb59
SHA1: 68b2c4dfde258ce8bb3e11db5c7be70cf2f4dcbb
SHA256: 3a1cf9845ada6ba59175a49a08b7acac4af8cc975177f342b9fb489e456fd49b
Section: golang
Priority: optional
Homepage: https://github.com/Azure/azure-storage-blob-go
Description: Microsoft Azure Blob Storage Library for Go (library)
 Azure Storage Blob SDK for Go (PREVIEW) GoDoc Widget
 (https://godoc.org/github.com/Azure/azure-storage-blob-go/azblob)
 If you would like to access our latest Go SDK,
 please refer to the new preview azblob package here
 (https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/storage/azblob#readme).
 If you would like more information on Azure's burgeoning
 effort to coordinate the development of the SDKs across
 services, of which this change is a part, please refer to this article
 (https://azure.microsoft.com/en-us/blog/previewing-azure-sdks-following-new-azure-sdk-api-standards/).We
 will continue to respond to issues here, but prefer that you post them on
 the new repo (https://github.com/Azure/azure-sdk-for-go). Thank you for
 your patience. We look forward to continuing to work together with you.
 The Microsoft Azure Storage SDK for Go allows you to build applications
 that takes advantage of Azure's scalable cloud storage.
 .
 This repository contains the open source Blob SDK for Go. The File
 SDK (https://github.com/Azure/azure-storage-file-go) and Queue SDK
 (https://github.com/Azure/azure-storage-queue-go) are also available.
 .
 This library is in preview.  Features• Blob Storage •
 Create/List/Delete Containers• Create/Read/List/Update/Delete
 Block Blobs• Create/Read/List/Update/Delete Page Blobs•
 Create/Read/List/Update/Delete Append BlobsGetting Started•
 If you don't already have it, install the Go distribution
 (https://golang.org/dl/)• Get the SDK, with any method you prefer:
 • Go Get: go get github.com/Azure/azure-storage-blob-go/azblob• Dep:
 add github.com/Azure/azure-storage-blob-go to Gopkg.toml:
 .
 [[constraint]]
   version = "0.3.0" name = "github.com/Azure/azure-storage-blob-go"•
   Module: simply import the SDK and Go will download it for you• Use
   the SDK:
 import "github.com/Azure/azure-storage-blob-go/azblob"Version Table•
 If you are looking to use a specific version of the Storage Service,
 please refer to the following table: | Service Version | Corresponding
 SDK Version | Import Path                                              |
 |-----------------|---------------------------|----------------------------------------------------------|
 | 2016-05-31      | 0.2.0                     |
 github.com/Azure/azure-storage-blob-go/2016-05-31/azblob
 | | 2017-07-29      | 0.2.0                     |
 github.com/Azure/azure-storage-blob-go/2017-07-29/azblob
 | | 2018-03-28      | 0.3.0 - 0.5.0             |
 github.com/Azure/azure-storage-blob-go/azblob            |
 | 2018-11-09      | 0.6.0 - 0.7.0             |
 github.com/Azure/azure-storage-blob-go/azblob            |
 .
 Note: the directory structure of the SDK has changed dramatically since
 0.3.0. The different Service Versions are no longer sub-directories;
 the latest azblob is directly under the root directory. In the
 future, each new Service Version will be introduced with a new
 major semantic version.  SDK Architecture• The Azure Storage SDK
 for Go provides low-level and high-level APIs.  • ServiceURL,
 ContainerURL and BlobURL objects provide the low-level API
 functionality and map one-to-one to the Azure Storage Blob REST APIs
 (https://docs.microsoft.com/en-us/rest/api/storageservices/blob-service-rest-api)•
 The high-level APIs provide convenience abstractions
 such as uploading a large stream to a block blob (using
 multiple PutBlock requests).Code Samples• Blob Storage Examples
 (https://godoc.org/github.com/Azure/azure-storage-blob-go/azblob#pkg-examples)License
 This project is licensed under MIT.  Contributing This project welcomes
 contributions and suggestions.  Most contributions require you to agree to
 a Contributor License Agreement (CLA) declaring that you have the right
 to, and actually do, grant us the rights to use your contribution. For
 details, visit https://cla.microsoft.com.
 .
 When you submit a pull request, a CLA-bot will automatically determine
 whether you need to provide a CLA and decorate the PR appropriately
 (e.g., label, comment). Simply follow the instructions provided by the
 bot. You will only need to do this once across all repos using our CLA.
 .
 This project has adopted the Microsoft Open Source Code of
 Conduct (https://opensource.microsoft.com/codeofconduct/).
 For more information see the Code of Conduct FAQ
 (https://opensource.microsoft.com/codeofconduct/faq/) or contact
 opencode@microsoft.com (mailto:opencode@microsoft.com) with any additional
 questions or comments.

Package: golang-github-azure-azure-storage-file-go-dev
Source: golang-github-azure-azure-storage-file-go
Version: 0.6.0+git20201111.3c1754d-1
Architecture: all
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 731
Depends: golang-github-azure-azure-pipeline-go-dev, golang-golang-x-sys-dev, golang-gopkg-check.v1-dev
Filename: ./all/golang-github-azure-azure-storage-file-go-dev_0.6.0+git20201111.3c1754d-1_all.deb
Size: 95370
MD5sum: 22dfa414c9193de4a2823fa587bde3e7
SHA1: 36de0f4962cbe3e9bb5d564370f10802ea66ed8a
SHA256: e9f0b0b5b9124a1ee0672166e0677df72b552e9f48cb4d1f4a7a920e4114bd32
Section: golang
Priority: optional
Homepage: https://github.com/Azure/azure-storage-file-go
Description: Microsoft Azure File Storage Library for Go (library)
 Azure Storage File SDK for Go GoDoc Widget
 (https://godoc.org/github.com/Azure/azure-storage-file-go/azfile) Build
 Status (https://travis-ci.org/Azure/azure-storage-file-go)
 .
 The Microsoft Azure Storage SDK for Go allows you to build applications
 that takes advantage of Azure's scalable cloud storage.
 .
 This repository contains the open source File SDK for Go.  Features•
 File Storage • Create/List/Delete Shares• Create/List/Delete
 Directories• Create/Read/List/Update/Delete FilesGetting
 Started• If you don't already have it, install the Go distribution
 (https://golang.org/dl/)• Get the SDK, with any method you prefer:
 • Go Get: go get github.com/Azure/azure-storage-file-go/azfile• Dep:
 add github.com/Azure/azure-storage-file-go to Gopkg.toml:
 .
 [[constraint]]
   version = "0.4.1" name = "github.com/Azure/azure-storage-file-go"•
   Module: simply import the SDK and Go will download it for you• Use
   the SDK:
 import "github.com/Azure/azure-storage-file-go/azfile"Version Table•
 If you are looking to use a specific version of the Storage Service,
 please refer to the following table: | Service Version | Corresponding
 SDK Version | Import Path                                              |
 |-----------------|---------------------------|----------------------------------------------------------|
 | 2017-07-29      | 0.3.0                     |
 github.com/Azure/azure-storage-file-go/2017-07-29/azfile
 | | 2018-03-28      | 0.4.1+                    |
 github.com/Azure/azure-storage-file-go/azfile            |
 .
 Note: the directory structure of the SDK has changed dramatically since
 0.4.1. The different Service Versions are no longer sub-directories;
 the latest azfile is directly under the root directory. In the
 future, each new Service Version will be introduced with a new
 major semantic version.  SDK Architecture• The Azure Storage SDK
 for Go provides low-level and high-level APIs.  • ServiceURL,
 ShareURL, DirectoryURL and FileURL objects provide the low-level API
 functionality and map one-to-one to the Azure Storage File REST APIs
 (https://docs.microsoft.com/en-us/rest/api/storageservices/file-service-rest-api)•
 The high-level APIs provide convenience abstractions such as
 uploading a large stream to an Azure file (using multiple PutRange
 requests in parallel) or downloading a large Azure file to local (using
 multiple Get requests in parallel).Code Samples• File Storage Examples
 (https://godoc.org/github.com/Azure/azure-storage-file-go/azfile#pkg-examples)License
 This project is licensed under MIT.  Contributing This project welcomes
 contributions and suggestions.  Most contributions require you to agree to
 a Contributor License Agreement (CLA) declaring that you have the right
 to, and actually do, grant us the rights to use your contribution. For
 details, visit https://cla.microsoft.com.
 .
 When you submit a pull request, a CLA-bot will automatically determine
 whether you need to provide a CLA and decorate the PR appropriately
 (e.g., label, comment). Simply follow the instructions provided by the
 bot. You will only need to do this once across all repos using our CLA.
 .
 This project has adopted the Microsoft Open Source Code of
 Conduct (https://opensource.microsoft.com/codeofconduct/).
 For more information see the Code of Conduct FAQ
 (https://opensource.microsoft.com/codeofconduct/faq/) or contact
 opencode@microsoft.com (mailto:opencode@microsoft.com) with any additional
 questions or comments.

Package: golang-github-azure-go-autorest-dev
Source: golang-github-azure-go-autorest
Version: 14.2.0+git20211214.a46566d-1
Architecture: all
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 834
Depends: golang-github-golang-jwt-jwt-dev, golang-golang-x-crypto-dev
Filename: ./all/golang-github-azure-go-autorest-dev_14.2.0+git20211214.a46566d-1_all.deb
Size: 111772
MD5sum: 10a032fac05040b961c153e117b08baa
SHA1: 2e0cf3239234f64e55a522870375db93e6bf5e8c
SHA256: 3c17488e79bd9ec0fccba9d256d3c63da21b4c8588c3260320dca137f9592157
Section: golang
Priority: optional
Homepage: https://github.com/Azure/go-autorest
Description: This package implements an HTTP request pipeline suitable for use across multiple go-routines and provides the shared routines relied on by AutoRest generated Go code. (library)
 go-autorest GoDoc
 (https://godoc.org/github.com/Azure/go-autorest/autorest) Build Status
 (https://dev.azure.com/azure-sdk/public/_build/latest?definitionId=625&branchName=master)
 Go Report Card (https://goreportcard.com/report/Azure/go-autorest)
 .
 Package go-autorest provides an HTTP request client for use with Autorest
 (https://github.com/Azure/autorest.go)-generated API client packages.
 .
 An authentication client tested with Azure Active
 Directory (AAD) is also provided in this repo in the package
 github.com/Azure/go-autorest/autorest/adal.  Despite its name,
 this package is maintained only as part of the Azure Go SDK and
 is not related to other "ADAL" libraries in github.com/AzureAD
 (https://github.com/AzureAD).  Overview Package go-autorest implements
 an HTTP request pipeline suitable for use across multiple goroutines
 and provides the shared routines used by packages generated by Autorest
 (https://github.com/Azure/autorest.go).
 .
 The package breaks sending and responding to HTTP requests into three
 phases: Preparing, Sending, and Responding. A typical pattern is:
 .
 ```go
   req, err := Prepare(&http.Request{},
     token.WithAuthorization())
 .
 resp, err := Send(req,
     WithLogging(logger),
     DoErrorIfStatusCode(http.StatusInternalServerError), DoCloseIfError(),
     DoRetryForAttempts(5, time.Second))
 .
 err = Respond(resp,
         ByDiscardingBody(),
     ByClosing())
 ```
 .
 Each phase relies on decorators to modify and / or manage
 processing. Decorators may first modify and then pass the data along,
 pass the data first and then modify the result, or wrap themselves
 around passing the data (such as a logger might do). Decorators run in
 the order provided. For example, the following:
 .
 go
   req, err := Prepare(&http.Request{},
     WithBaseURL("https://microsoft.com/"), WithPath("a"), WithPath("b"),
     WithPath("c"))
 .
 .
 will set the URL to:
 .
 .
   https://microsoft.com/a/b/c
 .
 .
 Preparers and Responders may be shared and re-used (assuming the
 underlying decorators support sharing and re-use). Performant use is
 obtained by creating one or more Preparers and Responders shared among
 multiple go-routines, and a single Sender shared among multiple sending
 go-routines, all bound together by means of input / output channels.
 .
 Decorators hold their passed state within a closure (such as the path
 components in the example above). Be careful to share Preparers and
 Responders only in a context where such held state applies. For example,
 it may not make sense to share a Preparer that applies a query string
 from a fixed set of values. Similarly, sharing a Responder that reads
 the response body into a passed struct (e.g., ByUnmarshallingJson)
 is likely incorrect.
 .
 Errors raised by autorest objects and methods will conform to the
 autorest.Error interface.
 .
 See the included examples for more detail. For details on
 the suggested use of this package by generated clients, see
 the Client described below.  HelpersHandling Swagger Dates The
 Swagger specification (https://swagger.io) that drives AutoRest
 (https://github.com/Azure/autorest/) precisely defines two date forms:
 date and date-time. The github.com/Azure/go-autorest/autorest/date package
 provides time.Time derivations to ensure correct parsing and formatting.
 Handling Empty Values In JSON, missing values have different semantics
 than empty values. This is especially true for services using the
 HTTP PATCH verb. The JSON submitted with a PATCH request generally
 contains only those values to modify. Missing values are to be left
 unchanged. Developers, then, require a means to both specify an empty
 value and to leave the value out of the submitted JSON.
 .
 The Go JSON package (encoding/json) supports the omitempty tag. When
 specified, it omits empty values from the rendered JSON. Since Go
 defines default values for all base types (such as "" for string and
 0 for int) and provides no means to mark a value as actually empty,
 the JSON package treats default values as meaning empty, omitting them
 from the rendered JSON. This means that, using the Go base types encoded
 through the default JSON package, it is not possible to create JSON to
 clear a value at the server.
 .
 The workaround within the Go community is to use pointers to base types
 in lieu of base types within structures that map to JSON. For example,
 instead of a value of type string, the workaround uses *string. While
 this enables distinguishing empty values from those to be unchanged,
 creating pointers to a base type (notably constant, in-line values)
 requires additional variables. This, for example,
 .
 go
   s := struct {
     S *string
   }{ S: &"foo" }
 .
 fails, while, this
 .
 go
   v := "foo" s := struct {
     S *string
   }{ S: &v }
 .
 succeeds.
 .
 To ease using pointers, the subpackage to contains helpers that convert
 to and from pointers for Go base types which have Swagger analogs. It
 also provides a helper that converts between map[string]string
 and map[string]*string, enabling the JSON to specify that the value
 associated with a key should be cleared. With the helpers, the previous
 example becomes
 .
 go
   s := struct {
     S *string
   }{ S: to.StringPtr("foo") }
 .
 Install bash go get github.com/Azure/go-autorest/autorest
 go get github.com/Azure/go-autorest/autorest/azure go
 get github.com/Azure/go-autorest/autorest/date go get
 github.com/Azure/go-autorest/autorest/to
 .
 Using with Go Modules In v12.0.1
 (https://github.com/Azure/go-autorest/pull/386), this repository
 introduced the following modules.  • autorest/adal•
 autorest/azure/auth• autorest/azure/cli• autorest/date•
 autorest/mocks• autorest/to• autorest/validation• autorest•
 logger• tracing Tagging cumulative SDK releases as a whole
 (e.g. v12.3.0) is still enabled to support consumers of this repo
 that have not yet migrated to modules.  License See LICENSE file.
 --------------------------------------------------------------------------------
 .
 This project has adopted the Microsoft Open Source Code of
 Conduct (https://opensource.microsoft.com/codeofconduct/). For
 more information see the Code of Conduct FAQ
 (https://opensource.microsoft.com/codeofconduct/faq/) or contact
 opencode@microsoft.com (mailto:opencode@microsoft.com) with any additional
 questions or comments.

Package: golang-github-golang-jwt-jwt-dev
Source: golang-github-golang-jwt-jwt
Version: 4.3.0+git20220210.279dd19-1
Architecture: all
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 4111
Filename: ./all/golang-github-golang-jwt-jwt-dev_4.3.0+git20220210.279dd19-1_all.deb
Size: 2103902
MD5sum: cdfb263ec8decc108bb5fc88349a71d8
SHA1: cc0bf195920248c54a0b40536ead5c9bc1027852
SHA256: 638bc8819076350ad0b19758bc84c75181dae59f1b3f055d60a8587352ba810a
Section: golang
Priority: optional
Homepage: https://github.com/golang-jwt/jwt
Description: Community maintained clone of https://github.com/dgrijalva/jwt-go (library)
 jwt-go build
 (https://github.com/golang-jwt/jwt/actions/workflows/build.yml) Go
 Reference (https://pkg.go.dev/github.com/golang-jwt/jwt/v4)
 .
 A go (http://www.golang.org) (or 'golang' for search
 engine friendliness) implementation of JSON Web Tokens
 (https://datatracker.ietf.org/doc/html/rfc7519).
 .
 Starting with v4.0.0
 (https://github.com/golang-jwt/jwt/releases/tag/v4.0.0) this project adds
 Go module support, but maintains backwards compatibility with older v3.x.y
 tags and upstream github.com/dgrijalva/jwt-go.  See the MIGRATION_GUIDE.md
 (./MIGRATION_GUIDE.md) for more information.
 .
 After the original author of the library suggested migrating the
 maintenance of jwt-go, a dedicated team of open source maintainers
 decided to clone the existing library into this repository. See
 dgrijalva/jwt-go#462 (https://github.com/dgrijalva/jwt-go/issues/462)
 for a detailed discussion on this topic.
 .
 SECURITY NOTICE: Some older versions of Go have a security issue in the
 crypto/elliptic. Recommendation is to upgrade to at least 1.15 See issue
 dgrijalva/jwt-go#216 (https://github.com/dgrijalva/jwt-go/issues/216)
 for more detail.
 .
 SECURITY NOTICE: It's important that you
 validate the alg presented is what you expect
 (https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/).
 This library attempts to make it easy to do the right thing by requiring
 key types match the expected alg, but you should take the extra step
 to verify it in your usage.  See the examples provided.  Supported Go
 versions Our support of Go versions is aligned with Go's version release
 policy (https://golang.org/doc/devel/release#policy).  So we will support
 a major version of Go until there are two newer major releases.  We no
 longer support building jwt-go with unsupported Go versions, as these
 contain security vulnerabilities which will not be fixed.  What the heck
 is a JWT?  JWT.io has a great introduction (https://jwt.io/introduction)
 to JSON Web Tokens.
 .
 In short, it's a signed JSON object that does something useful (for
 example, authentication).  It's commonly used for Bearer tokens
 in Oauth 2.  A token is made of three parts, separated by .'s.
 The first two parts are JSON objects, that have been base64url
 (https://datatracker.ietf.org/doc/html/rfc4648) encoded.  The last part
 is the signature, encoded the same way.
 .
 The first part is called the header.  It contains the necessary
 information for verifying the last part, the signature.  For example,
 which encryption method was used for signing and what key was used.
 .
 The part in the middle is the interesting bit.  It's called the
 Claims and contains the actual stuff you care about.  Refer to RFC
 7519 (https://datatracker.ietf.org/doc/html/rfc7519) for information
 about reserved keys and the proper way to add your own.  What's in
 the box?  This library supports the parsing and verification as well
 as the generation and signing of JWTs.  Current supported signing
 algorithms are HMAC SHA, RSA, RSA-PSS, and ECDSA, though hooks are
 present for adding your own.  Examples See the project documentation
 (https://pkg.go.dev/github.com/golang-jwt/jwt/v4) for examples
 of usage: • Simple example of parsing and validating a token
 (https://pkg.go.dev/github.com/golang-jwt/jwt#example-Parse-Hmac)•
 Simple example of building and signing a token
 (https://pkg.go.dev/github.com/golang-jwt/jwt#example-New-Hmac)•
 Directory of Examples
 (https://pkg.go.dev/github.com/golang-jwt/jwt#pkg-examples)Extensions
 This library publishes all the necessary components for adding your own
 signing methods or key functions.  Simply implement the SigningMethod
 interface and register a factory method using RegisterSigningMethod or
 provide a jwt.Keyfunc.
 .
 A common use case would be integrating with different 3rd party signature
 providers, like key management services from various cloud providers or
 Hardware Security Modules (HSMs) or to implement additional standards.
 .
 | Extension | Purpose
 | Repo                                       | | --------- |
 --------------------------------------------------------------------------------------------------------
 | ------------------------------------------ | | GCP       | Integrates
 with multiple Google Cloud Platform signing tools (AppEngine, IAM API,
 Cloud KMS)             | https://github.com/someone1/gcp-jwt-go     |
 | AWS       | Integrates with AWS Key Management Service, KMS
 | https://github.com/matelang/jwt-go-aws-kms |
 | JWKS      | Provides support for JWKS (RFC 7517
 (https://datatracker.ietf.org/doc/html/rfc7517)) as a jwt.Keyfunc |
 https://github.com/MicahParks/keyfunc       |
 .
 Disclaimer: Unless otherwise specified, these integrations
 are maintained by third parties and should not be considered
 as a primary offer by any of the mentioned cloud providers
 Compliance This library was last reviewed to comply with RFC 7519
 (https://datatracker.ietf.org/doc/html/rfc7519) dated May 2015 with a few
 notable differences: • In order to protect against accidental use of
 Unsecured JWTs (https://datatracker.ietf.org/doc/html/rfc7519#section-6),
 tokens using alg=none will only be accepted if the constant
 jwt.UnsafeAllowNoneSignatureType is provided as the key.Project Status &
 Versioning This library is considered production ready.  Feedback and
 feature requests are appreciated.  The API should be considered stable.
 There should be very few backwards-incompatible changes outside of major
 version updates (and only with good reason).
 .
 This project uses Semantic Versioning 2.0.0 (http://semver.org).  Accepted
 pull requests will land on main.  Periodically, versions will be tagged
 from main.  You can find all the releases on the project releases page
 (https://github.com/golang-jwt/jwt/releases).
 .
 BREAKING CHANGES:* A full list of breaking changes is available in
 VERSION_HISTORY.md.  See MIGRATION_GUIDE.md for more information on
 updating your code.  Usage TipsSigning vs Encryption A token is simply
 a JSON object that is signed by its author. this tells you exactly two
 things about the data: • The author of the token was in the possession
 of the signing secret• The data has not been modified since it was
 signed It's important to know that JWT does not provide encryption,
 which means anyone who has access to the token can read its contents. If
 you need to protect (encrypt) the data, there is a companion spec, JWE,
 that provides this functionality. JWE is currently outside the scope
 of this library.  Choosing a Signing Method There are several signing
 methods available, and you should probably take the time to learn about
 the various options before choosing one.  The principal design decision
 is most likely going to be symmetric vs asymmetric.
 .
 Symmetric signing methods, such as HSA, use only a single secret. This
 is probably the simplest signing method to use since any []byte can be
 used as a valid secret. They are also slightly computationally faster to
 use, though this rarely is enough to matter. Symmetric signing methods
 work the best when both producers and consumers of tokens are trusted,
 or even the same system. Since the same secret is used to both sign and
 validate tokens, you can't easily distribute the key for validation.
 .
 Asymmetric signing methods, such as RSA, use different keys for signing
 and verifying tokens. This makes it possible to produce tokens with
 a private key, and allow any consumer to access the public key for
 verification.  Signing Methods and Key Types Each signing method expects a
 different object type for its signing keys. See the package documentation
 for details. Here are the most common ones: • The HMAC signing method
 (https://pkg.go.dev/github.com/golang-jwt/jwt#SigningMethodHMAC)
 (HS256,HS384,HS512) expect []byte values for
 signing and validation• The RSA signing method
 (https://pkg.go.dev/github.com/golang-jwt/jwt#SigningMethodRSA)
 (RS256,RS384,RS512) expect *rsa.PrivateKey for signing and
 *rsa.PublicKey for validation• The ECDSA signing method
 (https://pkg.go.dev/github.com/golang-jwt/jwt#SigningMethodECDSA)
 (ES256,ES384,ES512) expect *ecdsa.PrivateKey for signing and
 *ecdsa.PublicKey for validation• The EdDSA signing method
 (https://pkg.go.dev/github.com/golang-jwt/jwt#SigningMethodEd25519)
 (Ed25519) expect ed25519.PrivateKey for signing and ed25519.PublicKey
 for validationJWT and OAuth It's worth mentioning that OAuth and JWT are
 not the same thing. A JWT token is simply a signed JSON object. It can be
 used anywhere such a thing is useful. There is some confusion, though, as
 JWT is the most common type of bearer token used in OAuth2 authentication.
 .
 Without going too far down the rabbit hole, here's a description of
 the interaction of these technologies: • OAuth is a protocol for
 allowing an identity provider to be separate from the service a user
 is logging in to. For example, whenever you use Facebook to log into a
 different service (Yelp, Spotify, etc), you are using OAuth.• OAuth
 defines several options for passing around authentication data. One
 popular method is called a "bearer token". A bearer token is simply
 a string that should only be held by an authenticated user. Thus,
 simply presenting this token proves your identity. You can probably
 derive from here why a JWT might make a good bearer token.• Because
 bearer tokens are used for authentication, it's important they're kept
 secret. This is why transactions that use bearer tokens typically happen
 over SSL.Troubleshooting This library uses descriptive error messages
 whenever possible. If you are not getting the expected result, have a
 look at the errors. The most common place people get stuck is providing
 the correct type of key to the parser. See the above section on signing
 methods and key types.  More Documentation can be found on pkg.go.dev
 (https://pkg.go.dev/github.com/golang-jwt/jwt).
 .
 The command line utility included in this project (cmd/jwt) provides
 a straightforward example of token creation and parsing as well as a
 useful tool for debugging your own integration. You'll also find several
 implementation examples in the documentation.
 .
 golang-jwt (https://github.com/orgs/golang-jwt)
 incorporates a modified version of the JWT logo, which
 is distributed under the terms of the MIT License
 (https://github.com/jsonwebtoken/jsonwebtoken.github.io/blob/master/LICENSE.txt).

Package: golang-github-jeffreyrichter-enum-dev
Source: golang-github-jeffreyrichter-enum
Version: 0.0~git20180725.2567042-1
Architecture: all
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 43
Filename: ./all/golang-github-jeffreyrichter-enum-dev_0.0~git20180725.2567042-1_all.deb
Size: 8730
MD5sum: a0abad9f63d10038ce24943b0833bf4b
SHA1: 23f98a85b5a6c453a273158b46232ac09b1f0ae3
SHA256: 48b8ba63dd8948fbef72fe48f8a06a49b3edb95abd484eb7c98c6b79fdc21048
Section: golang
Priority: optional
Homepage: https://github.com/JeffreyRichter/enum
Description: Support for enumerated types for the Go programming language (library)
 enum Support for enumerated types for the Go programming language

Package: golang-github-wastore-keyctl-dev
Source: golang-github-wastore-keyctl
Version: 0.3.1-1
Architecture: all
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 36
Filename: ./all/golang-github-wastore-keyctl-dev_0.3.1-1_all.deb
Size: 6296
MD5sum: 7d930a583e659d148cf8aa0d494cadc3
SHA1: e82123d41606ebd843f16a88572aa23f18383fdf
SHA256: 2a44503a49ce594aa4e25a7e3a3b48c8ac81339212fa18f3caa9491bc03720fa
Section: golang
Priority: optional
Homepage: https://github.com/wastore/keyctl
Description: A Go-lang interface to the linux kernel keyring api (library)
 keyctl Slim version of github.com/jsipprell/keyctl with basic keyring
 operations.

Package: libazguestattestation-dev
Source: cvm-guest-attestation
Version: 1.0.3-1
Architecture: amd64
Maintainer: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Installed-Size: 10
Filename: ./amd64/libazguestattestation-dev_1.0.3-1_amd64.deb
Size: 1000
MD5sum: f136233877586277224930cfa8035adc
SHA1: bb4ecdbabb125637f384a898a6ee68927d46593f
SHA256: 2fb9d403374e1c3afa1c8961d0701369638de722247fccea6e0e3d453ef532df
Section: misc
Priority: optional
Description: CVM Attestation Library

Package: libazguestattestation1
Source: cvm-guest-attestation
Version: 1.0.3-1
Architecture: amd64
Maintainer: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Installed-Size: 420
Depends: libc6 (>= 2.32), libcurl4 (>= 7.16.2), libgcc-s1 (>= 3.3.1), libssl1.1 (>= 1.1.0), libstdc++6 (>= 11), libtss2-esys-3.0.2-0 (>= 2.3.1), libtss2-mu0 (>= 3.0.1), libtss2-tcti-device0 (>= 3.0.1)
Filename: ./amd64/libazguestattestation1_1.0.3-1_amd64.deb
Size: 153668
MD5sum: 4321b9381a4425c3dafc7f6de2a75701
SHA1: fd4cf6475b13763949b99410db128df30f2bb93c
SHA256: 6ef06b7859ac5c4467ad5bc851a15bcbaaf43b3b60d9f1d7e6acecb943563056
Section: misc
Priority: optional
Description: CVM Attestation Library

Package: libbcc
Source: bcc
Version: 0.24.0-4
Architecture: amd64
Maintainer: Brenden Blanco <bblanco@plumgrid.com>
Installed-Size: 77511
Depends: libc6, libstdc++6, libelf1
Conflicts: libbpfcc, libbpfcc-dev
Provides: libbpfcc, libbpfcc-dev
Filename: ./amd64/libbcc_0.24.0-4_amd64.deb
Size: 20609754
MD5sum: dc278eb986c4a6fa5c58e92749dbdfbc
SHA1: 056e6ea3db2b9407c5db1bdd7d8477e4024af9ad
SHA256: c02948f8d04627c8c90826530c00b9ccf46681d53aa4dfc07fe05770619c3257
Section: misc
Priority: optional
Homepage: https://github.com/iovisor/bcc
Description: Shared Library for BPF Compiler Collection (BCC)
 Shared Library for BPF Compiler Collection to control BPF programs
 from userspace.

Package: libbcc-examples
Source: bcc
Version: 0.24.0-4
Architecture: amd64
Maintainer: Brenden Blanco <bblanco@plumgrid.com>
Installed-Size: 551
Depends: libbcc (= 0.24.0-4)
Filename: ./amd64/libbcc-examples_0.24.0-4_amd64.deb
Size: 289526
MD5sum: f59bcc220c374bb87347cff3d20eb1a7
SHA1: ff7744f643e9501a86aa0bed883e156ce0336be0
SHA256: 51e859e2ec5fc8c45453577efecf9de8031a64d18d9c26dd8de576383f1ae71c
Section: misc
Priority: optional
Homepage: https://github.com/iovisor/bcc
Description: Examples for BPF Compiler Collection (BCC)

Package: libbpf-dev
Source: libbpf (0.7.0-2)
Version: 1:0.7.0-2
Architecture: amd64
Maintainer: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Installed-Size: 893
Depends: libbpf0 (= 1:0.7.0-2), libelf-dev, zlib1g-dev
Filename: ./amd64/libbpf-dev_0.7.0-2_amd64.deb
Size: 232152
MD5sum: 6f5f9286be8ecd285e791a7a9f1882ed
SHA1: 4d768f2b5c6312de1727dd8983f83d36026e0b0a
SHA256: b05b49e08ed9056db6203c366253c4c3ee7ec65f6ca7c05ccb287dedb0ee661f
Section: libdevel
Priority: optional
Multi-Arch: same
Description: eBPF helper library (development files)
 libbpf is a library for loading eBPF programs and reading and
 manipulating eBPF objects from user-space.
 .
 This package is needed to compile programs against libbpf.

Package: libbpf0
Source: libbpf (0.7.0-2)
Version: 1:0.7.0-2
Architecture: amd64
Maintainer: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Installed-Size: 378
Depends: libc6 (>= 2.28), libelf1 (>= 0.142), zlib1g (>= 1:1.2.3.3)
Filename: ./amd64/libbpf0_0.7.0-2_amd64.deb
Size: 152368
MD5sum: 5eb14f643d7adfb925fc9b696eb6cd9f
SHA1: 7c2118ba2bc3324e722c5d7d845e342c0ad39889
SHA256: a2acaf1adee4adeeb77c4c191f0ea85181ef8cd51ceeee5d22f343c27b07c4b1
Section: libs
Priority: optional
Multi-Arch: same
Description: eBPF helper library (shared library)
 libbpf is a library for loading eBPF programs and reading and
 manipulating eBPF objects from user-space.
 .
 This package contains the shared library.

Package: libsdbus-c++-bin
Source: sdbus-cpp
Version: 0.8.3-4
Architecture: amd64
Maintainer: Shengjing Zhu <zhsj@debian.org>
Installed-Size: 117
Depends: libc6 (>= 2.34), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.3.1), libstdc++6 (>= 9)
Filename: ./amd64/libsdbus-c++-bin_0.8.3-4_amd64.deb
Size: 42106
MD5sum: ed3b88c30b326dc18a3b48e05e481139
SHA1: d1b65a9e4def38a6069b84b7ecfcfa9a08e56bcf
SHA256: 35dcdd88b5da108ca7c3dd64d511f26f38992aedb45efd472772b2a059bbe715
Section: utils
Priority: optional
Homepage: https://github.com/Kistler-Group/sdbus-cpp
Description: High-level C++ D-Bus library for Linux in modern C++ (utilities)
 sdbus-c++ is a high-level C++ D-Bus library for Linux designed to provide
 expressive, easy-to-use API in modern C++. It adds another layer of
 abstraction on top of sd-bus, a nice, fresh C D-Bus implementation by systemd.
 .
 This package contains binary utilities.

Package: libsdbus-c++-dev
Source: sdbus-cpp
Version: 0.8.3-4
Architecture: amd64
Maintainer: Shengjing Zhu <zhsj@debian.org>
Installed-Size: 183
Depends: libsdbus-c++-bin (= 0.8.3-4), libsdbus-c++0 (= 0.8.3-4)
Filename: ./amd64/libsdbus-c++-dev_0.8.3-4_amd64.deb
Size: 24098
MD5sum: aa290d7b6adba94f45bfc5c1aeb1ec1a
SHA1: 38afcd12502b8f2ca20c11d1fdf029d1ea7f4e52
SHA256: e2169d62c8937ac74faed0362f01258d0080114f4817708f34311c5529e9bab0
Section: libdevel
Priority: optional
Homepage: https://github.com/Kistler-Group/sdbus-cpp
Description: High-level C++ D-Bus library for Linux in modern C++ (development files)
 sdbus-c++ is a high-level C++ D-Bus library for Linux designed to provide
 expressive, easy-to-use API in modern C++. It adds another layer of
 abstraction on top of sd-bus, a nice, fresh C D-Bus implementation by systemd.
 .
 This package contains development files.

Package: libsdbus-c++-doc
Source: sdbus-cpp
Version: 0.8.3-4
Architecture: all
Maintainer: Shengjing Zhu <zhsj@debian.org>
Installed-Size: 3287
Filename: ./all/libsdbus-c++-doc_0.8.3-4_all.deb
Size: 290678
MD5sum: a45ada205bc27fa377c6340e8c784756
SHA1: 05d2b7dddde24264d55c0cbaaae5feb9fd71dcb8
SHA256: b3bd21b583d02d9d73d3c001b8335cfaa4c7fb9fbde418ea2c79620d4ebff879
Section: doc
Priority: optional
Homepage: https://github.com/Kistler-Group/sdbus-cpp
Description: High-level C++ D-Bus library for Linux in modern C++ (documentation)
 sdbus-c++ is a high-level C++ D-Bus library for Linux designed to provide
 expressive, easy-to-use API in modern C++. It adds another layer of
 abstraction on top of sd-bus, a nice, fresh C D-Bus implementation by systemd.
 .
 This package contains documentation.

Package: libsdbus-c++0
Source: sdbus-cpp
Version: 0.8.3-4
Architecture: amd64
Maintainer: Shengjing Zhu <zhsj@debian.org>
Installed-Size: 198
Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libstdc++6 (>= 11), libsystemd0 (>= 243)
Filename: ./amd64/libsdbus-c++0_0.8.3-4_amd64.deb
Size: 58266
MD5sum: 485f2d8762120a42fbf9fa7c5dca50c7
SHA1: a288f2ee82ce303d0ba093b1ddc441f52fe65c32
SHA256: 5fe32ce6255c5bb018501e7c29ee3337a102612bc12cd8d715bcab5eca8f2a75
Section: libs
Priority: optional
Homepage: https://github.com/Kistler-Group/sdbus-cpp
Description: High-level C++ D-Bus library for Linux in modern C++ (library)
 sdbus-c++ is a high-level C++ D-Bus library for Linux designed to provide
 expressive, easy-to-use API in modern C++. It adds another layer of
 abstraction on top of sd-bus, a nice, fresh C D-Bus implementation by systemd.
 .
 This package contains library.

Package: python3-bcc
Source: bcc
Version: 0.24.0-4
Architecture: all
Maintainer: Brenden Blanco <bblanco@plumgrid.com>
Installed-Size: 209
Depends: libbcc (= 0.24.0-4), python3, binutils
Conflicts: python3-bpfcc
Provides: python3-bpfcc
Filename: ./all/python3-bcc_0.24.0-4_all.deb
Size: 42226
MD5sum: b581dc605213e209e22a493191aef875
SHA1: b3011a7ff573378a974dc6c1179a99f873eab374
SHA256: 812f7671434d4dfc4ad75262c48d069751c2c04804cc9db3e06396a720d1d64d
Section: misc
Priority: optional
Homepage: https://github.com/iovisor/bcc
Description: Python3 wrappers for BPF Compiler Collection (BCC)