diff options
67 files changed, 196 insertions, 38 deletions
@@ -6,3 +6,4 @@ attachments pelican/content/*/* pelican/pelicanconf.py trac.db +pelican/website diff --git a/GNUmakefile b/GNUmakefile index 2136f0b..6298f56 100644 --- a/GNUmakefile +++ b/GNUmakefile @@ -1,5 +1,6 @@ all: ./extract.py + cd pelican; pelican --output website --settings pelicanconf.py --fatal errors content fetch: rsync -aP --delete bikeshed.cryptech.is:/home/trac/db/trac.db bikeshed.cryptech.is:/home/trac/files/attachments . @@ -40,8 +40,11 @@ attachment_query = ''' filename, time ''' -def isotime(t): - return None if t == 0 else time.strftime("%Y-%m-%dT%H:%M:%SZ", time.gmtime(t)) +markdown_header = '''\ +Date: {0.isotime} +Title: {0.name} + +'''.format def attachment_link(row): h = lambda whatever: hashlib.sha1(whatever.encode()).hexdigest() @@ -50,7 +53,7 @@ def attachment_link(row): fn2 = os.path.splitext(row["filename"])[1] return \ os.path.join("attachments", "wiki", h1[:3], h1, h2 + fn2), \ - os.path.join("pelican", "content", urllib.parse.quote(row.id, ""), urllib.parse.quote(row.filename, "")) + os.path.join("pelican", "content", urllib.parse.quote(row.id, ""), row.filename) class Filter: @@ -68,9 +71,14 @@ class Filter: return True class Row(sqlite3.Row): + def __getattr__(self, name): return self[name] + @property + def isotime(self): + return time.strftime("%Y-%m-%d %H:%M", time.gmtime(self.time)) + def main(): for dn in ("wiki", "pelican"): @@ -92,7 +100,7 @@ def main(): print(slug, row.version) with open("wiki/{}.trac".format(slug), "w") as f: f.write(row.text) - md = trac2md.WikiToMD(row.text, slug) + md = markdown_header(row) + trac2md.WikiToMD(row.text, slug) with open("pelican/content/{}.md".format(slug), "w") as f: f.write(md) diff --git a/filter.json b/filter.json index ebb1456..708428e 100644 --- a/filter.json +++ b/filter.json @@ -1,6 +1,7 @@ [ ["+", "WikiStart"], ["-", "CamelCase"], + ["-", "EDAToolchainSurvey\""], ["-", "GitRepositories*"], ["-", "InterMapTxt"], ["-", "InterTrac"], diff --git a/pelican/content/ASICImplementations.md b/pelican/content/ASICImplementations.md index dc21bf9..e8901fd 100644 --- a/pelican/content/ASICImplementations.md +++ b/pelican/content/ASICImplementations.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: ASICImplementations + # Development of a Cryptech ASIC Implementation ## Introduction diff --git a/pelican/content/AlphaBoard.md b/pelican/content/AlphaBoard.md index 9dd7fee..0fa7237 100644 --- a/pelican/content/AlphaBoard.md +++ b/pelican/content/AlphaBoard.md @@ -1,3 +1,6 @@ +Date: 2019-01-22 08:46 +Title: AlphaBoard + # Alpha Board ## Rev 02 diff --git a/pelican/content/AlphaBoardComponents.md b/pelican/content/AlphaBoardComponents.md index 20b2ca5..a307efc 100644 --- a/pelican/content/AlphaBoardComponents.md +++ b/pelican/content/AlphaBoardComponents.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: AlphaBoardComponents + # CrypTech Alpha Board BOM and PCB design requirement sketch This document contains a list of component level description and requirements for the Crypteh Alpha board. diff --git a/pelican/content/AlphaBoardPictures.md b/pelican/content/AlphaBoardPictures.md index 9e006f0..377a80b 100644 --- a/pelican/content/AlphaBoardPictures.md +++ b/pelican/content/AlphaBoardPictures.md @@ -1,3 +1,6 @@ +Date: 2017-05-19 17:49 +Title: AlphaBoardPictures + ## High resolution pictures of the Alpha board diff --git a/pelican/content/AlphaBoardReview.md b/pelican/content/AlphaBoardReview.md index 98b3d33..e6e87bb 100644 --- a/pelican/content/AlphaBoardReview.md +++ b/pelican/content/AlphaBoardReview.md @@ -1 +1,4 @@ +Date: 2016-12-15 22:44 +Title: AlphaBoardReview + ## Alpha board Layout review diff --git a/pelican/content/AlphaBoardStrategy.md b/pelican/content/AlphaBoardStrategy.md index 23c0b31..05e3bac 100644 --- a/pelican/content/AlphaBoardStrategy.md +++ b/pelican/content/AlphaBoardStrategy.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: AlphaBoardStrategy + # The Cryptech Alpha Board ## Goal diff --git a/pelican/content/AlphaReviewLog.md b/pelican/content/AlphaReviewLog.md index 2d49480..d25ccd0 100644 --- a/pelican/content/AlphaReviewLog.md +++ b/pelican/content/AlphaReviewLog.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: AlphaReviewLog + # Review feedback of the Alpha schematics ## Power subsystem diff --git a/pelican/content/AlphaSchematics.md b/pelican/content/AlphaSchematics.md index 7d20880..9b8e73b 100644 --- a/pelican/content/AlphaSchematics.md +++ b/pelican/content/AlphaSchematics.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:39 +Title: AlphaSchematics + The Alpha schematics are almost finished! PDF and Eagle files available for download here in the [[source:/hardware/eagle/alpha/rev02 | hardware]] repository. diff --git a/pelican/content/AlphaSealedBags.md b/pelican/content/AlphaSealedBags.md index a69a66c..6c4d4c9 100644 --- a/pelican/content/AlphaSealedBags.md +++ b/pelican/content/AlphaSealedBags.md @@ -1,3 +1,6 @@ +Date: 2016-12-16 14:12 +Title: AlphaSealedBags + ## Chain of custody diff --git a/pelican/content/AssuredTooChain.md b/pelican/content/AssuredTooChain.md index 89ea7d9..8666e09 100644 --- a/pelican/content/AssuredTooChain.md +++ b/pelican/content/AssuredTooChain.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: AssuredTooChain + # Issues of an Assured Tool-Chain We do not have any assurance that our basic tools are not compromised. diff --git a/pelican/content/BerlinWorkshop.md b/pelican/content/BerlinWorkshop.md index 0c7da32..5e80099 100644 --- a/pelican/content/BerlinWorkshop.md +++ b/pelican/content/BerlinWorkshop.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: BerlinWorkshop + # CRYPTECH Workshop Agenda ### 15-16 July 2016 diff --git a/pelican/content/BinaryPackages.md b/pelican/content/BinaryPackages.md index 632299b..4330625 100644 --- a/pelican/content/BinaryPackages.md +++ b/pelican/content/BinaryPackages.md @@ -1,3 +1,6 @@ +Date: 2019-09-03 15:23 +Title: BinaryPackages + [[PageOutline]] # Binary Packages for Cryptech Software and Firmware diff --git a/pelican/content/BuildingFromSource.md b/pelican/content/BuildingFromSource.md index 8f2a4fd..8aafb17 100644 --- a/pelican/content/BuildingFromSource.md +++ b/pelican/content/BuildingFromSource.md @@ -1,3 +1,6 @@ +Date: 2017-05-17 21:28 +Title: BuildingFromSource + [[PageOutline]] # Building Cryptech Software/Firmware/Bitstream From Source diff --git a/pelican/content/ConfigureFPGA.md b/pelican/content/ConfigureFPGA.md index 8a4beab..d32d3a3 100644 --- a/pelican/content/ConfigureFPGA.md +++ b/pelican/content/ConfigureFPGA.md @@ -1 +1,4 @@ +Date: 2016-12-15 22:39 +Title: ConfigureFPGA + *Page Under Development* diff --git a/pelican/content/CoretestHashesC5G.md b/pelican/content/CoretestHashesC5G.md index 20a3faa..aff2dd2 100644 --- a/pelican/content/CoretestHashesC5G.md +++ b/pelican/content/CoretestHashesC5G.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: CoretestHashesC5G + # How to start using coretest_hashes on the TerasIC C5G Board This is a writeup on how to setup, build and testrun the coretest_hashes Cryptech subsystem on a TerasiC C5G Cyclone V GX Starter Kit FPGA diff --git a/pelican/content/CoretestHashesNovena.md b/pelican/content/CoretestHashesNovena.md index 3dfc8cd..86f15e7 100644 --- a/pelican/content/CoretestHashesNovena.md +++ b/pelican/content/CoretestHashesNovena.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: CoretestHashesNovena + # How to start using coretest_hashes on the Novena PVT1 This is a writeup on how to setup, build and testrun the coretest_hashes diff --git a/pelican/content/DNSSEC%2FRequirements.md b/pelican/content/DNSSEC%2FRequirements.md index 36b1152..178ab5e 100644 --- a/pelican/content/DNSSEC%2FRequirements.md +++ b/pelican/content/DNSSEC%2FRequirements.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: DNSSEC/Requirements + # DNSSEC Requirements ## Questions diff --git a/pelican/content/DNSSEC.md b/pelican/content/DNSSEC.md index 4d57d27..2df98bf 100644 --- a/pelican/content/DNSSEC.md +++ b/pelican/content/DNSSEC.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: DNSSEC + # DNSSEC diff --git a/pelican/content/Dashboard.md b/pelican/content/Dashboard.md index ca2c512..6382901 100644 --- a/pelican/content/Dashboard.md +++ b/pelican/content/Dashboard.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: Dashboard + # Project Status Dashboard ## Product Component Requirements diff --git a/pelican/content/DevBridgeBoard.md b/pelican/content/DevBridgeBoard.md index 2df3ac4..697d792 100644 --- a/pelican/content/DevBridgeBoard.md +++ b/pelican/content/DevBridgeBoard.md @@ -1,3 +1,6 @@ +Date: 2021-02-14 17:30 +Title: DevBridgeBoard + [[PageOutline]] # dev-bridge board diff --git a/pelican/content/DevelopersGuide.md b/pelican/content/DevelopersGuide.md index bbb0f1e..85899e3 100644 --- a/pelican/content/DevelopersGuide.md +++ b/pelican/content/DevelopersGuide.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:39 +Title: DevelopersGuide + *Page Under Development* # Developers Guide diff --git a/pelican/content/DisasterRecovery.md b/pelican/content/DisasterRecovery.md index 9c0e56f..bd4f5e2 100644 --- a/pelican/content/DisasterRecovery.md +++ b/pelican/content/DisasterRecovery.md @@ -1,3 +1,6 @@ +Date: 2017-05-13 00:30 +Title: DisasterRecovery + # Disaster Recovery This page covers a few likely (hopefully unlikely) oh-noes. diff --git a/pelican/content/DocMeet.md b/pelican/content/DocMeet.md index b49ec5d..c6ceff7 100644 --- a/pelican/content/DocMeet.md +++ b/pelican/content/DocMeet.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:39 +Title: DocMeet + # Documents, Meetings, etc. ## Meetings diff --git a/pelican/content/Documents.md b/pelican/content/Documents.md index 94d19e1..44d0dc1 100644 --- a/pelican/content/Documents.md +++ b/pelican/content/Documents.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: Documents + # Presentations and Design Documents ``` diff --git a/pelican/content/EDAToolchainSurvey%22.md b/pelican/content/EDAToolchainSurvey%22.md deleted file mode 100644 index 5516a29..0000000 --- a/pelican/content/EDAToolchainSurvey%22.md +++ /dev/null @@ -1,18 +0,0 @@ -**Note: this page has been replaced by wiki:EDAToolchainSurvey** - -The major issue is finding tools that allows a designer, user to verify that the RTL source code (in Verilog or VHDL) matches what is generated at the physical level. As part of the project we need to investigate the current status of open tools in the toolchain for implementation and verification of hardware. This includes RTL simulation, synthesis, place & route, netlist verification, timing analysis and configuration file generation and analysis. (This implies that the target is an FPGA.). If there are no open tools we need to find ways of verifying pre- and post-functionality to check that the black box tool does not alter (subvert) the design in ways not intended. - -The basic action flow is: - -* Finding open EDA tools and assess their status -* Settling for Closed -* Strategy to Develop Trust in Tools -* Validation Methods for Output - - -Some tools and frameworks worth investigating are: - -* ["OpTiMSoC"](http://www.optimsoc.org/index.html) - An open System on Chip (SoC) framework built around the OpenRISC CPU. -* ["Icarus Verilog"](http://iverilog.icarus.com/) - An open Verilog event driven simulator that supports Verilog 2001, 2005 and SystemVerilog. -* ["gEDA"](http://www.geda-project.org/) - A project that aims at developing GNU based EDA tools. -* ["gplEDA"](http://www.gpleda.org/) - A collection of GPL licensed EDA tools. Points to gEDA. diff --git a/pelican/content/EDAToolchainSurvey.md b/pelican/content/EDAToolchainSurvey.md index ffd40e6..e17f221 100644 --- a/pelican/content/EDAToolchainSurvey.md +++ b/pelican/content/EDAToolchainSurvey.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: EDAToolchainSurvey + The major issue is finding tools that allows a designer, user to verify that the RTL source code (in Verilog or VHDL) matches what is generated at the physical level. As part of the project we need to investigate the current status of open tools in the toolchain for implementation and verification of hardware. This includes RTL simulation, synthesis, place & route, netlist verification, timing analysis and configuration file generation and analysis. (This implies that the target is an FPGA.). If there are no open tools we need to find ways of verifying pre- and post-functionality to check that the black box tool does not alter (subvert) the design in ways not intended. The basic action flow is: diff --git a/pelican/content/ExternalProjects.md b/pelican/content/ExternalProjects.md index d07eb4c..47c92a0 100644 --- a/pelican/content/ExternalProjects.md +++ b/pelican/content/ExternalProjects.md @@ -1,3 +1,6 @@ +Date: 2018-09-17 10:27 +Title: ExternalProjects + External projects using [CrypTech](https://cryptech.is/) technology. diff --git a/pelican/content/ExternalProjectsTorHSM.md b/pelican/content/ExternalProjectsTorHSM.md index 9dd8b7c..1351b46 100644 --- a/pelican/content/ExternalProjectsTorHSM.md +++ b/pelican/content/ExternalProjectsTorHSM.md @@ -1,3 +1,6 @@ +Date: 2018-10-01 14:38 +Title: ExternalProjectsTorHSM + # External project TorHSM ## Problem diff --git a/pelican/content/GettingStartedNovena.md b/pelican/content/GettingStartedNovena.md index 8c58aed..4f71ead 100644 --- a/pelican/content/GettingStartedNovena.md +++ b/pelican/content/GettingStartedNovena.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: GettingStartedNovena + [[PageOutline]] # Getting Started on the Novena diff --git a/pelican/content/Hardware.md b/pelican/content/Hardware.md index fbdac48..c97b272 100644 --- a/pelican/content/Hardware.md +++ b/pelican/content/Hardware.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: Hardware + # Cryptech Hardware ## Generation 1 diff --git a/pelican/content/InterconnectStandards.md b/pelican/content/InterconnectStandards.md index 819b497..8961475 100644 --- a/pelican/content/InterconnectStandards.md +++ b/pelican/content/InterconnectStandards.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: InterconnectStandards + # Comparison of On-Chip Bus Standards ## Introduction diff --git a/pelican/content/Joachim%20Str%C3%B6mbergson.md b/pelican/content/Joachim%20Str%C3%B6mbergson.md index dcf0a94..eac7775 100644 --- a/pelican/content/Joachim%20Str%C3%B6mbergson.md +++ b/pelican/content/Joachim%20Str%C3%B6mbergson.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:54 +Title: Joachim Strömbergson + # Joachim Strömbergson ## Bio diff --git a/pelican/content/MailingLists.md b/pelican/content/MailingLists.md index 599f336..a2c2307 100644 --- a/pelican/content/MailingLists.md +++ b/pelican/content/MailingLists.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:39 +Title: MailingLists + # Communications ## Mailing Lists diff --git a/pelican/content/MiscStuff.md b/pelican/content/MiscStuff.md index 8742c7b..76f5767 100644 --- a/pelican/content/MiscStuff.md +++ b/pelican/content/MiscStuff.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:39 +Title: MiscStuff + # References & Miscellaneous ## Interesting research and people diff --git a/pelican/content/NoisyDiode.md b/pelican/content/NoisyDiode.md index 46e5ec2..8090ff9 100644 --- a/pelican/content/NoisyDiode.md +++ b/pelican/content/NoisyDiode.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: NoisyDiode + ## Noisy Diode entropy source diff --git a/pelican/content/OpenCryptoChip.md b/pelican/content/OpenCryptoChip.md index c8163f8..299193a 100644 --- a/pelican/content/OpenCryptoChip.md +++ b/pelican/content/OpenCryptoChip.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: OpenCryptoChip + [[PageOutline]] # An Open Crypto Chip diff --git a/pelican/content/OpenDNSSEC.md b/pelican/content/OpenDNSSEC.md index 49e2868..9bbfe29 100644 --- a/pelican/content/OpenDNSSEC.md +++ b/pelican/content/OpenDNSSEC.md @@ -1,3 +1,6 @@ +Date: 2017-05-13 21:34 +Title: OpenDNSSEC + # DNSSEC signing using OpenDNSSEC and a Cryptech alpha board rev03 ## Before you start, you'll need diff --git a/pelican/content/PKCS11Proxy.md b/pelican/content/PKCS11Proxy.md index e0776a3..9de7dd7 100644 --- a/pelican/content/PKCS11Proxy.md +++ b/pelican/content/PKCS11Proxy.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: PKCS11Proxy + The pkcs11-proxy is a way to tunnel PKCS11 over TCP (TLS). This page explains how to build and install PKCS11 proxy on the novena. There are various forks of this on github. We're going to use the SUNET fork since it support TLS-PSK for authentication out of the box. The proxy does not currently support different word length on each side of the tunnel so to use it with the novena platform your PKCS11 client must be 32 bit. ## Why would you want this? diff --git a/pelican/content/PostAlphaPlan.md b/pelican/content/PostAlphaPlan.md index aadc44a..f238e1c 100644 --- a/pelican/content/PostAlphaPlan.md +++ b/pelican/content/PostAlphaPlan.md @@ -1,3 +1,6 @@ +Date: 2017-05-16 14:53 +Title: PostAlphaPlan + The core dev team had a design meeting in Berlin after the alpha workshop. We came up with a plan for the hardware and the software work for the next few months: diff --git a/pelican/content/PrahaWorkshop.md b/pelican/content/PrahaWorkshop.md index 6638dce..6217ecb 100644 --- a/pelican/content/PrahaWorkshop.md +++ b/pelican/content/PrahaWorkshop.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: PrahaWorkshop + [[PageOutline]] # CrypTech Workshop - 2015.07.18 Praha diff --git a/pelican/content/PrahaWorkshopSSH.md b/pelican/content/PrahaWorkshopSSH.md index a48c5b6..18a17d3 100644 --- a/pelican/content/PrahaWorkshopSSH.md +++ b/pelican/content/PrahaWorkshopSSH.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: PrahaWorkshopSSH + ## The list of all known SSH keys ``` diff --git a/pelican/content/ProjectArchive.md b/pelican/content/ProjectArchive.md index 0407c13..424984a 100644 --- a/pelican/content/ProjectArchive.md +++ b/pelican/content/ProjectArchive.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: ProjectArchive + *Page Under Construction* # Project Archive and Far Future Planning diff --git a/pelican/content/ProjectManagement.md b/pelican/content/ProjectManagement.md index aad8443..b8f468d 100644 --- a/pelican/content/ProjectManagement.md +++ b/pelican/content/ProjectManagement.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: ProjectManagement + [[PageOutline]] # v0.1 Resources diff --git a/pelican/content/ProjectMetadata.md b/pelican/content/ProjectMetadata.md index e9b9c70..e741afa 100644 --- a/pelican/content/ProjectMetadata.md +++ b/pelican/content/ProjectMetadata.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: ProjectMetadata + # Project Metadata diff --git a/pelican/content/ProjectStatus.md b/pelican/content/ProjectStatus.md index c42d475..d58bb46 100644 --- a/pelican/content/ProjectStatus.md +++ b/pelican/content/ProjectStatus.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: ProjectStatus + *Page Under Development* # Project Status diff --git a/pelican/content/QuickStart.md b/pelican/content/QuickStart.md index 75d5a3f..a476a8f 100644 --- a/pelican/content/QuickStart.md +++ b/pelican/content/QuickStart.md @@ -1,3 +1,6 @@ +Date: 2017-05-13 20:39 +Title: QuickStart + [[PageOutline]] *Page Under Development* diff --git a/pelican/content/RandomnessTesting.md b/pelican/content/RandomnessTesting.md index 0b14c59..315248b 100644 --- a/pelican/content/RandomnessTesting.md +++ b/pelican/content/RandomnessTesting.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: RandomnessTesting + # Randomness Testing Tools This page explains some basics on testing for randomness, and the background necessary to understand their outputs. diff --git a/pelican/content/RelatedWork.md b/pelican/content/RelatedWork.md index 221f614..1129822 100644 --- a/pelican/content/RelatedWork.md +++ b/pelican/content/RelatedWork.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: RelatedWork + # Related Work ## Richard Lamb / ICANN diff --git a/pelican/content/ReleaseNotes.md b/pelican/content/ReleaseNotes.md index 43a7f5b..0f61495 100644 --- a/pelican/content/ReleaseNotes.md +++ b/pelican/content/ReleaseNotes.md @@ -1,3 +1,6 @@ +Date: 2017-05-13 19:18 +Title: ReleaseNotes + [[PageOutline]] # Release Notes diff --git a/pelican/content/Requirements.md b/pelican/content/Requirements.md index 434e4db..ad9406a 100644 --- a/pelican/content/Requirements.md +++ b/pelican/content/Requirements.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:39 +Title: Requirements + # HSM Requirements Requirements for the Cryptech Alpha System. Derived from Use Cases (see below). There are also utility, internal requirements (again, see below). diff --git a/pelican/content/RoughV1.md b/pelican/content/RoughV1.md index ada39d9..3eb6ab1 100644 --- a/pelican/content/RoughV1.md +++ b/pelican/content/RoughV1.md @@ -1,3 +1,6 @@ +Date: 2021-02-14 17:33 +Title: RoughV1 + # Rough Cut at v0.01 Proof of Concept Feature Set [[PageOutline]] diff --git a/pelican/content/SecureChannel.md b/pelican/content/SecureChannel.md index 1d943d5..b03b0f6 100644 --- a/pelican/content/SecureChannel.md +++ b/pelican/content/SecureChannel.md @@ -1,3 +1,6 @@ +Date: 2017-07-27 19:02 +Title: SecureChannel + # Secure Channel This is a sketch of a design for the secure channel that we want to diff --git a/pelican/content/SideChannel.md b/pelican/content/SideChannel.md index 83d031a..583bf67 100644 --- a/pelican/content/SideChannel.md +++ b/pelican/content/SideChannel.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: SideChannel + # Side Channel Attacks diff --git a/pelican/content/StateOfPlay.md b/pelican/content/StateOfPlay.md index 524971b..4207ddc 100644 --- a/pelican/content/StateOfPlay.md +++ b/pelican/content/StateOfPlay.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: StateOfPlay + [[PageOutline]] # A Completely Informal Snapshot Of The Current State Of The Cryptech Project As Of 2014-11-06 diff --git a/pelican/content/SunetInitialDevelopment.md b/pelican/content/SunetInitialDevelopment.md index 974bd5e..452facb 100644 --- a/pelican/content/SunetInitialDevelopment.md +++ b/pelican/content/SunetInitialDevelopment.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: SunetInitialDevelopment + # Planning for SUNET funded Cryptech Work The following documents the first two development steps in Cryptech funded by SUNET. The development is being done by Joachim Strömbergson diff --git a/pelican/content/TRNGDevelopment.md b/pelican/content/TRNGDevelopment.md index 9204952..38e2f54 100644 --- a/pelican/content/TRNGDevelopment.md +++ b/pelican/content/TRNGDevelopment.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:44 +Title: TRNGDevelopment + # TRNG Development One, if not THE key functionality in the Cryptech system is the True Random Number Generator (TRNG). We therefore need to discuss, investigate and test to find a TRNG that we and the users of Cryptech can trust and can verify to be trusted. diff --git a/pelican/content/UpgradeToKSNG.md b/pelican/content/UpgradeToKSNG.md index d33c834..cc9fbe5 100644 --- a/pelican/content/UpgradeToKSNG.md +++ b/pelican/content/UpgradeToKSNG.md @@ -1,3 +1,6 @@ +Date: 2016-12-22 22:53 +Title: UpgradeToKSNG + [[PageOutline]] # Upgrading Cryptech Alpha HSM to "ksng" development package diff --git a/pelican/content/Upgrading.md b/pelican/content/Upgrading.md index bfc9106..ef22187 100644 --- a/pelican/content/Upgrading.md +++ b/pelican/content/Upgrading.md @@ -1,3 +1,6 @@ +Date: 2018-04-07 23:03 +Title: Upgrading + [[PageOutline]] # Upgrading the Cryptech Alpha HSM diff --git a/pelican/content/UsingSTLink.md b/pelican/content/UsingSTLink.md index 1c6f7da..45c94d5 100644 --- a/pelican/content/UsingSTLink.md +++ b/pelican/content/UsingSTLink.md @@ -1,3 +1,6 @@ +Date: 2019-01-24 14:37 +Title: UsingSTLink + # Using ST-LINK ST-LINK is STM's implementation of the [| Serial Wire Debug (SWD)](https://developer.arm.com/products/architecture/cpu-architecture/debug-visibility-and-trace/coresight-architecture/serial-wire-debug) protocol. diff --git a/pelican/content/WhoWeAre.md b/pelican/content/WhoWeAre.md index 1299661..eb0e7ec 100644 --- a/pelican/content/WhoWeAre.md +++ b/pelican/content/WhoWeAre.md @@ -1,3 +1,6 @@ +Date: 2016-12-15 22:43 +Title: WhoWeAre + # Who We Are This effort was started at the suggestion of Russ Housley, Stephen Farrell, and Jari Arkko of the IETF, to meet the assurance needs of supporting IETF protocols in an open and transparent manner. diff --git a/pelican/content/WikiStart.md b/pelican/content/WikiStart.md index c84bafb..65d160c 100644 --- a/pelican/content/WikiStart.md +++ b/pelican/content/WikiStart.md @@ -1,3 +1,6 @@ +Date: 2017-05-13 20:30 +Title: WikiStart + [[PageOutline]] # Overview diff --git a/pelicanconf.py b/pelicanconf.py index 41ac132..ab8afd2 100644 --- a/pelicanconf.py +++ b/pelicanconf.py @@ -6,7 +6,7 @@ SITENAME = "Cryptech Project" PATH = "content" TIMEZONE = "UTC" -DEFAULT_LANG = u"English" +DEFAULT_LANG = "en" # Feed generation is usually not desired when developing SITEURL = "" diff --git a/wiki/EDAToolchainSurvey%22.trac b/wiki/EDAToolchainSurvey%22.trac deleted file mode 100644 index f49c37c..0000000 --- a/wiki/EDAToolchainSurvey%22.trac +++ /dev/null @@ -1,15 +0,0 @@ -'''Note: this page has been replaced by wiki:EDAToolchainSurvey'''
-
-The major issue is finding tools that allows a designer, user to verify that the RTL source code (in Verilog or VHDL) matches what is generated at the physical level. As part of the project we need to investigate the current status of open tools in the toolchain for implementation and verification of hardware. This includes RTL simulation, synthesis, place & route, netlist verification, timing analysis and configuration file generation and analysis. (This implies that the target is an FPGA.). If there are no open tools we need to find ways of verifying pre- and post-functionality to check that the black box tool does not alter (subvert) the design in ways not intended.
-
-The basic action flow is:
-* Finding open EDA tools and assess their status
-* Settling for Closed
-* Strategy to Develop Trust in Tools
-* Validation Methods for Output
-
-Some tools and frameworks worth investigating are:
-* [http://www.optimsoc.org/index.html "OpTiMSoC"] - An open System on Chip (SoC) framework built around the OpenRISC CPU.
-* [http://iverilog.icarus.com/ "Icarus Verilog"] - An open Verilog event driven simulator that supports Verilog 2001, 2005 and SystemVerilog.
-* [http://www.geda-project.org/ "gEDA"] - A project that aims at developing GNU based EDA tools.
-* [http://www.gpleda.org/ "gplEDA"] - A collection of GPL licensed EDA tools. Points to gEDA.
|