frereth.cp.server.state — com.frereth/cp 0.0.3-g3b13aae

Managing CurveCP server state

alter-client-state clj

(alter-client-state state altered-client)

configure-shared-secrets clj

(configure-shared-secrets client client-short-pk server-short-sk)

Return altered client state that reflects new shared key This almost corresponds to lines 369-371 in reference implementation, but does not have side-effects! <----

find-client clj

(find-client state client-short-key)

handle-key-rotation clj

(handle-key-rotation {:keys [:frereth.cp.server.state/cookie-cutter]
                      log-state :frereth.weald.specs/state
                      :as state})

Doing it this way means that state changes are only seen locally

They really need to propagate back up to the System that owns the Component.

It seems obvious that this state should go into an atom, or possibly an agent so other pieces can see it.

But this is very similar to the kinds of state management issues that Om and Om next are trying to solve. So that approach might not be as obvious as it seems at first.

hide-secrets! clj

(hide-secrets! {log-state :frereth.weald.specs/state :as this})

Scrambles sensitive byte-arrays in place

new-client clj

(new-client {:keys [:host :port] :as packet}
            {:keys [:frereth.cp.shared.templates/clnt-short-pk
                    :frereth.cp.shared.templates/srvr-short-sk]
             :as cookie}
            {:keys [:frereth.cp.shared.constants/clnt-xtn] :as initiate})

randomized-cookie-cutter clj

(randomized-cookie-cutter)