frereth.cp.client
Implement the client half of the CurveCP protocol.
It seems like it would be nice if I could just declare the message exchange, but that approach gets complicated on the server side. At least half the point there is reducing DoS.
Implement the client half of the CurveCP protocol. It seems like it would be nice if I could just declare the message exchange, but that approach gets complicated on the server side. At least half the point there is reducing DoS.
frereth.cp.client.state
Handle the inherently stateful pieces associated with the client side of things.
The fact that this is so big says a lot about needing to re-think my approach
Handle the inherently stateful pieces associated with the client side of things. The fact that this is so big says a lot about needing to re-think my approach
frereth.cp.message
Translation of curvecpmessage.c
This is really a generic buffer program
The "parent" child/server reads/writes to pipes that this provides, in a specific (and apparently undocumented) communications protocol.
This, in turn, reads/writes data from/to a child that it spawns.
I keep wanting to think of this as a simple transducer and just skip the buffering pieces, but they (and the flow control) are really the main point.
Translation of curvecpmessage.c This is really a generic buffer program The "parent" child/server reads/writes to pipes that this provides, in a specific (and apparently undocumented) communications protocol. This, in turn, reads/writes data from/to a child that it spawns. I keep wanting to think of this as a simple transducer and just skip the buffering pieces, but they (and the flow control) are really the main point.
- action-trigger!
- build-un-ackd-blocks
- child->!
- child-buffer-timeout
- child-close!
- choose-next-scheduled-time
- clear-interrupt!
- condensed-choose-next-scheduled-time
- do-start
- fast-spins
- get-state
- halt!
- initial-state
- interrupt!
- interrupted?
- max-child-buffer-size
- parent->!
- pick-next-action
- schedule-next-timeout!
- start-event-loops!
- swap-parent-callback!
- trigger-from-child
- trigger-from-parent
- trigger-from-timer
- trigger-output
- write-from-child-timeout
- write-from-parent-timeout
frereth.cp.message.constants
- eof-error
- eof-normal
- header-length
- k-1
- k-128
- k-16
- k-1f
- k-2
- k-4
- k-64
- k-8
- k-8f
- k-div2
- k-div4
- k-div4f
- k-div8
- m-16
- max-32-uint-obsolete
- max-bytes-in-initiate-message
- max-msg-len
- max-outgoing-blocks
- min-msg-len
- min-padding-length
- minute-1
- ms-5
- recv-byte-buf-size
- sec->n-sec
- secs-1
- secs-10
- send-byte-buf-size
- standard-max-block-length
- stream-length-limit
frereth.cp.message.flow-control
Cope with flow-control algorithms
Cope with flow-control algorithms
frereth.cp.message.helpers
Top-level message helpers
Top-level message helpers
frereth.cp.message.registry
Track active message loops
Track active message loops
frereth.cp.message.specs
Common specs that are shared among message namespaces
Common specs that are shared among message namespaces
No vars found in this namespace.
frereth.cp.message.to-child
Looks like this may not be needed at all
Pretty much everything that might have been interesting really seems to belong in from-parent.
Or in the callback that got handed to message as part of its constructor.
Although there is the bit about closing the pipe to the child at the bottom of each event loop.
Looks like this may not be needed at all Pretty much everything that might have been interesting really seems to belong in from-parent. Or in the callback that got handed to message as part of its constructor. Although there *is* the bit about closing the pipe to the child at the bottom of each event loop.
frereth.cp.message.to-parent
- block->parent!
- build-message-block-description
- calculate-message-data-packet-length-flags
- calculate-padded-size
- check-for-new-block-to-send
- check-for-previous-block-to-resend
- mark-block-resent
- mark-block-sent
- maybe-send-block!
- ok-to-send-new?
- pick-next-block-to-send
- pre-calculate-state-after-send
- send-eof-buffered?
frereth.cp.server
Implement the server half of the CurveCP protocol
Implement the server half of the CurveCP protocol
frereth.cp.server.cookie
For dealing with cookie packets on the server side
For dealing with cookie packets on the server side
frereth.cp.server.hello
For coping with incoming HELLO packets
For coping with incoming HELLO packets
frereth.cp.server.helpers
Utility functions that are generally useful for Curve servers
Utility functions that are generally useful for Curve servers
frereth.cp.server.initiate
For coping with Initiate packets
This is the part that possibly establishes a 'connection'
For coping with Initiate packets This is the part that possibly establishes a 'connection'
- build-and-configure-client-basics
- build-new-client
- client-public-key-triad-matches?
- client-short-pk-matches-cookie?
- create-child
- decompose-initiate-packet
- decrypt-cookie
- decrypt-initiate-box
- do-fork-child!
- do-handle
- extract-cookie
- forward-message-portion!
- nonce-modulo
- open-client-crypto-box
- packet-header-length
- possibly-re-initiate-existing-client-connection
- unbox-innermost-key
- validate-server-name
frereth.cp.server.shared-specs
No vars found in this namespace.
frereth.cp.server.state
Managing CurveCP server state
Managing CurveCP server state
frereth.cp.shared
For pieces shared among client, server, and messaging
For pieces shared among client, server, and messaging
frereth.cp.shared.bit-twiddling
Shared functions for fiddling with bits
Shared functions for fiddling with bits
- ->string
- byte-copy!
- bytes=
- extract-rightmost-byte
- possibly-2s-complement-8
- possibly-2s-uncomplement-16
- possibly-2s-uncomplement-32
- possibly-2s-uncomplement-64
- possibly-2s-uncomplement-8
- possibly-2s-uncomplement-n
- secure-mod
- sub-byte-array
- uint-pack!
- uint16-pack
- uint16-pack!
- uint16-unpack
- uint32-pack!
- uint32-unpack
- uint64-pack
- uint64-pack!
- uint64-unpack
- zero-out!
frereth.cp.shared.child
Manage child ioloops
Manage child ioloops
frereth.cp.shared.constants
Magical names, numbers, and data structures
Magical names, numbers, and data structures
- all-zeros
- box-zero-bytes
- client-header-prefix
- client-header-prefix-string
- client-key-length
- cookie-frame-length
- cookie-header
- cookie-header-string
- cookie-nonce-minute-prefix
- cookie-nonce-prefix
- cookie-packet-length
- decrypt-box-zero-bytes
- extension-length
- header-length
- hello-crypto-box-length
- hello-header
- hello-header-string
- hello-nonce-prefix
- hello-packet-dscr
- hello-packet-length
- initiate-header
- initiate-nonce-prefix
- initiate-packet-dscr
- key-length
- legal-vouch-message-length?
- m-1
- max-16-int
- max-16-uint
- max-32-int
- max-32-uint
- max-64-uint
- max-8-int
- max-8-uint
- max-initiate-packet-size
- max-random-nonce
- max-vouch-message-length
- message-len
- min-vouch-message-length
- minimum-vouch-length
- nonce-length
- send-child-message-timeout
- server-cookie-length
- server-header-prefix-string
- server-key-length
- shared-key-length
- two-pow-48
- unboxed-crypto-cookie-length
- vouch-length
- vouch-nonce-prefix
- vouch-overhead
- vouch-wrapper
- zero-box-length
- zero-bytes
frereth.cp.shared.crypto
Wrap up the low-level crypto functions
Wrap up the low-level crypto functions
- box-after
- box-prepare
- build-box
- build-random-iv
- decompose-box
- do-load-keypair
- do-safe-nonce
- encrypt-block
- generate-symmetric-key
- get-nonce-agent-state
- get-random-bytes
- get-safe-client-nonce-suffix
- get-safe-server-nonce-suffix
- initial-nonce-agent-state
- load-nonce-key
- new-nonce-key!
- nonce-key-length
- obscure-nonce
- open-after
- open-box
- random-array
- random-bytes!
- random-key
- random-key-pair
- random-keys
- random-mod
- random-nonce
- randomize-buffer!
- reload-nonce
- reset-safe-nonce-state!
- secret-box
- secret-unbox
frereth.cp.shared.serialization
Convert native data structures to/from raw bytes for network travel
Convert native data structures to/from raw bytes for network travel
frereth.cp.shared.specs
For specs that make sense to share among all the pieces
For specs that make sense to share among all the pieces
frereth.cp.shared.templates
Descriptions of binary files to marshall
Descriptions of binary files to marshall
frereth.cp.shared.util
Pieces refactored from frereth.common.util
Because I haven't really decided what to do with them yet
Pieces refactored from frereth.common.util Because I haven't really decided what to do with them yet
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close