MagicStack / MagicStack/asyncpg
[Feature Request] Support transport encryption using GSSAPI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
In addition to using GSSAPI for authentication, [Postgres supports using GSSAPI for channel encryption](https://www.postgresql.org/docs/current/gssapi-enc.html) as an alternative to TLS with certs. I find this pairs well when also using GSSAPI for authentication.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked PostgreSQL GSSAPI encryption documentation and asyncpg's existing GSSAPI authentication path. Identify the connection and configuration entry points involved, then define coverage for encrypted GSSAPI connections used alongside authentication. Done means the feature works against PostgreSQL and its behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100