linkedin / linkedin/Burrow

Using tls encrypted secrets

Open
#788 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

Hi,

to configure tls, it's possible to use the [tls] section as it's specified in the documentation, something like

    [tls.tlsconfig]
    certfile="/opt/burrow/certs/burrow.crt"
    keyfile="/opt/burrow/certs/burrow.key"
    cafile="/opt/burrow/certs/ca.crt"
    noverify=false

but there are no configurations such as certfileKey, keyfileKey and cafileKey in case these certificates come also encrypted symetrically with a password.

This is just to confirm this and if so, a feature request.

Thanks for this great tool!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Burrow's [tls] configuration handling and the documentation section describing tls.tlsconfig. Review how certfile, keyfile, and cafile are loaded; done means encrypted certificate settings can accept the requested passwords and the supported configuration is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
backend, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.