aboutsummaryrefslogtreecommitdiffstats
path: root/tkd/command.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* tkd: Support READCERT command.gniibe/t6364NIIBE Yutaka2023-03-221-0/+26
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* tkd: Add RESTART command.NIIBE Yutaka2023-03-201-0/+20
| | | | | | | | | It will be useful, when TKDaemon will maintain a context for a connection. -- Signed-off-by: NIIBE Yutaka <[email protected]>
* Fix PKSIGN to get data by EXTRA.NIIBE Yutaka2023-03-171-0/+15
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* tkd: sorted out entities and initialize PKCS#11 on demand.NIIBE Yutaka2023-03-171-5/+5
| | | | | | | | | | | | | tkd: host side process which manages KEYs on TOKENs It's a KEYGRIP which identifies a KEY. it's TKD which administrates: where is a KEY on which TOKEN. cryptoki (ck): access object of PKCS#11 API. CRYPTOKI has slots. token: abstraction of a device. Each slots has slot_id. Slot_id corresponds a TOKEN. 1:1 map between slot_id and TOKEN. KEY: TOKEN may have multiple KEYs. Signed-off-by: NIIBE Yutaka <[email protected]>
* tkd: Fix for rescanning the slot list.NIIBE Yutaka2023-03-161-1/+1
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* tkd: Implement finalizer.NIIBE Yutaka2023-03-151-1/+51
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* Implement READKEY command.NIIBE Yutaka2023-03-081-91/+4
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* Implement token_keyinfo.NIIBE Yutaka2023-03-031-1/+1
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* Fix assuan context things.NIIBE Yutaka2023-03-031-5/+4
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* Move functions.NIIBE Yutaka2023-03-021-0/+6
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* Define routines for pkcs11.c in the header.NIIBE Yutaka2023-02-271-24/+8
| | | | Signed-off-by: NIIBE Yutaka <[email protected]>
* Start tkdaemon to offer PKCS#11 module access.NIIBE Yutaka2023-02-271-0/+695
Currently, it's a mock-up. Signed-off-by: NIIBE Yutaka <[email protected]>