summaryrefslogtreecommitdiff
path: root/p11p-daemon
Commit message (Collapse)AuthorAgeFilesLines
...
* reformatLinus Nordberg2019-07-011-18/+15
|
* rename client/server "change" -> "event"Linus Nordberg2019-07-013-10/+10
|
* document the manager a bit moreLinus Nordberg2019-07-011-7/+19
|
* use a list comprehension in the place of lists:map/2Linus Nordberg2019-06-301-5/+4
| | | | | | | | map/2 does _not_ risk reordering the list. The comment "The evaluation order depends on the implementation." in the documentation refers only to in which order fun is applied. A list comprehension looks a little bit nicer though, IMO.
* rename manager functions to reflect where the policy livesLinus Nordberg2019-06-303-11/+11
| | | | | | Servers and remotes (soon renamed "clients") are not the ones implementing policy. They should therefore report events to the manager which then imposes policy.
* at p11 client disconnect, server asks manager to kill remoteLinus Nordberg2019-06-303-18/+34
| | | | | | | | Also, comment out all debug printouts reporting about octets sent and received, all four types. Missing: Switching remote behind the back of the p11 client, including replaying whatever needs to be replayed.
* start remotes on demand rather than at manager startupLinus Nordberg2019-06-302-36/+55
| | | | | | | Also, rotate list of remotes on remote timeout. Still missing: When a remote times out, switch remote under the feet of the client.
* make p11p_server:reply/2 a call tooLinus Nordberg2019-06-302-12/+12
|
* turn most cast's into call's, for more synchronisityLinus Nordberg2019-06-303-20/+30
|
* parse rpc replies and timeout if they're not on timeLinus Nordberg2019-06-282-18/+42
| | | | | | | | | | | | | | | | | Not that it works though, demonstrated thanks to our attempts at reusing a remote for a new client which is sending that version byte before the rpc message. At least I think that's why. Seems like send (to remote) is blocking and therefore the timeout can't fire (same process). First things is that the timeout should probably be in the server instead, in case the remote is blocking like in this case. Second is that we'd at least seen something if the server was calling the remote genserver instead of casting, du to the default gen_server:call timeout of 5s. Why are we casting in the first place? Well, we had to back when we didn't collect the full rpc message before passing it on. That could change now.
* don't send that version octet by itselfLinus Nordberg2019-06-284-34/+40
| | | | Instead, add it to new remote outbuf.
* parse rpc requests and don't send until we've got a full requestLinus Nordberg2019-06-281-14/+30
|
* serialise rpcLinus Nordberg2019-06-281-2/+10
|
* prepend debug printouts with own pidLinus Nordberg2019-06-281-10/+7
|
* first rought cut of an rpc parserLinus Nordberg2019-06-282-0/+173
|
* add a genserver for handling remotes and start forwarding dataLinus Nordberg2019-06-274-45/+158
| | | | | | | | | | Current status is that p11tool successfully performs a --list-tokens request over p11p, yay! Only once though -- the next request hangs. heh. Also, the timeout logic is wrong and should move to the server, measuring the time it takes to get a full p11 response. This reqires parsing of the p11-kit rpc protocol, which we need anyway.
* typeLinus Nordberg2019-06-271-1/+1
|
* add remote manager, fork+execing p11-kit-remote processesLinus Nordberg2019-06-264-7/+106
|
* keep tokens and their modules in mapsLinus Nordberg2019-06-262-38/+73
| | | | | | For convenient lookup by name. Not the most storage efficient, and maybe proplists would be better suited. Learning maps is useful though.
* stop exposing config recordsLinus Nordberg2019-06-245-26/+15
|
* debugLinus Nordberg2019-06-241-0/+2
|
* init servers from config; cleanup on app stopLinus Nordberg2019-06-243-11/+29
|
* make top sup rest-for-one: restart servers if config changesLinus Nordberg2019-06-241-1/+1
|
* whitespaceLinus Nordberg2019-06-241-1/+1
|
* start one sock_server per token; give servers a chance to clean upLinus Nordberg2019-06-242-31/+63
| | | | still not rm'ing the socket file though. wonder where that should happen.
* include unix pid in socket nameLinus Nordberg2019-06-242-5/+7
|
* use default intensity/restart values (1 restart in 5 seconds)Linus Nordberg2019-06-241-4/+5
|
* add READMELinus Nordberg2019-06-241-0/+26
|
* server side accepting connections, reading from socketLinus Nordberg2019-06-204-74/+101
|
* add listenerLinus Nordberg2019-06-192-1/+75
|
* follow our own spec a bitLinus Nordberg2019-06-191-2/+3
|
* remove level 'global' in configLinus Nordberg2019-06-191-12/+10
|
* tidy up, add path to p11moduleLinus Nordberg2019-06-192-11/+18
|
* add test configLinus Nordberg2019-06-191-1/+13
|
* don't include sasl until we need itLinus Nordberg2019-06-191-1/+1
|
* new fileLinus Nordberg2019-06-191-0/+8
|
* comment on deps from debian pkgsLinus Nordberg2019-06-191-0/+1
|
* syntaxLinus Nordberg2019-06-191-1/+1
|
* add p11p-daemon skeletonLinus Nordberg2019-06-1911-0/+294
generated by cgit v1.1 at 2025-07-04 17:20:36 +0000