azure-sdk-for-cpp
azure-sdk-for-cpp copied to clipboard
Azure
This repository is for active development of the Azure SDK for C++. For consumers of the SDK we recommend visiting our versioned developer docs at https://azure.github.io/azure-sdk-for-cpp.
The user-input data here is not being encoded. https://github.com/Azure/azure-sdk-for-cpp/blob/c152c05d4a56074d20451b7efa483bbf17bef116/sdk/keyvault/azure-security-keyvault-keys/src/key_client.cpp#L478-L479 We should audit other places that might have this issue. For example, in golang, they are encoded: https://github.com/Azure/azure-sdk-for-go/blob/37f3c8dd2e9bafb7b6bf9aabb0795e753038928d/sdk/keyvault/azkeys/client.go#L276-L277
The RFC specifies which characters in a query parameter can be left unencoded. https://www.rfc-editor.org/rfc/rfc3986#section-3.4 Our current implementation of Encode(), by default, encodes all characters except those that are reserved, and...
**Query/Question** How to get more context info from a logger output? How do I get timestamp and session id printed in the listener output? ***Why is this not a Bug...
Hi Azure team, We are need to using proxy auth (username and password). We found your SDK is not support yet. Could you support this feature for Curl transport? https://github.com/Azure/azure-sdk-for-cpp/blob/main/sdk/core/azure-core/inc/azure/core/http/curl_transport.hpp...
Using `Start-Process` works well enough on Windows but it's not working properly in Linux (even `Start-Process nohup -Arguments @('arg1, ...)`)... There should be a way to do this so that...
We need to update the Key Vault documentation in a few places: - [ ] **Authentication in Samples:** Our samples should show the use of Managed Identity instead of Service...
# Missing TLS options in CURL Http transport - Ability to enable/disable certificate revocation list checks - Ability to specify single trusted certificates. For LibCurl the option seems to accept...
# Add support for HTTP Proxies in the WInHTTP transport. ## Support HTTP proxies ## Support TLS Options in WinHTTP transport.
We want to avoid cases like these in the future, where a GA release depends on beta version of core. Can we come up with an automatic validation step to...
This is a pre-requisite step before enable the credscan in PR validation. Setup a testing scan against the entire repo. Here is the error report: [CredScan result analysis](https://dev.azure.com/azure-sdk/public/_build/results?buildId=1715661&view=logs&j=a129effc-2dd1-54d1-fb5a-ad7bdc0e851d&t=9036d097-2774-5136-505e-b4dc0a37f42d)
