trufnetwork / trufnetwork/node
Problem: Stakeholders can't login to SSH server using simple login & password
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
Description
Or can we just ssh with login & password?
Can we use Github Environment Variables for that? So it will be part of the build & deploy script, but won't be publicly exposed.
source: https://github.com/truflation/tsn-db/issues/47#issuecomment-1985868504
Note: we currently can login using a predefined keypair from AWS.
Defined here: https://github.com/truflation/tsn-db/blob/a24b3cb1a0ff2097aa46b1c83a14a512f5724613/truflation/infra/cdk_main.go#L140
Note that CDK works by creating a template from code, which exposes environment variables if used in a stack. However, if this resulting file is not accessible at the end of a build step, this won't expose anything.
Contributor guide
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 truflation/infra/cdk_main.go around line 140 and inspect how the AWS SSH keypair is defined and used in the CDK-generated template. Review the referenced issue discussion and determine how password-based login would fit the build and deploy flow without exposing credentials; done means stakeholders can authenticate with a login and password safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github, go
- Domain
- authentication, cloud, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100