-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KES Agent Connectivity #1402
base: main
Are you sure you want to change the base?
KES Agent Connectivity #1402
Conversation
@@ -150,6 +150,7 @@ library | |||
crypton, | |||
deepseq, | |||
formatting >=6.3 && <7.3, | |||
kes-agent, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This dependency cannot work as is, because it builds socket-unix
which won't fly on Windows.
keyThreadAsync <- async | ||
(keyThread set) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do label this thread. This is mandatory in my opinion, see IntersectMBO/cardano-node#6086
@@ -262,20 +265,38 @@ data PraosCanBeLeader c = PraosCanBeLeader | |||
|
|||
data PraosCredentialsSource c | |||
= PraosCredentialsUnsound (OCert.OCert c) (KES.UnsoundPureSignKeyKES (KES c)) | |||
| PraosCredentialsAgent FilePath |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm unsure if this one should use FsPath instead? cc @jorisdral
This reverts commit e1a177e.
This adds KES Agent connectivity to consensus.
To use a KES Agent to source KES SignKeys and OpCerts, the
praosCredentialsSource
in thePraosCanBeLeader
data structure can now be pointed to a domain socket address where it will look for a KES Agent.