Need a mechanism for generating the customer-specific encrypted book content

[usernamenumber]

_EDIT_

These requirements have simplified since the issue was created. Per the revised and clarified deliverables after the 13 May meeting:

The app will include a simple standard for creating books it can read, e.g. "book content should be HTML encrypted with the teacher's key using $ALGORITHM, in a zip file along with a json metadata file following $SCHEMA". Certell will take care of the vending, book generation, etc

However, we need to at least...

• Finalize the json metadata schema
  • Do things like digital signature, expiration date, institution name, etc need to be added? What is the best way to store sensitive properties securely?
• Add a "download book" mechanism to the app, so students can be given a url to download the right book.
  • This is pretty terrible UX. Maybe we can come up with something better, like a custom extension for which we can make Funzo the download handler?

    original, probably obsolete, issue text follows

We can encrypt the book (#32), and we're working on geolocation (#33) but several tasks remain before this meets the requirement in the spec:

If the IP address shows a US/Canada location, then the student must enter a unique code proving they are "in an educational setting"­ that code determines the length of time the student will be able to access the eBook.

So we need a way to:

1. Register authorized "educational settings"
2. Generate a code for each registered setting (that, at least, should be trivial)
3. Authenticate representatives of registered settings
4. Generate book content encrypted with the setting's code
   • ...in a format that can be imported into funzo from a device.
   • ...which implies a way to host the generate content for download? Otherwise either Certell will ned to provide hosting (which hopefully they could do), or content will need to be loaded onto devices via SD card (which might be beyond the average econ teacher).

[usernamenumber]

Proposal for dealing with this, at least in part, is in https://github.com/usernamenumber/funzo-cse/issues/3