Package: azure-kms-pkcs11 Version: 0.0.0-3 Architecture: arm64 Maintainer: Jeremi Piotrowski Installed-Size: 978 Depends: libc6 (>= 2.34), libcurl4 (>= 7.18.2), libgcc-s1 (>= 3.0), libjson-c5 (>= 0.15), libssl3 (>= 3.0.0), libstdc++6 (>= 11) Filename: arm64/azure-kms-pkcs11_0.0.0-3_arm64.deb Size: 277584 MD5sum: b3cb8ffcb0c3ccd48913eb556abb820e SHA1: b576dd9cae3d6a70d705534d22644d5b3b754da7 SHA256: 4232e4ff71b9d62d3d3fe572c367919ed2e40574f7a10f5c428c3b7585746eab Section: misc Priority: extra Package: azure-kms-pkcs11 Version: 0.0.0-3 Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 1054 Depends: libc6 (>= 2.34), libcurl4 (>= 7.18.2), libgcc-s1 (>= 3.0), libjson-c5 (>= 0.15), libssl3 (>= 3.0.0), libstdc++6 (>= 11) Filename: amd64/azure-kms-pkcs11_0.0.0-3_amd64.deb Size: 317244 MD5sum: 21c148cd292afc194de897692f7fcb57 SHA1: 1d5fe3f99b682a7ff5ac9553d363313f54ca6f44 SHA256: 9d40bb7dd7218ca50afc9c7dea6afc2f59afca20b4a6e0c6ad6c17f65181b3e1 Section: misc Priority: extra Package: azure-kms-pkcs11-dbgsym Source: azure-kms-pkcs11 Version: 0.0.0-3 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Jeremi Piotrowski Installed-Size: 1265 Depends: azure-kms-pkcs11 (= 0.0.0-3) Filename: arm64/azure-kms-pkcs11-dbgsym_0.0.0-3_arm64.deb Size: 976468 MD5sum: b42ec982cccde7db6ff51c443f508a4f SHA1: c605e993eaf0250b7fe3dd46361848e55d8b00ba SHA256: 1f5dc9e799d456906a4a70c6720ec46de6d356c046ed929223ea555402f49ee8 Section: debug Priority: optional Description: debug symbols for azure-kms-pkcs11 Build-Ids: 95f6c5a911a70471cccecbf562c6c5ff4584d498 Package: azure-kms-pkcs11-dbgsym Source: azure-kms-pkcs11 Version: 0.0.0-3 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 1278 Depends: azure-kms-pkcs11 (= 0.0.0-3) Filename: amd64/azure-kms-pkcs11-dbgsym_0.0.0-3_amd64.deb Size: 990796 MD5sum: 43583e5633802e4c9345e227e210d88c SHA1: d443f3c8f1c3d960b1a18de8ae680362b3754a3b SHA256: 928cf7ebec798cff198273249b7b323b31546adfbe983bbb11c52362ea047706 Section: debug Priority: optional Description: debug symbols for azure-kms-pkcs11 Build-Ids: 905d2b39c48b1955415260d08610c9d39038615b Package: azure-sdk-for-cpp Version: 0.0.0-4 Architecture: arm64 Maintainer: Jeremi Piotrowski Installed-Size: 7 Filename: arm64/azure-sdk-for-cpp_0.0.0-4_arm64.deb Size: 1180 MD5sum: 3a68b4fb5db3f112cbf419f1e4fa8477 SHA1: 1815bfa45a442cea848ea6b43ec9708dc01f407e SHA256: c5cb3031104ad61ec591b0cb1983a4a357f7e997bb2f872de86baa7acd5da569 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 Version: 0.0.0-4 Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 7 Filename: amd64/azure-sdk-for-cpp_0.0.0-4_amd64.deb Size: 1180 MD5sum: c67e61e283659aa3d365df0627669875 SHA1: 8d5b6df089ea26866131d7ffb6749bb0584bafcf SHA256: da330cd17f8937160a10275aef59f1e08f023a3ac8997e96caa2bd8da92a7732 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: arm64 Maintainer: Jeremi Piotrowski Installed-Size: 18821 Depends: azure-sdk-for-cpp (= 0.0.0-4), libcurl4-openssl-dev, libssl-dev, libxml2-dev Filename: arm64/azure-sdk-for-cpp-dev_0.0.0-4_arm64.deb Size: 1719388 MD5sum: 6c1c2b10afc549356b3f3f0746811861 SHA1: 69823c81fd11391313a8a7a6899c6c24ac9b7600 SHA256: b19180527148eef27df3bf3dd7a7ea68ae937a51a69558bd5d437443f26c50fd 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-sdk-for-cpp-dev Source: azure-sdk-for-cpp Version: 0.0.0-4 Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 19257 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: 1793312 MD5sum: a011daa1001ad9dea5219ecd1884dc54 SHA1: 8e57f4ff584a678c84360da03ca551a48e174f22 SHA256: ed292dd3a1c7334fd4455af007845e0b89f1c90aa3917a167e1b5767e9987f4d 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: arm64 Maintainer: Debian Go Packaging Team Installed-Size: 19030 Depends: libc6 (>= 2.34) Built-Using: go-md2man-v2 (= 2.0.4-1), golang-1.23 (= 1.23.4-1), golang-blackfriday-v2 (= 2.1.0-1), golang-github-azure-azure-pipeline-go (= 0.2.3-1), 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~git20210331.41bb18b-1), golang-github-golang-jwt-jwt (= 4.3.0+git20220210.279dd19-1), golang-github-golang-protobuf-1-5 (= 1.5.4-1), golang-github-google-uuid (= 1.6.0-1), golang-github-googleapis-gax-go (= 2.13.0-1), golang-github-jeffreyrichter-enum (= 0.0~git20180725.2567042-1), golang-github-klauspost-cpuid (= 2.2.9-1), golang-github-mattn-go-ieproxy (= 0.0.9-1), golang-github-minio-minio-go (= 6.0.53-1), golang-github-minio-sha256-simd (= 1.0.1-1), golang-github-mitchellh-go-homedir (= 1.1.0-1), golang-github-pkg-errors (= 0.9.1-3), golang-github-spf13-cobra (= 1.8.1-1), golang-github-spf13-pflag (= 1.0.6~git20210604-d5e0c0615ace-1), golang-github-wastore-keyctl (= 0.3.1-1), golang-go.crypto (= 1:0.25.0-1), golang-go.opencensus (= 0.24.0-2), golang-golang-x-net (= 1:0.27.0-1), golang-golang-x-oauth2 (= 0.15.0-1), golang-golang-x-sync (= 0.7.0-1), golang-golang-x-sys (= 0.22.0-1), golang-golang-x-text (= 0.16.0-1), golang-google-api (= 0.61.0-5), golang-google-cloud (= 0.56.0-5), golang-google-genproto (= 0.0~git20210726.e7812ac-4), golang-google-grpc (= 1.64.0-6), golang-google-protobuf (= 1.33.0-1), golang-gopkg-ini.v1 (= 1.67.0-1), golang-gopkg-yaml.v3 (= 3.0.1-3) Filename: arm64/azure-storage-azcopy_10.14.1-1_arm64.deb Size: 4668272 MD5sum: 98efbf0877d8e654bfbd3d340b73c9f3 SHA1: 0a8203b6ba524aae650d3bc88a5af7db1553222a SHA256: d2866197d7b356cb7cb12c7780cbc6630224668d34e33eb92799bcef3a4146c0 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: azure-storage-azcopy Version: 10.14.1-1 Architecture: amd64 Maintainer: Debian Go Packaging Team Installed-Size: 19978 Depends: libc6 (>= 2.34) Built-Using: go-md2man-v2 (= 2.0.4-1), golang-1.23 (= 1.23.4-1), golang-blackfriday-v2 (= 2.1.0-1), golang-github-azure-azure-pipeline-go (= 0.2.3-1), 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~git20210331.41bb18b-1), golang-github-golang-jwt-jwt (= 4.3.0+git20220210.279dd19-1), golang-github-golang-protobuf-1-5 (= 1.5.4-1), golang-github-google-uuid (= 1.6.0-1), golang-github-googleapis-gax-go (= 2.13.0-1), golang-github-jeffreyrichter-enum (= 0.0~git20180725.2567042-1), golang-github-klauspost-cpuid (= 2.2.9-1), golang-github-mattn-go-ieproxy (= 0.0.9-1), golang-github-minio-minio-go (= 6.0.53-1), golang-github-minio-sha256-simd (= 1.0.1-1), golang-github-mitchellh-go-homedir (= 1.1.0-1), golang-github-pkg-errors (= 0.9.1-3), golang-github-spf13-cobra (= 1.8.1-1), golang-github-spf13-pflag (= 1.0.6~git20210604-d5e0c0615ace-1), golang-github-wastore-keyctl (= 0.3.1-1), golang-go.crypto (= 1:0.25.0-1), golang-go.opencensus (= 0.24.0-2), golang-golang-x-net (= 1:0.27.0-1), golang-golang-x-oauth2 (= 0.15.0-1), golang-golang-x-sync (= 0.7.0-1), golang-golang-x-sys (= 0.22.0-1), golang-golang-x-text (= 0.16.0-1), golang-google-api (= 0.61.0-5), golang-google-cloud (= 0.56.0-5), golang-google-genproto (= 0.0~git20210726.e7812ac-4), golang-google-grpc (= 1.64.0-6), golang-google-protobuf (= 1.33.0-1), golang-gopkg-ini.v1 (= 1.67.0-1), golang-gopkg-yaml.v3 (= 3.0.1-3) Filename: amd64/azure-storage-azcopy_10.14.1-1_amd64.deb Size: 5399356 MD5sum: 90cca2e2624f0be5297fc19adf669adb SHA1: 1bfd301842822a52659a0d78d6efddcbc5640f26 SHA256: d6196a0db9cfc7f2f421271cef134da2d14e98ae2f6cb6b0fdc5f4a12681ddb3 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: azure-storage-azcopy-dbgsym Source: azure-storage-azcopy Version: 10.14.1-1 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Debian Go Packaging Team Installed-Size: 26545 Depends: azure-storage-azcopy (= 10.14.1-1) Filename: arm64/azure-storage-azcopy-dbgsym_10.14.1-1_arm64.deb Size: 5823172 MD5sum: 38ca529687fb1986683851456558af47 SHA1: 4b3346cfde74385cbe8fa8e9a34c3c4e73e1754b SHA256: d9f121cc5fb1886d05778c72bc556d3385d147e0f25b040832b8121ed57a5b8e Section: debug Priority: optional Description: debug symbols for azure-storage-azcopy Build-Ids: 8040ce5f5a82c4b3a4b5e894d6d8e16bdcfb4bea Package: azure-storage-azcopy-dbgsym Source: azure-storage-azcopy Version: 10.14.1-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Debian Go Packaging Team Installed-Size: 18577 Depends: azure-storage-azcopy (= 10.14.1-1) Filename: amd64/azure-storage-azcopy-dbgsym_10.14.1-1_amd64.deb Size: 6164720 MD5sum: 063bcbad2055dedfaf8a4eb998fb262e SHA1: f32ba548a4037146048f39ebc07f11467c1d2ab2 SHA256: 0e213b521694785d4fb195dd77e9545c3574474a620b035404a3a40e1f03d31a Section: debug Priority: optional Description: debug symbols for azure-storage-azcopy Build-Ids: 2db657ef754fc678c22485eb594dfc79afd43f7a Package: bpfcc-introspection Source: bpfcc Version: 0.24.0+ds-1 Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 88 Depends: libbpf0 (>= 5.2.6), libbpfcc (= 0.24.0+ds-1), libc6 (>= 2.34) Filename: arm64/bpfcc-introspection_0.24.0+ds-1_arm64.deb Size: 13728 MD5sum: 11eb862dcae0bdc28ca42df7c6caeed4 SHA1: 7e63ca6458628be442b67aa94501c27d72be02b6 SHA256: 6060fa316f5481be8530f01acc82aace8d7f937fe2076efc1f882ce68e8e5945 Section: misc Priority: optional Homepage: https://github.com/iovisor/bcc Description: tool to help introspect BPF programs BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides tools to introspect BPF programs. Currently following programs are provided as part of this package. . - bps: Lists all BPF programs loaded into the kernel. `ps` for BPF programs Package: bpfcc-introspection Source: bpfcc Version: 0.24.0+ds-1 Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 40 Depends: libbpf0 (>= 5.2.6), libbpfcc (= 0.24.0+ds-1), libc6 (>= 2.34) Filename: amd64/bpfcc-introspection_0.24.0+ds-1_amd64.deb Size: 13612 MD5sum: 6d7b0088891ac103048a0b8d060b780c SHA1: 5b78bc9af9362750989588c40edce3258203816f SHA256: 49885fa437a5463139f31b446081145bef702243d0384d37f1d43ad64001d505 Section: misc Priority: optional Homepage: https://github.com/iovisor/bcc Description: tool to help introspect BPF programs BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides tools to introspect BPF programs. Currently following programs are provided as part of this package. . - bps: Lists all BPF programs loaded into the kernel. `ps` for BPF programs Package: bpfcc-introspection-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 27 Depends: bpfcc-introspection (= 0.24.0+ds-1) Filename: arm64/bpfcc-introspection-dbgsym_0.24.0+ds-1_arm64.deb Size: 11904 MD5sum: ebf9ebfb45d2301e89a8924baacb4a57 SHA1: 6a29660a08bcbb7cfb315885786a6515bfe4bf6d SHA256: e03c62716711116b870b0561e60c3fd0942488fb362cdda491b86598bc303341 Section: debug Priority: optional Description: debug symbols for bpfcc-introspection Build-Ids: fc340c78a715e14b5f9f217ecb52921914babbf8 Package: bpfcc-introspection-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 26 Depends: bpfcc-introspection (= 0.24.0+ds-1) Filename: amd64/bpfcc-introspection-dbgsym_0.24.0+ds-1_amd64.deb Size: 11464 MD5sum: 3cdf7cfb862f57b09386d91ce9a21578 SHA1: c30486f76b0a628b1b21213a818e2f7004d5d5a5 SHA256: 3fff1d6d993bc823f0d8b5cb664f4b98943c6c069645861bfb67114a4006248a Section: debug Priority: optional Description: debug symbols for bpfcc-introspection Build-Ids: ef06d7ce91e5873eccd602ef7f0a8de41a00d878 Package: bpfcc-lua Source: bpfcc Version: 0.24.0+ds-1 Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 729 Depends: libbpfcc (>= 0.24.0+ds-1), libc6 (>= 2.34), libgcc-s1 (>= 3.3) Filename: amd64/bpfcc-lua_0.24.0+ds-1_amd64.deb Size: 316880 MD5sum: ba3a9351b4a070ec46d341bae7b93c53 SHA1: 4a8d89200d591afc94e89df0c8275c5ed9362651 SHA256: 04850b60536f4d8cfba231d4e65e7b2ba31df07ed1322e919e60730083505c47 Section: misc Priority: optional Homepage: https://github.com/iovisor/bcc Description: Standalone tool to run BCC tracers written in Lua BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the Lua bindings Package: bpfcc-lua-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 83 Depends: bpfcc-lua (= 0.24.0+ds-1) Filename: amd64/bpfcc-lua-dbgsym_0.24.0+ds-1_amd64.deb Size: 22588 MD5sum: 1292176c825a5f91c1d89b577b4d4eef SHA1: 883666c7a84c6c112cd1a1c83fc80fec33ead925 SHA256: 26e89cf832921dd3dfa5f34faf0c80afeba62a1ee7ea652377dda42655d2a361 Section: debug Priority: optional Description: debug symbols for bpfcc-lua Build-Ids: 6ad357944df3d2653c4d141b8c6a54e123c2494a Package: bpfcc-tools Source: bpfcc Version: 0.24.0+ds-1 Architecture: all Maintainer: Ritesh Raj Sarraf Installed-Size: 2637 Depends: python3-bpfcc (>= 0.24.0+ds-1), python3-netaddr, python3:any Filename: all/bpfcc-tools_0.24.0+ds-1_all.deb Size: 685672 MD5sum: 8d54cc04980efc00e383684db71eafb3 SHA1: c54028f4dbedc916beab98b2bfd5fbe578db7f6f SHA256: 05983ebb1be6cb3fb761ca19f75609678682d20947518d1725b55f0ce60b9da0 Section: misc Priority: optional Homepage: https://github.com/iovisor/bcc Description: tools for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the command-line tools and examples Package: cvm-guest-attestation-client Source: cvm-guest-attestation Version: 1.0.3-1 Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 143 Depends: libazguestattestation1, libc6 (>= 2.38), libgcc-s1 (>= 3.0), libstdc++6 (>= 13.1) Filename: amd64/cvm-guest-attestation-client_1.0.3-1_amd64.deb Size: 49016 MD5sum: f0bf15e7d262035fd47c4b8635a4884a SHA1: 2656e7aa3cda4a4ff5a3f43118984c869e554887 SHA256: 3d86f1cba1b4c0ca4ab70a4a63d3cf4e88e718cd6ce1df90aa47130bec609003 Section: misc Priority: optional Description: CVM Attestation Sample App Package: cvm-guest-attestation-client-dbgsym Source: cvm-guest-attestation Version: 1.0.3-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 741 Depends: cvm-guest-attestation-client (= 1.0.3-1) Filename: amd64/cvm-guest-attestation-client-dbgsym_1.0.3-1_amd64.deb Size: 681644 MD5sum: 575854190bf6166c2413e5b83f805206 SHA1: e5c841663ebc5e973ee61d48374aa5d603545416 SHA256: 9769f035749892034400ba4d03b7d3af03ec6daf722eafb4511385d640c00017 Section: debug Priority: optional Description: debug symbols for cvm-guest-attestation-client Build-Ids: a277db40c30052865ed8c8bf4c6f387335530278 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 Installed-Size: 1442 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: 144800 MD5sum: 6723dd849dc5d63b958cf67ddb9b075e SHA1: f5dc70fffeb41683c965a2f5632f6793d8910f89 SHA256: b760d2bc91f45027465a7424261fe310d4b2344f8850e3b78fce0763442f9b2b 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 Installed-Size: 732 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: 95180 MD5sum: ceecc74701702d3233e8259eca12f0b8 SHA1: 2cd7b1cd304049b55b275472334a28f3aff31217 SHA256: 72085096ce4d5129a345994d929cdb67a1abdc39e9a0af1424a161058d3eb1e2 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 Installed-Size: 845 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: 120676 MD5sum: e9c42bb2bc230eb50ecc72fc414a531d SHA1: 62402d1e35d01485f73f1bb8f4707e478022bf6c SHA256: c415bf971d64f38ca0b29b1885971a8ae3f028c7b245863bede18763f6a24e62 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 Installed-Size: 5004 Filename: all/golang-github-golang-jwt-jwt-dev_4.3.0+git20220210.279dd19-1_all.deb Size: 2534820 MD5sum: c022226d1e44098f46d767f34e500192 SHA1: 0ff286ae9bab795be3c5d6390c7cf2e219cf39fe SHA256: c499009cc4eddaac593f4cbe362dd294c69bb98565c2b75088fd5a8ce6c4d792 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 Installed-Size: 43 Filename: all/golang-github-jeffreyrichter-enum-dev_0.0~git20180725.2567042-1_all.deb Size: 8780 MD5sum: 0cfbaa9fa3952feaa43cd19bc4d54f47 SHA1: 6df94fda1a18f68e06eb04965e3c1cf4a460a1ee SHA256: 946fbd84868e6396e68f42e61a9dbd1731eaef5bc17f66416841932181917ee2 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 Installed-Size: 36 Filename: all/golang-github-wastore-keyctl-dev_0.3.1-1_all.deb Size: 6400 MD5sum: 233b14653ae8ae219841e565238890c5 SHA1: 76707a86be1b572e15508c2d0c14b2794f14ce4f SHA256: e48f9b431da691b038bf54bef931f8bc02c93f8fbb43a0fe0b6679a6db0d6d0c 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 Installed-Size: 10 Filename: amd64/libazguestattestation-dev_1.0.3-1_amd64.deb Size: 1180 MD5sum: 177f52428f1b0afb4e401a16f89acfd5 SHA1: 0d2ecbf793758d37fc7622f9f9873a98f74fe3b9 SHA256: 9a32c9ecc7deda1dfec8981f5413cb96a324bee9ddff61fa32a279726b3801af Section: misc Priority: optional Description: CVM Attestation Library Package: libazguestattestation1 Source: cvm-guest-attestation Version: 1.0.3-1 Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 499 Depends: libc6 (>= 2.38), libcurl4t64 (>= 7.16.2), libgcc-s1 (>= 3.0), libssl3t64 (>= 3.0.0), libstdc++6 (>= 14), libtss2-esys-3.0.2-0t64 (>= 2.3.1), libtss2-mu-4.0.1-0t64 (>= 3.0.1), libtss2-tcti-device0t64 (>= 3.0.1) Filename: amd64/libazguestattestation1_1.0.3-1_amd64.deb Size: 159724 MD5sum: e8a2c2df2b2aa8eb8868611fd65a873d SHA1: de6852eed2cfa577f44e9c41dfdd7d6daa4aa74e SHA256: 6b4125f4e7ef91d4bee27d5aa3e78ad3cf26170f49c1fcc45760ad49a86a430c Section: misc Priority: optional Description: CVM Attestation Library Package: libazguestattestation1-dbgsym Source: cvm-guest-attestation Version: 1.0.3-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Jeremi Piotrowski Installed-Size: 2241 Depends: libazguestattestation1 (= 1.0.3-1) Filename: amd64/libazguestattestation1-dbgsym_1.0.3-1_amd64.deb Size: 2199572 MD5sum: 5a974c9cd1ebc931989a877d31791995 SHA1: c1548dd91aa277a538de02882a47590e4eff58ea SHA256: a1baffa8c26250c885bdcca9fa1ef4f08b7ed9f617a43c3a523a832c09b2f920 Section: debug Priority: optional Description: debug symbols for libazguestattestation1 Build-Ids: 9f2b77b5f18d5a26ee1229e77e19ff700b34c77c Package: libbpf-tools Source: bpfcc Version: 0.24.0+ds-1 Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 13882 Depends: libc6 (>= 2.34), libelf1 (>= 0.144), zlib1g (>= 1:1.2.3.3) Filename: arm64/libbpf-tools_0.24.0+ds-1_arm64.deb Size: 895932 MD5sum: b6de43ff640251c43c189ef8eefc2ff7 SHA1: 2376b2af478656c9866081915060ac2ee0756785 SHA256: bd4262fe1accd2ff7c744ca15a9c100843a24d567936723dd464ad92b69ee0e3 Section: misc Priority: optional Homepage: https://github.com/iovisor/bcc Description: tools for BPF Compiler Collection based on libbpf (BTF and CO-RE) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the tools from bpfcc-tools but written in a portable fashion using BTF and libbpf hence the installation footprint will be smaller compared to bpfcc-tools. . At this time this package contains subset of tools from bpfcc-tools Package: libbpf-tools Source: bpfcc Version: 0.24.0+ds-1 Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 13473 Depends: libc6 (>= 2.34), libelf1 (>= 0.144), zlib1g (>= 1:1.2.3.3) Filename: amd64/libbpf-tools_0.24.0+ds-1_amd64.deb Size: 972436 MD5sum: f30ce99b471769b3c1ec54b5a6c1436a SHA1: b7bae8a7b51a5c8477d6ec785eb6d9ef5775bccd SHA256: e191085f2e1205808407ba2fd112e597d8731ec4b852d359082bc3a9a7ec0df2 Section: misc Priority: optional Homepage: https://github.com/iovisor/bcc Description: tools for BPF Compiler Collection based on libbpf (BTF and CO-RE) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the tools from bpfcc-tools but written in a portable fashion using BTF and libbpf hence the installation footprint will be smaller compared to bpfcc-tools. . At this time this package contains subset of tools from bpfcc-tools Package: libbpf-tools-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 2751 Depends: libbpf-tools (= 0.24.0+ds-1) Filename: arm64/libbpf-tools-dbgsym_0.24.0+ds-1_arm64.deb Size: 1110292 MD5sum: baa147b060ea6482ad8b18b2e5d2d3ff SHA1: baa16ed15a962e57adc182cf3444a9ab44c0e57b SHA256: 410c69f7137e8b05a10a6fd7e9355613d48064c69395ca2b019c2ce7298a6783 Section: debug Priority: optional Description: debug symbols for libbpf-tools Build-Ids: 015c89e35f47d0f56b5c4885a3a71f4e167fc16f 03003e0aa1e9092fbdb058c160dc6e998770d6db 04cd7506e592fedce1b0eb625bc457c313d2a892 0c4dd117eceaff9ed163db0e5900654f3291b8a9 13b5d0bfe1859130dbf92158ec2ca2bfb248923a 192c8c968969780adda36d54cf0540069770a1f0 1bca24822ae67ff21705a4ca14ff3e1cca43df83 1c84ce82842314e7f4d0bc868834f29c758a3f5f 1e283694c9102a6017bbbac38a5ea123eef52bdf 2a82c35475ad9fea36c1ee47a050d354bd15a363 2eac821e9d19067d57533f33b1da1f6545336994 4cab7f00ff08bc61fcbfe9cc444280a56596ef11 4d00eba9588099435092c57e9675c431eee163a8 4f7bc466071caaeaec64cacece9bd2a554080a39 6498c6b49c589949ca90ca3749acda77c37662c4 67d5f9750935485d366f75de78c2e45f97e6c24c 6b1318bb6c62c190190c384902f8917a243a8f97 6c7bdd67869dece669640f69a7d846b9b7367dd7 6d8d318e07338546d2692d8be08e3abd1b4a356a 7512ea95a59479aacea8e96df2bf9cee133a369a 77f0edc6f588e81721fca377365e7b5bfbf41ba0 7c64af6274a066eb2140b7308d10ba8011fac6c2 82d2cdc6cb28eaadc834de5d18546a008b780a70 850df5bafe2962ec7ee56e446fe0eb99b69bd154 8a39085e5998aee8015486cb183e9ff7203315ca 99f8b5c61609db6d63c303c1ff5a9fa10c687d75 9da83b736967aae53484dc8081fbcfe50bdf3321 a330e5f77401c212b0fb61c0320c165f0a0c5b2e a3b6a4eb47a1603975b458d3d433f8f16f0464bb a50ead69d941a16b6f85a188c3bf9bc85970eed0 a8ebe6309d4371c593f0a21545c0f85985c07665 b51c0a5193b0c457cf103ccdc987a8f839e703c1 b7fd9ed3bc065ec2dbef6b9b1a236352bc1a1e8e d6b721a576ac68c299a5f302c0e179582a21b7ea dc229c1715eb60ab6b0a4422bfbf2d883004f411 df43a9dab78e5595090dad3ac39eebfeb2a9bb15 ecf939cd7182d11b4ed67aefdd69ca9a99f3988f f2b30029359f528eaac3a032de245a4ac2025204 f384b80cba0d27d180bc0679130abbdd8f5090e3 Package: libbpf-tools-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 2695 Depends: libbpf-tools (= 0.24.0+ds-1) Filename: amd64/libbpf-tools-dbgsym_0.24.0+ds-1_amd64.deb Size: 1158868 MD5sum: 2f10541fddee1e856c2a4b16b78e3109 SHA1: 755e45e637d61e8d44a1bd2400a9a36afae60feb SHA256: 9a7938ede986983e58c53c50f4e57184dbb9ae3ab8d72d0b7b892def3c5a11ef Section: debug Priority: optional Description: debug symbols for libbpf-tools Build-Ids: 06cbe0a98e2e373eb93db42e6ffd84c77ad366b6 08085070e4c7d60e087d3f8152f773d8d6bb3c17 0b25d2c29f536cb767867b81adfa4a9fceb02eec 0cdfd95c03405f7f6dff597c087bed9e49beab75 13407d3e773f5c6682cbf54f0b4b8b4c090093df 14e1d1a3196c9d6a806abd16aa7e409017625e42 1f5814172fb133739ea27b61d454e184bbecced6 20b4406e603cf6f3133f525a32e6aef9e9816840 2cd5dc9a8bdc9ea84ec4c0b2d77c071f6f623246 340a5f36b7d5b658b11d70af00acedd68f5a8a78 373aeda60a53fa88ce034fb4289e65fb5bfe18ab 55b3eeb1f01ad2b003985d43006a4be566cb9e2e 56778c6b1c850b386bc9829e7e36cf95f875dbe1 56d9200b9cd4c1ea26ddbe4c9682a6107b3a27f6 5ae82588bcdbe2ddd1585322065853ebe10e0477 5b9e21d1b83cf7c9778bcd786dce7ad117d2e098 733de2cef3cfdd19a3cfee7d0db5a6e645264acf 77751c4dbeb5b837b5215dcbaafb1a01730e1e51 84893c0da01b5553b6084a4c5765cd3953d9a4aa 853fb31b3204b3e475cfb1cb741bd61164130428 8d0916ed6bed4ae950523bfe250ab5d469c0851e 8ed38893133da8f133b270c9758f45c67e23f3a0 9d4c0e8c76c687a276a4fe9fa7ec1bf7e6e1800b a5f4c1fb5f3b641841a7dba4e13d785ee24dde99 a62e6703bde6067d9d3a6339c30a084579ffbd00 aaa2c41090943dbe29d63b6ff12b575850031636 bcb527ffd4a9248c6cecdf3137aaecc594b1c547 c007a55b5400aa0840679602e82ce03f64ae7d3a c23f0fc025f1281f80aeee487fc2279bec85a4f9 ca21ba21479db707d9773af5b3a94fa4900c50bc ca4dd732e1c21d17b02733d8a6dca8a6e5527a75 d5839d62c1cc3c9b68f2dae1a890fb3d4c6ee2b9 d68e2478b9ed7d6f35e9b40e09e4197c78efeeea d7d0a27e1a266e4508429210c15dc93bae42adef e49d647047ba8798b8082d7be6759aabc1ce5b37 e7882f3ba1f73bf3c49e96a6c7cb00f05ae43661 f98c552170fe51412c88e2127572487277218a0e faea599dd406f1546d357676b0253f52ba113ac7 ff23c378dda930bd4998e8d5b8275ca6e7062cc4 Package: libbpfcc Source: bpfcc Version: 0.24.0+ds-1 Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 3784 Depends: libbpf0 (>= 1:0.6.0), libc6 (>= 2.34), libclang-cpp14 (>= 1:14.0.6), libelf1 (>= 0.144), libgcc-s1 (>= 3.0), libllvm14, libstdc++6 (>= 11) Filename: arm64/libbpfcc_0.24.0+ds-1_arm64.deb Size: 593732 MD5sum: 42c8564177634f4ad38bf96366943c6d SHA1: e7f07781fa1b432790b15aea8649dac45f23a7a8 SHA256: 1d18a79e646d2a01dbe9bdf274a40a7381012b6335a1422b3cd28642040250e8 Section: misc Priority: optional Multi-Arch: same Homepage: https://github.com/iovisor/bcc Description: shared library for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the shared library for BPF Compiler Collection to control BPF programs from userspace. Package: libbpfcc Source: bpfcc Version: 0.24.0+ds-1 Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 3708 Depends: libbpf0 (>= 1:0.6.0), libc6 (>= 2.34), libclang-cpp14 (>= 1:14.0.6), libelf1 (>= 0.144), libgcc-s1 (>= 3.0), libllvm14, libstdc++6 (>= 11) Filename: amd64/libbpfcc_0.24.0+ds-1_amd64.deb Size: 657120 MD5sum: 495ba21e5703b6f0fab3cb1113c00240 SHA1: 615f828e2b74a51c37a398f592040f04f399a771 SHA256: 6ff89795d6b2649e510ed20fbb5f79a415c2f3d28da006a2a760275440915d5e Section: misc Priority: optional Multi-Arch: same Homepage: https://github.com/iovisor/bcc Description: shared library for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the shared library for BPF Compiler Collection to control BPF programs from userspace. Package: libbpfcc-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 16933 Depends: libbpfcc (= 0.24.0+ds-1) Filename: arm64/libbpfcc-dbgsym_0.24.0+ds-1_arm64.deb Size: 16240012 MD5sum: e563fcb18243bcb983389d64f6b13718 SHA1: 556afda6f54798fac76c4d17c222557712921c7c SHA256: 99b871d8e91b025e7b68533d9abd7516fbd97e5ae50d743ccb8580d70b76edf3 Section: debug Priority: optional Multi-Arch: same Description: debug symbols for libbpfcc Build-Ids: 331488361c7e1cdf8def5c5c23f7771bd30a1307 8f1a13a496dec9a771ddf446f30fcb2a366eed5e Package: libbpfcc-dbgsym Source: bpfcc Version: 0.24.0+ds-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 17074 Depends: libbpfcc (= 0.24.0+ds-1) Filename: amd64/libbpfcc-dbgsym_0.24.0+ds-1_amd64.deb Size: 16466200 MD5sum: 0ea47da3fd606c985c33b726f46ebcef SHA1: 60bc118dc4193c701d1914fa8feacd92c4c975e5 SHA256: 58a7fdab891cc573ec0b033423f53b30efea47e4a85790d377250a1ae8e76562 Section: debug Priority: optional Multi-Arch: same Description: debug symbols for libbpfcc Build-Ids: 577e352209aca1f2beb09b13df314586098546d9 cca7c349ba4ec7d049fb54bcbf2bc5102ad72bc3 Package: libbpfcc-dev Source: bpfcc Version: 0.24.0+ds-1 Architecture: arm64 Maintainer: Ritesh Raj Sarraf Installed-Size: 3520 Depends: libbpfcc (= 0.24.0+ds-1) Filename: arm64/libbpfcc-dev_0.24.0+ds-1_arm64.deb Size: 351996 MD5sum: 52946c1a609b4c34a0a05c551b016fde SHA1: 7561eed925e4fdc40d3640eeccfadeb6c457af48 SHA256: 5fc0a8964dfc11e819a6e3df1c58a24299c0ff5708de2c4d1810a8a6c08fd3b5 Section: libdevel Priority: optional Multi-Arch: same Homepage: https://github.com/iovisor/bcc Description: shared library for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the development headers for BPF Compiler Collection Package: libbpfcc-dev Source: bpfcc Version: 0.24.0+ds-1 Architecture: amd64 Maintainer: Ritesh Raj Sarraf Installed-Size: 3500 Depends: libbpfcc (= 0.24.0+ds-1) Filename: amd64/libbpfcc-dev_0.24.0+ds-1_amd64.deb Size: 364312 MD5sum: cadc868aaf60b6a160e4fb1d0dc13a06 SHA1: 2408ca39eaae473be4bf2ffa892922f8ee05dd00 SHA256: dddbb550abbef6ac9817376432234f690bda0964908261be7773bf435706dee2 Section: libdevel Priority: optional Multi-Arch: same Homepage: https://github.com/iovisor/bcc Description: shared library for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the development headers for BPF Compiler Collection Package: libsdbus-c++-bin Source: sdbus-cpp Version: 0.8.3-4 Architecture: arm64 Maintainer: Shengjing Zhu Installed-Size: 209 Depends: libc6 (>= 2.34), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.0), libstdc++6 (>= 13.1) Filename: arm64/libsdbus-c++-bin_0.8.3-4_arm64.deb Size: 52152 MD5sum: e136875d31d78ec222d0c845bd5f020d SHA1: bc5f106cb71f43b46885726e9752e74078d2ab28 SHA256: 12f05f655405e1b1efe82333823d9137beb2c40270baefb6c61ac234596feed2 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++-bin Source: sdbus-cpp Version: 0.8.3-4 Architecture: amd64 Maintainer: Shengjing Zhu Installed-Size: 185 Depends: libc6 (>= 2.34), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.0), libstdc++6 (>= 13.1) Filename: amd64/libsdbus-c++-bin_0.8.3-4_amd64.deb Size: 62288 MD5sum: c6059a2cf0453677b012aaf19be3c691 SHA1: a9b7c63be009485b01cd1b040e2439fdb9f2a3d1 SHA256: a7e973bad5b25dec2872ea0d98a18ea018045684fc137c24f91b875298707436 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++-bin-dbgsym Source: sdbus-cpp Version: 0.8.3-4 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Shengjing Zhu Installed-Size: 883 Depends: libsdbus-c++-bin (= 0.8.3-4) Filename: arm64/libsdbus-c++-bin-dbgsym_0.8.3-4_arm64.deb Size: 744600 MD5sum: 388c2c3d0a038c338e329e1cd4cdb012 SHA1: 0864f12efe559741a7ceda673723ab56cedf8007 SHA256: b4ba600793083edcd8babbe9b8fa30150744c1fddc0555409c171cced9549eab Section: debug Priority: optional Description: debug symbols for libsdbus-c++-bin Build-Ids: 393f1d70959b0329759e4f82e8df57e9ef4d7802 Package: libsdbus-c++-bin-dbgsym Source: sdbus-cpp Version: 0.8.3-4 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Shengjing Zhu Installed-Size: 801 Depends: libsdbus-c++-bin (= 0.8.3-4) Filename: amd64/libsdbus-c++-bin-dbgsym_0.8.3-4_amd64.deb Size: 769764 MD5sum: d8601538da053991eab6fe96552a3d11 SHA1: 1b21e7ea0fef1abf2b3e1aec55720672c7a10bc6 SHA256: 41e158155505c290fdda2144d1379077533714fcd4975f7eb4ad1a6c0ba2fa9a Section: debug Priority: optional Description: debug symbols for libsdbus-c++-bin Build-Ids: 33a7d56aa442035dc16deedb8dd7acd92e1907f3 Package: libsdbus-c++-dev Source: sdbus-cpp Version: 0.8.3-4 Architecture: arm64 Maintainer: Shengjing Zhu Installed-Size: 189 Depends: libsdbus-c++-bin (= 0.8.3-4), libsdbus-c++0 (= 0.8.3-4) Filename: arm64/libsdbus-c++-dev_0.8.3-4_arm64.deb Size: 27620 MD5sum: 2cfb1ab408dac712ee3535f8f4f499df SHA1: 7df235a31bf2cf3acbddb487c1f14a36a40f6833 SHA256: 3e59c4ee484fcb67d077c058cf2988dcd26e391e3b838153c08cca55ad8a8404 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++-dev Source: sdbus-cpp Version: 0.8.3-4 Architecture: amd64 Maintainer: Shengjing Zhu Installed-Size: 189 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: 27624 MD5sum: 328d30385df69c30941b5fc6df8a0a7d SHA1: 0b9edfc953b1adc5a0db4d1614b49ba84e2281b9 SHA256: 2d1d776c1e674971bb84684fa644ce9887380dba892526e5f9a3e4ebae921606 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 Installed-Size: 3302 Filename: all/libsdbus-c++-doc_0.8.3-4_all.deb Size: 291676 MD5sum: 9150eba791147933a686b3abb46f390b SHA1: 7d08eee98189685d6c126da418779558d236bfeb SHA256: 72f2e9b9e65809a64d90cb8cf712def225616343cda9aacfb67fb712ca94b79e 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: arm64 Maintainer: Shengjing Zhu Installed-Size: 214 Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.0), libstdc++6 (>= 12), libsystemd0 (>= 243) Filename: arm64/libsdbus-c++0_0.8.3-4_arm64.deb Size: 51572 MD5sum: c5b7a88d40f363425398ac018ea6fb5b SHA1: df2f514892b00268894e36a33108b73a78fb8284 SHA256: 47b23ddd9ad098cb952f7798d192b87552c57df63e8df255805f7beec725939c 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: libsdbus-c++0 Source: sdbus-cpp Version: 0.8.3-4 Architecture: amd64 Maintainer: Shengjing Zhu Installed-Size: 214 Depends: libc6 (>= 2.34), libgcc-s1 (>= 3.0), libstdc++6 (>= 12), libsystemd0 (>= 243) Filename: amd64/libsdbus-c++0_0.8.3-4_amd64.deb Size: 59128 MD5sum: a34036c06997ce6f07fe26542058099c SHA1: 9fe8cf0f40801b927c82a6dcab819e16bc1ac36c SHA256: bde02a48c0d8dbcc06a795dcc42f436430216bc512fa98cb38465e7abef49447 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: libsdbus-c++0-dbgsym Source: sdbus-cpp Version: 0.8.3-4 Auto-Built-Package: debug-symbols Architecture: arm64 Maintainer: Shengjing Zhu Installed-Size: 779 Depends: libsdbus-c++0 (= 0.8.3-4) Filename: arm64/libsdbus-c++0-dbgsym_0.8.3-4_arm64.deb Size: 734216 MD5sum: b3e66de4f412d048b6fa251ec5c6fff1 SHA1: 39a9afe92543dcc802cab26ef4ef967b1d3b260a SHA256: b967343322431a569cc7866e2ed937a0f6be9aeea4444bdf2ed1806bbc07bc0f Section: debug Priority: optional Description: debug symbols for libsdbus-c++0 Build-Ids: 32c1397a3d95cbdd2c24118f10267b0994df1a10 Package: libsdbus-c++0-dbgsym Source: sdbus-cpp Version: 0.8.3-4 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Shengjing Zhu Installed-Size: 807 Depends: libsdbus-c++0 (= 0.8.3-4) Filename: amd64/libsdbus-c++0-dbgsym_0.8.3-4_amd64.deb Size: 751272 MD5sum: de06df9b3c87e0f3a8f51bcd788544fc SHA1: 90366e19c545cf5b3ae5a7bcb13a221a8c131dca SHA256: 442debedf93676a87e51513584be5540d84b586df452262031d755856838c785 Section: debug Priority: optional Description: debug symbols for libsdbus-c++0 Build-Ids: 85b953592217178d1ef05931b5fe36ecb87c9982 Package: python3-bpfcc Source: bpfcc Version: 0.24.0+ds-1 Architecture: all Maintainer: Ritesh Raj Sarraf Installed-Size: 215 Depends: libbpfcc (>= 0.24.0+ds-1), python3:any Filename: all/python3-bpfcc_0.24.0+ds-1_all.deb Size: 43740 MD5sum: 1595c58955c37f131596a1322b1d5053 SHA1: 95a5ce01707bd13db4bbad976c68ed8d60ed9ff5 SHA256: c22de5d3cc298658c07491a30d2c4222e9292caec47a74a6daa8c236b753ded1 Section: python Priority: optional Homepage: https://github.com/iovisor/bcc Description: Python 3 wrappers for BPF Compiler Collection (BCC) BPF Compiler Collection (BCC) is a toolkit for creating efficient kernel tracing and manipulation programs . It makes use of extended BPF (Berkeley Package Filter) and provides tools for BPF based Linux IO analysis, networking, monitoring and more . This package provides the Python 3 bindings