
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
An implementation of HTTP Negotiate authentication (RFC 4559) for requests.
Negotiate authentication is commonly used to provide Kerberos authentication through GSSAPI.
Here's a trivial example:
import requests
import requests_negotiate
auth = requests_negotiate.HTTPNegotiateAuth()
response = requests.get('https://example.org/', auth=auth)
You'll need a valid Kerberos ticket - acquired using e.g. kinit
- for this to work.
You can instantiate an HTTPNegotiateAuth
with the following optional parameters:
service
- A Kerberos principal is generally composed of a service name (e.g. 'HTTP') and a hostname, separated by a slash ('/'). This lets you override the default service of 'HTTP'
.service_name
- Overrides the full service name (e.g. 'HTTP/example.org'
)negotiate_client_name
- Explicitly specify which client principal to authenticate as. Particularly useful when you're using a credential cache collection.FAQs
Negotiate authentication for the requests HTTP client library
We found that requests-negotiate demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.