Winter 2010 Posters/Certs
Project Name
SheevaPlug Configuration
Names
Alex Vlahopoulos
The SheevaPlug Hardware Specifications
Sheeva CPU Core
1.2 GHz operation
L1 Cache: 16K Instruction + 16K Data
L2 Cache: 256KB
Memory
DDR2 400MHz, 16-bit bus
512MB DDR2: 1Gb x8, 4 devices
Power efficient Samsung devices
NAND FLASH Controller, 8-bit bus
512MB NAND FLASH: 4Gb x8, direct boot
128-bit eFuse Memory
Power
Power input: 100-240VAC/50-60Hz 19W DC Consumption: 5V/3.0A High efficiency POL DC-DC converters
Development Interface
System Development Board JTAG and Console Interface via USB SDIO expansion JTAG OpenOCD support via USB
High Speed I/O & Peripherals
GE, USB 2.0 Host RTC w/ Battery
So after reading and tweaking sample openssl code and config here:
http://fedoraproject.org/wiki/Koji/ServerHowTo
I managed to break the code down into 2 separate peices. One for making the CA and one for making the certs for the different users. Now the way my script differs from the original is that it uses the variables passed to it as the default commonName in the ssl.cnf file.
For example, when executing my script to create a cert for a new user...lets say "kojiuser1":
- ./certscript kojiuser1
The script as usual asks the various questions about where you are from and the OU name and the province etc, etc, but is then followed by the question of what the commonName should be. This name and/or the OU name should always be different from any other certs already created or you will get a TXT_ error. My script makes pressing enter easier by allowing you to press enter knowing that the commonName will be (by default).. "kojiuser1". Now this may not seem like anything huge for the creation of one user but what if we were creating multiple users (which was the case with me).
