Skip to content
This repository has been archived by the owner on Apr 15, 2022. It is now read-only.

Roadmap

Jump to bottom
Josh edited this page May 26, 2014 · 2 revisions

There are three phases to the Hashlet development.

Phase 1: Monolithic Application

The first phase is create a standalone monolithic command line application to communicate with the Hashlet. The application will run entirely in user-space and not required root permission. This is to be the first milestone. The key features needed in this phase are:

  • Get Random command.
  • Check MAC command.
  • MAC command.
  • HMAC command.

A feature that would be nice to have is the personalization process, but there are some non-trivial details here.

Phase 2: Migrate to Library

Migrate the common features to libcrypti2c. This will allow other interfaces, beside a CLI, to use the software.

Phase 3: Kernel Module

Perhaps preferred over phase 2 is having a kernel module. The kernel module should provide the I2C communication layer but also handle the CRC and command encapsulation. There are a few commands and each command has multiple options so either everything is accessed through ioctl, or perhaps through sysfs one can export each command as a different file descriptor. i.e. one echos to the mac file descriptor.

Clone this wiki locally