TCP

Open
#42 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell

Research direction

Start by locating the current SSH key-exchange implementation and its tests; the issue names no files or entry points. A complete change would support key exchange over TCP without requiring SSH access, with encryption and authentication requirements defined and verified.

Written by the indexing model from the issue text.

Description

enhancement research

Some SPOs would prefer to not require opening up their node hosts to SSH.

Allowing kes-agent to exchange keys over TCP was suggested,however this would require solving encryption and authentication.

Dominant language
Haskell
Stars
2
Forks
13
PR merge metrics
No merged PRs in 30d

Getting set up

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.

More from IntersectMBO/kes-agent

All issues in IntersectMBO/kes-agent

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.