Elvis Wiki - User contributions [en]

Restore backup of smartphone with TWRP

2019-08-06T12:46:32Z

Mtausig: Create documentation

== Summary ==

If you have previously done a backup of a smartphone using the recovery TWRP, this documentation shows you how to restore it.

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: adb

In the documentation [[Unlock_Nexus_5X]] the creation of a usable backup is described.

== Description ==

=== Upload backup ===

The downloaded backup should look like this

$ tree BACKUPS
BACKUPS
└── ZY223WRD2C
└── 2016-07-09--03-01-28
├── boot.emmc.win
├── boot.emmc.win.sha2
├── data.f2fs.win
├── data.f2fs.win.sha2
├── data.info
├── recovery.log
├── system.ext4.win000
├── system.ext4.win000.sha2
├── system.ext4.win001
├── system.ext4.win001.sha2
└── system.info

Upload it to the smartphone

$ adb push BACKUPS /data/media/TWRP/BACKUPS/
BACKUPS/: 11 files pushed. 5.5 MB/s (2047191826 bytes in 355.858s)

=== Restore ===

Boot the smartphone into recovery and select Restore. It should show the folder with the date of the backup and beneath it a list of partitions. Select all of them and start the restore

== Used Hardware ==

* [[Motorola_Moto_G4_Play_Smartphone_16_GB,_Android,_Dual-SIM,_black]]
* [[LG_Nexus_5X_Google_Smartphone_32_GB,_Android_6.0_Marshmallow,_Carbon]]

== Courses ==

* -

== References ==

* -

[[Category:Documentation]]

Proxmark3: FH-Campus Card NFC Security Valuation

2019-07-25T16:05:26Z

Mtausig: Protected "NoNameArticle" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Proxmark3: FH-Campus Card NFC Security Valuation

2019-07-25T16:04:37Z

Mtausig: Text entfernt

Proxmark3: FH-Campus Card NFC Security Valuation

2019-07-25T16:04:22Z

Mtausig: Mtausig moved page Proxmark3: FH-Campus Card NFC Security Valuation to NoNameArticle without leaving a redirect

== Zusammenfassung ==

In unserer Arbeit wird gezegt, dass der größte Teil der Implementationen des FH-Campus-Karten-Systems gravierende Schwachstellen besitzt und diese mittels modifiziertem Proxmark3 Repository relativ schnell ausgenutzt werden können. Somit ist man in der Lage mit dem [[:File:iso14443a.zip|SourceCodes]] sich als beliebiger Nutzer an dem Drucker, Getränke und Snack-Automaten anzumelden und damit zu zahlen.

Genauere Dokumentation findet man hier:
[[:File:Proxmark.pdf|Proxmark3: Securityanalyse der Universitätsausweise]]

== Anforderungen ==

* Betriebssystem:
** Ubuntu 16.04/18.03
** Windows 10
** MacOS 10.x
* Proxmark3

Folgende Dokumentation ist hilfreich, jedoch nicht zwingend notwendig, da im [[:File:Proxmark.pdf|Paper]] genauer darauf eingegangen wird:
* [[Proxmark3: Installation]]
* [[Proxmark3: Useful commands]]

== Beschreibung ==

Dieses Projekt beschäftigt sich mit der Analyse und Sicherheit kontaktloser Karten (NFC). Dabei wird das Gerät Proxmark3 zur Hilfe genommen, um die Daten von kontaktlosen Karten mitzulesen und um mit diesen Karten zu kommunizieren.

In dieser Arbeit wird zunächst kurz die NFC-Technologie erläutert, die diese kontaktlose Identifikation ermöglicht. Danach gehen wir auf die unterschiedlichen Problemzonen und Schwachstellen dieser Technologie ein und erarbeiten die möglichen Angriffsvektoren.

Im Anschluss daran wird dieses Wissen in die Tat umgesetzt, indem wir eine Arbeitsumgebung für den Proxmark3 aufsetzen und zunächst die simplere RFID Karte Mifare Classic analysieren und die Schwächen dieses Typen inspizieren. Daraufhin wenden wir uns der Weiterentwickelten Karte, namens Mifare Plus S, die den Kartentyp unserer Universität widerspiegelt. Die gewonnenen Erkenntnisse werden genutzt, um das Kartensystem an der Universität auf ihre Sicherheit zu überprüfen.

* [[:File:Proxmark.pdf|Results.pdf]]
* [[:File:iso14443a.zip|SourceCode.c]]

== Benutzte Hardware ==

[[Proxmark 3]]

== Kurse ==

* [[Einführendes Wahlfachprojekt]] (2019)

== Authoren ==

* Ostrowski, John
* Arseven, Can

== Referenzen ==

siehe [[File:Proxmark.pdf]]

[[Category:Documentation]]

Connect LoRa Gateway to The Thing Network

2019-07-22T15:57:15Z

Mtausig: Finish documentaion

== Summary ==

This documentation describes how to setup a [[Lorix One LoRa Gateway IP65 with Outdoot antenna 4.15 dBi|Lorix One]] antenna as a Lorawan Gateway and connect it to [https://www.thethingsnetwork.org/ The Things Network]

== Requirements ==

The [[Lorix One LoRa Gateway IP65 with Outdoot antenna 4.15 dBi|Lorix One]] antenna need to be mounted outdoors.
It is powered by PoE. You should use a surge protector like [[Ethernet Surge Protector ETH-SP-G2]] with it.

You also need to setup your network accordingly. The gateway need outgoing access to the internet on the UDP port 1700 and must be able to receive answers from that port. Standard access to HTTP, HTTPS, DNS, NTP is highly recommended. For administration, Port 22 on the antenna has to be reachable.

You also need an account with The Things Network.

== Description ==

=== Basic configuration ===

The device comes with a [https://www.yoctoproject.org/ Yocto Linux] OS.

It is configured to the IP address 192.168.1.50 (configured at it at /etc/network/interfaces) and an open SSH port with the default credentials admin:lorix4u. Change them immediately after login.

During the first configuration you should update the device

sudo opkg update
sudo opkg upgrade
sudo opkg clean

(there might be some error messages due to obsolete packages, which can safely be ignored)

=== Configure Package Forwarder ===

Next the package forwarder, which forward received LoRa packages to the application server must be configured (it comes preinstalled).

$ sudo /etc/init.d/clouds-manager.sh stop
Stopping cloud loriot... done.
$ sudo /etc/init.d/clouds-manager.sh configure
==========================================
| LORIX One clouds manager configuration |
==========================================

Actual configuration:
autostart=true
cloud=loriot

Do you want to enable autostart at boot time?
[Yes|No]
> Yes

Which cloud app. do you want to use ?
[loriot|packet-forwarder|ttn|manual]
> ttn

New configuration:
autostart=true
cloud=ttn

$ cd /opt/lorix/clouds/ttn/
$ sudo cp local_conf.json local_conf.json.org

Next, you need to find out the EUI of your device:

$ sudo /opt/lorix/utils/update_gwid.sh /opt/lorix/clouds/ttn/local_conf.json
Gateway_ID set to fcc23dFFFE0a958a in file /opt/lorix/clouds/ttn/local_conf.json

(this command doesn't actually change the configuration file)

Next, you need to edit /opt/lorix/clouds/ttn/local_conf.json:

{
/* Put there parameters that are different for each gateway (eg. pointing one gateway to a test server while the others stay in production) */
/* Settings defined in global_conf will be overwritten by those in local_conf */
"gateway_conf": {
"gateway_ID": "fcc23dFFFE0a958a",

"servers": [
{
"server_address": "router.eu.thethings.network",
"serv_port_up": 1700,
"serv_port_down": 1700,
"serv_enabled": true
}
],
"fake_gps": false,
"ref_latitude": 10,
"ref_longitude": 20,
"ref_altitude": -1,
"contact_email": "elvis@fh-campsuwien.ac.at",
"description": "Wifx LORIX One gateway powered by ELVIS"
}
}

Immediately make a backup copy of this configuration file, as it might be overwritten by an update.

The sucessfull configuration can be tested by running /opt/lorix/clouds/ttn/poly_pkt_fwd.

If everything works, you can start the forwarder by running

sudo /etc/init.d/clouds-manager.sh start

It should also work after a reboot

sudo reboot

=== Register gateway with The Things Network ===

Login at [https://www.thethingsnetwork.org/ The Things Network] and open the [https://console.thethingsnetwork.org/ the Console].
Open Gateways -> Register

In the form, select "I'm using the legacy packet forwarder" and paste the gateway ID from above into that field (it will automatically be converted into a hex values). Then enter the following values:

* Description: Can be any text
* Frequency Plan: "Europe"
* Router: "ttn-router-eu"
* Location: Chose on map
* Antenna Placement: Outdoor

== Used Hardware ==

* [[Lorix One LoRa Gateway IP65 with Outdoot antenna 4.15 dBi]]
* [[Ethernet Surge Protector ETH-SP-G2]]

== References ==

* https://www.thethingsnetwork.org/
* [https://www.lorixone.io/sites/default/files/2018-11/LORIX%20One%20user%20manual%20EN.pdf User Manual]
* [https://www.thethingsnetwork.org/labs/story/install-awesome-lorix-one-gateway Install Documentation]
* [https://www.thethingsnetwork.org/forum/t/install-lorix-one-gw-in-less-than-1-hour/7775 Documentation discussion]
* [https://www.thethingsnetwork.org/forum/t/new-ttn-packet-forwarder-available/7644 State of the package forwarder]

[[Category:Documentation]]

Connect LoRa Gateway to The Thing Network

2019-07-22T15:42:22Z

Mtausig: Start Lorix configuration documentation

Atmel Sam Cryptography with CryptoAuth-Xpro-B

2019-06-24T13:22:55Z

Mtausig: Fix link to course and hardware

== Summary ==

This documentation describes the usage of security features for microcontrollers especially for the Atmel Sam R21 with the expansion board Atcryptoauth Xpro B.

== Requirements ==
* [https://www.microchip.com/mplab/avr-support/atmel-studio-7 AtmelStudio]
* [https://www.microchip.com/developmenttools/ProductDetails/atsamr21-xpro Atmel SAM R21 Xplained Pro]
* [https://www.microchip.com/DevelopmentTools/ProductDetails/atcryptoauth-xpro-b ATCRYPTOAUTH-XPRO-B]

== Description ==
The Cryptoauth expansion board contains four chips which gets connected via I2C
Chips:
* [https://www.microchip.com/wwwproducts/en/atsha204a ATSHA204A] (SHA256)
* [https://www.microchip.com/wwwproducts/en/atecc508a ATECC508A] (Ellipticcurve P256, SHA256)
* [https://www.microchip.com/wwwproducts/en/atecc608a ATECC608A] (Ellipticcurve P256, SHA256, AES-GCM)
* [https://www.microchip.com/wwwproducts/en/ataes132a ATAES132A] (AES128)

=== Implementation for ATECCx08A and ATSHA204A ===
The [https://git.fh-campuswien.ac.at/c1710475053/atmel-sam-cryptography-with-cryptoauth-xpro-b implementation for ATECCx08A and ATSHA204A] is based on the [https://github.com/MicrochipTech/cryptoauthlib Cryptoauthlib].For ease of use of the ASF USART a custom abstraction layer got implemented.

The example program Implements:
* Showing the serial numbers of the chips
* Hashing a message
* Showing locked zones
* Locking zones
* Generate a random number (only works with locked configuration Zone)
* Generate a keypair (only works with locked configuration Zone)

Usage:
* Connect your microcontroller to the EDGB USB port and upload the software
* Open a terminal Program ([https://www.putty.org/ Putty], [https://ttssh2.osdn.jp/index.html.en TeraTerm])
* Terminal program configuration:
Baud rate 115200
Data bits 8
Stop bits 1
Parity none
* Press the restart button in the controller
* The implementation has an text menu which allows you to navigate by numbers

=== Implementation for ATAES132A ===
[[File:AES132ADatasheet.pdf]] -> that Datasheet is made available from Atmel to get a better understanding of the ATAES132A Chip.

The ATAES132A Chip is NOT based on the [https://github.com/MicrochipTech/cryptoauthlib Cryptoauthlib]. Therefore Atmel doesn't offer complete or functioning example codes for this Chip. There are some example codes that might be working but only for the SAMD21 Xplained Pro board not the SAMR21 Xplained Pro B board, which we are using. I tried to use those example codes, with some changes so it would be working with our board, but I got ERROR messages each time. The main error probably is, that the SAMR21 Xplained Pro Microcontroller is not able to connect to the ATAES132A chip as a I2C slave. Some other problems are, that the example codes for the SAMD21 Xplained Pro board rely too much on that board, so it is nearly impossible to change it for the SAMR21 Xplained Pro B board. Another problem is that Atmel don't even offer an example code to connect to the extension boards, so I wasn't able to check if the ATAES132A chip is working, because no connection could be build. One of the codes is probably working if the connection could be established, because I got a build access and I could load the code onto the board, but I only got negative replies over the Usart.

Here is the link to the projects I tried: [https://github.com/georgie047/Wahlfachprojekt/tree/master/Code/ATAES132A]

== Security Features ==
[[File:Sicherheits-Features.pdf]]

== Cryptographic algorithms ==
[https://git.fh-campuswien.ac.at/c1710475053/atmel-sam-cryptography-with-cryptoauth-xpro-b/blob/master/Dokumentation/Cryptographic_Algorithms.pdf Click here for Pdf]

== User Guides ==
* [[File:User Guide Atmel.pdf]]
* [[File:User Guide EDGB.pdf]]
* [[File:User Guide Security Features.pdf]]
those User Guides are made available from Atmel to get a better understanding of their products.

== Used Hardware ==

* [[Cryptoauth XPro B]]
* [https://www.microchip.com/mplab/avr-support/atmel-studio-7 AtmelStudio]
* [https://www.microchip.com/developmenttools/ProductDetails/atsamr21-xpro Atmel SAM R21 Xplained Pro]
* [https://www.microchip.com/DevelopmentTools/ProductDetails/atcryptoauth-xpro-b ATCRYPTOAUTH-XPRO-B]

== Courses ==

* [[Einführendes Wahlfachprojekt]] (2019)

== References ==

Implementation:
* https://www.insidegadgets.com/2017/04/21/alarm-system-v3-part-3-using-the-atmel-cryptoauthentication-atsha204a/
* https://www.youtube.com/watch?v=TAOVKcN-pwY
* https://microchiptech.github.io/cryptoauthlib/html/index.html

Cryptographic algorithms:
* https://en.wikipedia.org/wiki/SHA-2
* http://www.iwar.org.uk/comsec/resources/cipher/sha256-384-512.pdf
* https://www.geeksforgeeks.org/implementation-diffie-hellman-algorithm/
* https://www.korelstar.de/informatik/aes.html
* https://en.wikipedia.org/wiki/Advanced_Encryption_Standard#Description_of_the_ciphers

[[Category:Documentation]]

OPTIGA Trust E evaluation kit

2019-06-24T13:19:12Z

Mtausig: Add correct links to hardware, course and category, fix header levels

== Summary ==

This summary gives an overview of the cryptographic applications of the microcontroller XMC4500 Relax Kit and the Optiga Trust E/X with security features.

== Used Hardware/Software ==

=== Infineon development tools ===

<p>Register at www.infineon.com to find all the important information about the XMC4500 board and the Optiga Trust E/X evaluation kit. Following development tools are needed to generate code for the XMC4500: DAVE ™ version 4. Alternatively, the Keil MDK can be used.</p>

<br/>
<p>Download-Link for Dave ™ version 4</p>

https://www.infineon.com/cms/en/product/promopages/aim-mc/dave_downloads.html

</br>
<p>Download-Link for Example Codes</p>
https://www.infineon.com/cms/en/product/promopages/aim-mc/dave_downloads.html

<br/>
The DAVE ™ package contains the IDE and all required libraries (DAVE ™ APPs, XMC ™ Lib, Device and Board Support Package, and Device Descriptions).

<br/>
<p> First Steps </p>
[https://www.infineon.com/dgdl/Infineon-DAVE_Quick_Start-GS-v02_00-EN.pdf?fileId=5546d4624cb7f111014d059f7b8c712d/ Quick Start - Simple LED Blinky]

=== Datasheets ===

<ul>
<li>[https://www.infineon.com/cms/de/product/evaluation-boards/kit_xmc45_relax_v1/ Infineon Overview of XMC4500]</li>
<li>[https://www.infineon.com/dgdl/Board_Users_Manual_XMC4500_Relax_Kit-V1_R1.2_released.pdf?fileId=db3a30433acf32c9013adf6b97b112f9/ XMC4500 User’s Guide]</li>
<li>[https://www.infineon.com/dgdl/Infineon-XMC4500-DS-v01_05-EN.pdf?fileId=5546d46254e133b40154e1b56cbe0123/ XMC4500 Datasheet]</li>
<li>[https://www.infineon.com/cms/de/product/evaluation-boards/optiga-trust-e-eval-kit/ Infineon Overview of Optiga Trust E/X]</li>
<li>[https://www.infineon.com/dgdl/Infineon-OPTIGA%20TRUST%20X%20SLS%2032AIA-DS-v02_60-EN.pdf?fileId=5546d462602a9dc801606f1c2ebb7fe9/ Optiga Trust E/X Datasheet]</li>
<li>[https://usermanual.wiki/Document/OPTIGATrustXSolutionReferenceManualv135.2125473546/view/ Optiga Trust E/X Reference Manual]</li>
</ul>

=== OPTIGA ™ Trust E-Evaluation Kit ===

[[Optiga_Trust_E_Evaluation_Kit]]

The Infineon Technologies OPTIGA ™ Trust E-Evaluation Kit evaluates and demonstrates the OPTIGA ™ Trust B Authentication Device. This kit features a PC plug-in board based on the XMC microcontroller and comes with software that provides the user with an intuitive graphical user interface. The OPTIGA ™ Trust E Evaluation Kit allows the user to try out OPTIGA Trust E applications, including authentication, adding cryptographic certificates, and read/write data. This evaluation kit can either be used to debug the Host Lib code or to demonstrate the key features of the OPTIGA ™ Trust E through the intuitive PC GUI.

<br/>
The OPTIGA ™ Trust E helps protect services, business models and user experience. This security solution uniquely identifies objects and protects PKI networks based on their one-way authentication mechanism. In addition, the OPTIGA Trust E protects the quality and safety of products.

<br/>
The OPTIGA Trust E is based on Elliptic Curve Cryptography (ECC) with 256-bit, AES128 and SHA-256. This security technology greatly enhances the security of the entire system. In addition, the OPTIGA Trust E covers a wide range of applications to protect the authentication, security and confidentiality of embedded devices. These include mutual authentication, secure communication, data store protection, lifecycle management, secured updates, and platform integrity protection.
The out-of-the-box facility, with full system integration and pre-programmed essentials, reduces design, integration and deployment requirements. As a ready-to-use solution, the OPTIGA Trust E comes with OS, embedded application and full host-side integration support.

==== Security Features ====

Cryptographic support: ECC256, AES128, SHA-256, TRNG (TrueRandomNumberGenerator), DRNG (DigitalRandomNumberGenerator)

==== Characteristics ====

<ul>
<li>High-end security controller</li>
<li>Ready to use solution</li>
<li>One-way authentication with ECDSA</li>
<li>Mutual authentication with DTLS client (standard RFC 6347)</li>
<li>Secure communication with DTLS</li>
<li>Compliant with USB Type-C ™ authentication standard</li>
<li>I2C interface</li>
<li>Cryptographic support: ECC256, AES128, SHA-256, TRNG, DRNG</li>
<li>Standard and extended temperature ranges</li>
<li>Complete system integration support</li>
<li>Common Criteria certified EAL6 + (high) hardware</li>
<li>Cryptographic Toolbox based on ECC NIST P256, P384 and SHA256 (register, verify, key generation, ECDH, session key derivation)</li>
</ul>

==== Applications ====

<ul>
<li>Industrial control and automation</li>
<li>Consumer electronics</li>
<li>Smart Home</li>
<li>Medical equipment</li>
</ul>

==== AES - Advanced Encryption Standard ====

Advanced Encryption Standard, AES for short, is a symmetric encryption method. Since the end of 2001, Rijndeal has been officially standardized as AES in the US by NIST (National Institute of Standards and Technology). It is used for the encryption of documents and communication connections. AES is not patented and therefore freely usable.

<br/>
Rijndael and AES are block ciphers based on a substitution-permutation network (SPN). The procedure alternates between substitution and permutation at each step. The transformation of the plaintext occurs in several rounds of the same structure. The plaintext is not processed as a whole, but in blocks.

<br/>
For Rijndael, block length and key length can be independently 128, 160, 192, 224 or 256 bits. For AES, the block length is set to 128 bits and the key size to 128 (10 rounds), 192 (12 rounds), and 256 bits (14 rounds).
The AES decryption necessarily requires that the same steps be followed as with encryption. Just in reverse order. It is, in a way, a weakness of AES.

==== ECC - Elliptic Curve Cryptography ====

Crypto-systems and methods based on elliptic curves are referred to as ECC methods. ECC procedures have been part of the NIST (National Institute of Standards and Technology) standards since 1999. ECC methods are among the asymmetric encryption methods. The number after the hyphen refers to the key length. Typical applications of ECC are the key exchange and signature procedures. Also, Mozilla Foundation products (including Firefox, Thunderbird) support ECC with min. 256 bit key length.

<br/>
Roughly speaking, ECC methods are based on operations with pairs of points on certain elliptic curves. Despite the complexity, the mathematics behind the ECC methods has been sufficiently well researched. Most cryptographers recommend ECC methods to be preferred.
The use of elliptic curves requires that both communication partners support the same curve. That means you can not just use any curve. It has to be a specific one.

==== SHA - Secure Hash Algorithm (SHA-1 / SHA-2 / SHA-3) ====

The Secure Hash Algorithm, SHA for short, and all its versions, are cryptographic hash functions. These are used to calculate a check value for any digital data (messages) and are among other things the basis for creating a digital signature. The check value is used to ensure the integrity of a message. If two messages produce the same check value, the equality of the messages should be guaranteed in their normal discretion, without prejudice to specific attempted manipulation of the messages. That's why we require a cryptographic hash function, the property of collision safety: it should be virtually impossible to create two different messages with the same test value.

<br/>
SHA was developed by the US secret service NSA on behalf of the US standardization authority NIST. SHA is used in all popular web applications and network protocols. PGP, SSL, IPsec and S / MIME. And of course with different signature methods. For example, for signing certificates.
The original SHA is referred to as SHA-1 to distinguish it from its successors SHA-2 and SHA-3. SHA-3 should not replace SHA-2, but is an alternative. Should SHA-2 be broken at some point, you can go to SHA-3.

== Objective and results of the project ==

The first objective was to test a simple Led toggling program to determine wether the XMC4500 board is working as it is supposed to. To do that the DAVE ™ 4 environment was used as it is recommended by Infineon. After the download and installation of Dave ™ 4 according to the Quick installation guide that came with the download, the Segger JLink needs to be installed and the libraries need to be updated as well. The first example code can be tested by downloading it on the Dave application itself, then building and debugging it. In this case, there was a problem. The microcontroller was not recognized by the program, the JLink couldn't be found. Following approaches were taken: Update of the Segger JLink, checking the preferences of Dave ™ 4 if correct board was assigned, trying other example codes, etc. The next approach was to see if the microcontroller would run on Keil MDK, A simple LED blinking examples code was installed and successfully run on the Keil environment. This meant that the microcontroller was actually able to connect to the PC. The next move was to try out older versions of Dave (Dave ™ 3), which also didn't work. So an older version of the Segger JLink was installed, and finally the board could be connected to Dave, it worked on both Dave ™ 3 and Dave ™ 4. The Led toggling code worked properly.

AES: The AES example code can be installed through the Dave ™ 4 Project Library. The installation is described on the corresponding Readme-file. Another problem appeared after running the code trough the debugger. The application was supposed to let the Led blink if the values of the key and the decryption output matched. But even though they did the Led still wouldn't toggle. The approach was to configure USART to be able to connect the microcontroller with TeraTerm so that the user can see if the algorithm worked correctly. But because of the fact that the XMC4500 was only recognized by the Dave application and not by the PC itself, there was no COM-Port found by TeraTerm. Therefore the final step was to set one of the other Leds as the output and to let the Led blink at the start and turn it off after the values matched by setting the 'Initial Output Level' of the Digital I/O pin to high.

ECC & SHA: There are no example codes distributed from Infineon for the ECC and SHA algorithms, but a few C example codes can be found on the internet. The example codes that were tested for these projects can be found on the 'References' part of this aritcle. There were error messages on all of these example codes. Almost all the time the problem was the included library. Either there were some files missing or the files coulnd't be found on that path. Another problem was that the code was not compatible with the Dave ™ 4 interface. The example codes were modified to try to solve these error messages. Either the paths of the files were changed or new library files were added. But with each modification, new error messages popped up. For this project especially the Optiga Trust X Framework code on Github seemed to be a good choice for cryptographical algorithms for Dave ™ 4. But, again, the problem was to integrate the two branches of the code, develop & master, so that the library files were complete. But even though the paths to the files were changed in the code or/and the location of these files were changed, the error messages couldn't still be resolved. There are probably other underlying problems for these errors.

Unpredictable Problems with Dave ™ 4: There is barely any documentation on how to use Dave ™ 4 or solutions to problems on writing code or handling error messages, not even on the Infineon webpage. The example codes just explained how to get the code running but they didn't say what the application is really supposed to do, the user doesn't really know what the input & the output should be or what to do in case of an error.

== Courses ==

* [[Einführendes_Wahlfachprojekt]] (2019)

== References ==

<ul>
<li>Overview of XMC-Microcontrollers & Software:
<p>https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/?redirId=53843#!tools</p></li>

<li>Sample Code AES:
<p>https://www.infineon.com/cms/en/product/promopages/aim-mc/dave_downloads.html</p></li>

<li>Sample Code ECDH & SHA:
<p>https://github.com/Infineon/getstarted-optiga-trust-x</p></li>

<li>Small sample Code ECDH:
<p>https://github.com/kokke/tiny-ECDH-c</p></li>
</ul>

[[Category:Documentation]]

PKCS11 token usage with opensc

2019-04-16T13:38:52Z

Mtausig: Describe RSA signature creation

== Summary ==

Basic command line usage of a PKCS#11 token

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: opensc >= 0.18 opensc-pkcs11

== Description ==

The documentation uses the [[Feitian ePass 2003 FIPS 140-2 Level 2]] tokens which can be used with the open source project [https://github.com/OpenSC/OpenSC OpenSC].

The default configuration of the tokens, according to the manufacturer, is as follows:

* Default User PIN: 12345678
* Default SO PIN: entersafe

=== Install opensc-0.18 ===

To install opensc-0.18 on Ubuntu 18.04 download the three source package files from https://packages.ubuntu.com/cosmic/opensc and store them in a build folder. Then run

$ dpkg-source -x opensc_0.18.0-3ubuntu2.dsc
gpgv: Signature made Tue 10 Jul 2018 14:45:55 CEST
gpgv: using RSA key 92978A6E195E4921825F7FF0F34F09744E9F5DD9
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./opensc_0.18.0-3ubuntu2.dsc
dpkg-source: info: extracting opensc in opensc-0.18.0
dpkg-source: info: unpacking opensc_0.18.0.orig.tar.gz
dpkg-source: info: unpacking opensc_0.18.0-3ubuntu2.debian.tar.xz
dpkg-source: info: applying ppc64el-fix.patch

$ cd opensc-0.18.0

$ dpkg-buildpackage
dpkg-buildpackage: info: source package opensc
dpkg-buildpackage: info: source version 0.18.0-3ubuntu2
[...]
dpkg-deb: building package 'opensc-pkcs11' in '../opensc-pkcs11_0.18.0-3ubuntu2_amd64.deb'.
dpkg-deb: building package 'opensc' in '../opensc_0.18.0-3ubuntu2_amd64.deb'.
dpkg-deb: building package 'opensc-dbgsym' in 'debian/.debhelper/scratch-space/build-opensc/opensc-dbgsym_0.18.0-3ubuntu2_amd64.deb'.
dpkg-deb: building package 'opensc-pkcs11-dbgsym' in 'debian/.debhelper/scratch-space/build-opensc-pkcs11/opensc-pkcs11-dbgsym_0.18.0-3ubuntu2_amd64.deb'.
Renaming opensc-dbgsym_0.18.0-3ubuntu2_amd64.deb to opensc-dbgsym_0.18.0-3ubuntu2_amd64.ddeb
Renaming opensc-pkcs11-dbgsym_0.18.0-3ubuntu2_amd64.deb to opensc-pkcs11-dbgsym_0.18.0-3ubuntu2_amd64.ddeb
dpkg-genbuildinfo
dpkg-genchanges >../opensc_0.18.0-3ubuntu2_amd64.changes
dpkg-genchanges: info: not including original source code in upload
dpkg-source --after-build opensc-0.18.0
dpkg-buildpackage: info: binary and diff upload (original source NOT included)
signfile opensc_0.18.0-3ubuntu2.dsc
gpg: skipped "Gianfranco Costamagna <locutusofborg@debian.org>": No secret key
gpg: dpkg-sign.HSiUXvK2/opensc_0.18.0-3ubuntu2.dsc: clear-sign failed: No secret key

dpkg-buildpackage: error: failed to sign .dsc file

$ sudo dpkg --install ../opensc_0.18.0-3ubuntu2_amd64.deb ../opensc-pkcs11_0.18.0-3ubuntu2_amd64.deb
(Reading database ... 526489 files and directories currently installed.)
Preparing to unpack .../opensc_0.18.0-3ubuntu2_amd64.deb ...
[...]

=== First steps ===

We are going to get some basic informations using the command line tool [https://linux.die.net/man/1/pkcs11-tool pkcs11-tool]

List the number of available tokens:

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -L
Available slots:
Slot 0 (0x0): Feitian ePass2003 00 00
C_GetTokenInfo() failed: rv = CKR_TOKEN_NOT_PRESENT
Slot 1 (0x4): Alcor Micro AU9560 01 00
(empty)

Initialise the token for usage with opensc:

$ pkcs15-init --erase-card --reader "Feitian ePass2003 00 00"

$ pkcs15-init --create-pkcs15 --profile pkcs15+onepin --label "myToken" --pin 123456 --puk 12345678 --reader "Feitian ePass2003 00 00"

$ pkcs15-tool --dump --reader "Feitian ePass2003 00 00"

PKCS#15 Card [myToken]:
Version : 0
Serial number : 213C3C500003003D
Manufacturer ID: EnterSafe
Last update : 20190415150218Z
Flags : EID compliant
PIN [User PIN]
Object Flags : [0x3], private, modifiable
ID : 01
Flags : [0x32], local, initialized, needs-padding
Length : min_len:4, max_len:16, stored_len:16
Pad char : 0x00
Reference : 1 (0x01)
Type : ascii-numeric
Path : 3f005015

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -L
Available slots:
Slot 0 (0x0): Feitian ePass2003 00 00
token label : User PIN (myToken)
token manufacturer : EnterSafe
token model : PKCS#15
token flags : login required, rng, token initialized, PIN initialized
hardware version : 0.0
firmware version : 0.0
serial num : 213C3C500003003D
pin min/max : 4/16

Erase the token:

$ pkcs15-init --erase-card --reader "Feitian ePass2003 00 00"

=== Key Generation ===

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so --slot 0 --list-mechanisms
Supported mechanisms:
SHA-1, digest
SHA256, digest
SHA384, digest
SHA512, digest
MD5, digest
RIPEMD160, digest
GOSTR3411, digest
ECDSA, keySize={256,256}, hw, sign
ECDSA-SHA1, keySize={256,256}, hw, sign
ECDSA-KEY-PAIR-GEN, keySize={256,256}, hw, generate_key_pair
RSA-X-509, keySize={512,2048}, hw, decrypt, sign, verify
RSA-PKCS, keySize={512,2048}, hw, decrypt, sign, verify
SHA1-RSA-PKCS, keySize={512,2048}, sign, verify
SHA256-RSA-PKCS, keySize={512,2048}, sign, verify
SHA384-RSA-PKCS, keySize={512,2048}, sign, verify
SHA512-RSA-PKCS, keySize={512,2048}, sign, verify
MD5-RSA-PKCS, keySize={512,2048}, sign, verify
RIPEMD160-RSA-PKCS, keySize={512,2048}, sign, verify
RSA-PKCS-KEY-PAIR-GEN, keySize={512,2048}, generate_key_pair

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so --slot 0 --keypairgen --key-type rsa:2048 --label "my RSA key" --id 42 --login
Logging in to "User PIN (myToken)".
Please enter User PIN:
Key pair generated:
Private Key Object; RSA
label: my RSA key
ID: 42
Usage: decrypt, sign, unwrap
Public Key Object; RSA 2048 bits
label: my RSA key
ID: 42
Usage: encrypt, verify, wrap

=== Sign Data ===

First we export the public key

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so --slot 0 --read-object --id 42 --type pubkey --output-file pubkey.der

Sign a file:

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so --slot 0 --sign --id 42 --mechanism SHA256-RSA-PKCS --input-file test.dat --output-file test.dat.sig --login
Logging in to "User PIN (myToken)".
Please enter User PIN:
Using signature algorithm SHA256-RSA-PKCS

And verify the signature:

$ openssl pkeyutl -pubin -inkey pubkey.der -keyform der -verifyrecover -in test.dat.sig -pkeyopt rsa_padding_mode:pkcs1 -pkeyopt digest:SHA256|xxd
00000000: b5bb 9d80 14a0 f9b1 d61e 21e7 96d7 8dcc ..........!.....
00000010: df13 52f2 3cd3 2812 f485 0b87 8ae4 944c ..R.<.(........L

$ sha256sum test.dat
b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c test.dat

== Used Hardware ==

[[Feitian ePass 2003 FIPS 140-2 Level 2]]

== Courses ==

None yet

== References ==

* https://github.com/OpenSC/OpenSC
* https://github.com/OpenSC/OpenSC/wiki/Feitian-ePass2003
* https://linux.die.net/man/1/pkcs11-tool
* https://www.ftsafe.com/Products/PKI/Standard/Specification
[[Category:Documentation]]

PKCS11 token usage with opensc

2019-04-16T13:19:56Z

Mtausig: Describe RSA key generation

== Summary ==

Basic command line usage of a PKCS#11 token

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: opensc >= 0.18 opensc-pkcs11

== Description ==

The documentation uses the [[Feitian ePass 2003 FIPS 140-2 Level 2]] tokens which can be used with the open source project [https://github.com/OpenSC/OpenSC OpenSC].

The default configuration of the tokens, according to the manufacturer, is as follows:

* Default User PIN: 12345678
* Default SO PIN: entersafe

=== Install opensc-0.18 ===

To install opensc-0.18 on Ubuntu 18.04 download the three source package files from https://packages.ubuntu.com/cosmic/opensc and store them in a build folder. Then run

$ dpkg-source -x opensc_0.18.0-3ubuntu2.dsc
gpgv: Signature made Tue 10 Jul 2018 14:45:55 CEST
gpgv: using RSA key 92978A6E195E4921825F7FF0F34F09744E9F5DD9
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./opensc_0.18.0-3ubuntu2.dsc
dpkg-source: info: extracting opensc in opensc-0.18.0
dpkg-source: info: unpacking opensc_0.18.0.orig.tar.gz
dpkg-source: info: unpacking opensc_0.18.0-3ubuntu2.debian.tar.xz
dpkg-source: info: applying ppc64el-fix.patch

$ cd opensc-0.18.0

$ dpkg-buildpackage
dpkg-buildpackage: info: source package opensc
dpkg-buildpackage: info: source version 0.18.0-3ubuntu2
[...]
dpkg-deb: building package 'opensc-pkcs11' in '../opensc-pkcs11_0.18.0-3ubuntu2_amd64.deb'.
dpkg-deb: building package 'opensc' in '../opensc_0.18.0-3ubuntu2_amd64.deb'.
dpkg-deb: building package 'opensc-dbgsym' in 'debian/.debhelper/scratch-space/build-opensc/opensc-dbgsym_0.18.0-3ubuntu2_amd64.deb'.
dpkg-deb: building package 'opensc-pkcs11-dbgsym' in 'debian/.debhelper/scratch-space/build-opensc-pkcs11/opensc-pkcs11-dbgsym_0.18.0-3ubuntu2_amd64.deb'.
Renaming opensc-dbgsym_0.18.0-3ubuntu2_amd64.deb to opensc-dbgsym_0.18.0-3ubuntu2_amd64.ddeb
Renaming opensc-pkcs11-dbgsym_0.18.0-3ubuntu2_amd64.deb to opensc-pkcs11-dbgsym_0.18.0-3ubuntu2_amd64.ddeb
dpkg-genbuildinfo
dpkg-genchanges >../opensc_0.18.0-3ubuntu2_amd64.changes
dpkg-genchanges: info: not including original source code in upload
dpkg-source --after-build opensc-0.18.0
dpkg-buildpackage: info: binary and diff upload (original source NOT included)
signfile opensc_0.18.0-3ubuntu2.dsc
gpg: skipped "Gianfranco Costamagna <locutusofborg@debian.org>": No secret key
gpg: dpkg-sign.HSiUXvK2/opensc_0.18.0-3ubuntu2.dsc: clear-sign failed: No secret key

dpkg-buildpackage: error: failed to sign .dsc file

$ sudo dpkg --install ../opensc_0.18.0-3ubuntu2_amd64.deb ../opensc-pkcs11_0.18.0-3ubuntu2_amd64.deb
(Reading database ... 526489 files and directories currently installed.)
Preparing to unpack .../opensc_0.18.0-3ubuntu2_amd64.deb ...
[...]

=== First steps ===

We are going to get some basic informations using the command line tool [https://linux.die.net/man/1/pkcs11-tool pkcs11-tool]

List the number of available tokens:

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -L
Available slots:
Slot 0 (0x0): Feitian ePass2003 00 00
C_GetTokenInfo() failed: rv = CKR_TOKEN_NOT_PRESENT
Slot 1 (0x4): Alcor Micro AU9560 01 00
(empty)

Initialise the token for usage with opensc:

$ pkcs15-init --erase-card --reader "Feitian ePass2003 00 00"

$ pkcs15-init --create-pkcs15 --profile pkcs15+onepin --label "myToken" --pin 123456 --puk 12345678 --reader "Feitian ePass2003 00 00"

$ pkcs15-tool --dump --reader "Feitian ePass2003 00 00"

PKCS#15 Card [myToken]:
Version : 0
Serial number : 213C3C500003003D
Manufacturer ID: EnterSafe
Last update : 20190415150218Z
Flags : EID compliant
PIN [User PIN]
Object Flags : [0x3], private, modifiable
ID : 01
Flags : [0x32], local, initialized, needs-padding
Length : min_len:4, max_len:16, stored_len:16
Pad char : 0x00
Reference : 1 (0x01)
Type : ascii-numeric
Path : 3f005015

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -L
Available slots:
Slot 0 (0x0): Feitian ePass2003 00 00
token label : User PIN (myToken)
token manufacturer : EnterSafe
token model : PKCS#15
token flags : login required, rng, token initialized, PIN initialized
hardware version : 0.0
firmware version : 0.0
serial num : 213C3C500003003D
pin min/max : 4/16

Erase the token:

$ pkcs15-init --erase-card --reader "Feitian ePass2003 00 00"

=== Key Generation ===

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so --slot 0 --list-mechanisms
Supported mechanisms:
SHA-1, digest
SHA256, digest
SHA384, digest
SHA512, digest
MD5, digest
RIPEMD160, digest
GOSTR3411, digest
ECDSA, keySize={256,256}, hw, sign
ECDSA-SHA1, keySize={256,256}, hw, sign
ECDSA-KEY-PAIR-GEN, keySize={256,256}, hw, generate_key_pair
RSA-X-509, keySize={512,2048}, hw, decrypt, sign, verify
RSA-PKCS, keySize={512,2048}, hw, decrypt, sign, verify
SHA1-RSA-PKCS, keySize={512,2048}, sign, verify
SHA256-RSA-PKCS, keySize={512,2048}, sign, verify
SHA384-RSA-PKCS, keySize={512,2048}, sign, verify
SHA512-RSA-PKCS, keySize={512,2048}, sign, verify
MD5-RSA-PKCS, keySize={512,2048}, sign, verify
RIPEMD160-RSA-PKCS, keySize={512,2048}, sign, verify
RSA-PKCS-KEY-PAIR-GEN, keySize={512,2048}, generate_key_pair

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so --slot 0 --keypairgen --key-type rsa:2048 --label "my RSA key" --id 42 --login
Logging in to "User PIN (myToken)".
Please enter User PIN:
Key pair generated:
Private Key Object; RSA
label: my RSA key
ID: 42
Usage: decrypt, sign, unwrap
Public Key Object; RSA 2048 bits
label: my RSA key
ID: 42
Usage: encrypt, verify, wrap

== Used Hardware ==

[[Feitian ePass 2003 FIPS 140-2 Level 2]]

== Courses ==

None yet

== References ==

* https://github.com/OpenSC/OpenSC
* https://github.com/OpenSC/OpenSC/wiki/Feitian-ePass2003
* https://linux.die.net/man/1/pkcs11-tool
* https://www.ftsafe.com/Products/PKI/Standard/Specification
[[Category:Documentation]]

PKCS11 token usage with opensc

2019-04-15T15:07:35Z

Mtausig: Add card reset

PKCS11 token usage with opensc

2019-04-15T15:05:38Z

Mtausig: Explain token initialization and opensc update

PKCS11 token usage with opensc

2019-04-15T14:27:17Z

Mtausig: Mtausig moved page PKCS to PKCS11 token usage with opensc without leaving a redirect

== Summary ==

Basic command line usage of a PKCS#11 token

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: opensc opensc-pkcs11

== Description ==

The documentation uses the [[Feitian ePass 2003 FIPS 140-2 Level 2]] tokens which can be used with the open source project [https://github.com/OpenSC/OpenSC OpenSC].

The default configuration of the tokens, according to the manufacturer, is as follows:

* Default User PIN: 12345678
* Default SO PIN: entersafe

=== Basic information gathering ===

We are going to get some basic informations using the command line tool [https://linux.die.net/man/1/pkcs11-tool pkcs11-tool]

List the number of available tokens:

$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -L
Available slots:
Slot 0 (0x0): Feitian ePass2003 00 00
C_GetTokenInfo() failed: rv = CKR_TOKEN_NOT_PRESENT
Slot 1 (0x4): Alcor Micro AU9560 01 00
(empty)

== Used Hardware ==

[[Feitian ePass 2003 FIPS 140-2 Level 2]]

== Courses ==

None yet

== References ==

* https://github.com/OpenSC/OpenSC
* https://linux.die.net/man/1/pkcs11-tool

[[Category:Documentation]]

PKCS11 token usage with opensc

2019-04-15T14:26:17Z

Mtausig: Start pkcs#11 token article

Elliptic Curve Cryptography

2019-02-21T14:23:31Z

Mtausig: Fix <math> elements; remove TOD (install math extension)

== Summary ==

This documentary gives a brief introduction into elliptic curve cryptography

==Elliptic Curve Cryptography ==

Elliptic curve cryptography is a part of asymmetric cryptography, it is based on the mathematical hard problem to find a solution for the elliptic curve discrete logarithm. The calculations are performed on the algebraic structure of elliptic curves over finite fields, which means we compute points on a elliptic curve over finite field by applying the group operations double and add.

The scalar multiplication of a point on an elliptic curve over a finite field is equivalent to the exponentation of a number in a prime field, therefore the inversion is also called discrete logarithm.

First proposed application of elliptic curves in cryptography was random number generations, now ECC is widely used for key establishment and digital signature schemes.

==Simple Weierstrass Elliptic Curve Presentation==

* Simple Weierstrass form curve equation:
<math>y^2 = x^3 + ax + b</math>
The elliptic curve are all points in the x,y coordinates which fulfill the cubic curve equation, whereas a and b are called the characteristic of the curve.
The curve needs to be smooth, which means that it will not contain any singularities such as a cusp or a self intersection,

[[File:Singularities.png]]

This can be also described by the term:
<math>4a^3 + 27b^2 \neq 0</math>

Another characteristic we need to introduce is the point at infinity denoted by 0 (also known as ideal point), which can be thought as identity element infinitly raised on the y axis.
Therefore our points on the elliptic curve over R² all fulfill this equation
<math>\{(x,y) \in R^2 | y^2=x^3+ax+b, 4a^3+27b^2 \neq 0\} \cup \{0\}</math>
and can be presented by:

[[File:Ecc.png]]

A point consists of 2 values P(x,y).

===Group operations on elliptic curves===
According to the group law all points support following operations:
* Point addition: <math> P+Q=R</math>
* Point doubling: <math>P=Q - 2P=R</math>

TODO:Need to install link target extension: https://www.mediawiki.org/wiki/Extension:LinkTarget
Test: <span target="_blank">https://cdn.rawgit.com/andreacorbellini/ecc/920b29a/interactive/reals-add.html</span>

<div class="toccolours mw-collapsible mw-collapsed " style="width:800px; overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Geometric derivation of the point addition by the Tangent Chord Law</div>
<div class="mw-collapsible-content">
[[File:Ecc_addition.png]]

<ref name="HMV">Hankerson, D., A. Menezes and S. Vanstome: Guide to Elliptic Curve Cryptographie. Springer Verlag New York, Inc., 1. Auflage, 2004.</ref>

Given the elliptic curve <math>E:y^2=x^3+ax+b</math> and the points <math>P=(x_1,y_1)</math> and <math>Q=(x_2,y_2)</math>, we can caculate the coordinates of the point <math>R=P+Q=(x_3,y_3)</math> as follows.
1. Calculation of <math>y_3</math>
* We know the equation from the line
<math>y=kx+d \qquad \text{concising of} \qquad k=\frac{\Delta y}{\Delta x}</math>
* Therfore
<math>k=\frac{y_2-y_1}{x_2-x_1}</math> and we can find the intersection with the y-axis and achieve d
<math> d=y_1-kx_1=\frac{y_1\cdot x_2-y_1 \cdot x_1-y_2 \cdot x_1 +y_1 \cdot x_1}{x_2-x_1}=\frac{y_1 \cdot x_2-y_2 \cdot x_1}{x_2-x_1}</math>.
* <math>y_3</math> we can find by insertion in the line equation:

<math>y_3=(-1)\bigg( \frac{y_2-y_1}{x_2-x_1}\cdot x_3 + y_1 - \frac{y_2-y_1}{x_2-x_1}\cdot x_1 \bigg)=\bigg(\frac{y_2-y_1}{x_2-x_1}\bigg)(x_1-x_3)-y_1</math>

2. Calculation of <math>x_3</math>
* Now we insert the values of the line equation into the elliptic curve equation:
<math>\begin{aligned}
(k \cdot x+d)^2 &=x^3+a \cdot x+b\\
k^2x^2+2k \cdot x\cdot d+d^2&=x^3+a \cdot x +b\\
x^3-x^2k^2+x(a-2k \cdot d)+b-d^2 &=0
\end{aligned}</math>
* The cross points can be searched by
<math>\begin{aligned}
(x-x_1)\cdot(x-x_2)\cdot(x-x_3)&=0\\
(x^2-x \cdot x_2 - x \cdot x_1 +x_1 \cdot x_2) \cdot(x-x_3)&=0\\
x^3-x^2 \cdot x_2-x^2 \cdot x_1 + x \cdot x_1 x_2 - x^2 \cdot x_3 + x \cdot x_2 x_3 + x \cdot x_1x_3-x_1x_2x_3 &=0\\
x^3 - x^2 (x_1+x_2+x_3) + x(x_1x_2+x_2x_3+x_1x_3)+x_1x_2x_3 &=0
\end{aligned}</math>
* Now we can conclude from the second term
<math>\begin{aligned}
x^3-x^2 \underline {k^2}+x(a-2k \cdot d)+b-d^2 &=0\\
x^3 - x^2 \underline {(x_1+x_2+x_3)} + x(x_1x_2+x_2x_3+x_1x_3)+x_1x_2x_3 &=0\\
k^2 &=x_1+x_2+x_3
\end{aligned}</math>
* and achieve a solution for <math>x_3</math> by:
<math>x_3=k^2-x_1-x_2 =\bigg(\frac{y_2-y_1}{x_2-x_1}\bigg)^2-x_1-x_2</math>
</div>
</div>

=== Algebraic group of points ===
The points further comply associative and commutative algebraic group laws and the handling of the neutral element:
** closure: <math>P+Q=R \forall P,Q,R \in E</math>b
** associative: <math>P+0=0+P \forall P \in E</math>
** identity element and inverse that: <math>P+(-P) = 0 \forall P \in E</math>
** cummutative: <math>P+(Q+R)=(P+Q)+R \forall P,Q,R \in E</math>

The inverse point of a point P(x,y) is therfore P(x,-y).

== Scalar Multiplication ==

=== Double and Add algorithm ===
=== Calculation in projective coordinates ===
=== Side Channel Attacks ===
=== Montgomery ladder ===

== Standardization of elliptic curves ==

== Curve25519==
Curve25519 is a highly optimized curve proposed by Daniel J. Bernstein (djb) in 2005.
The curve equation is
<math>y^2=x^3+486662x^2+x</math> over a prime field <math>2^{255}-19</math>
=== Edward curves===
== Applications Example Elliptic curve Diffie Hellman key exchange ==

== References ==

<references/>

[[Category:Basic]]

Elliptic Curve Cryptography

2019-02-21T11:05:38Z

Mtausig: Add references section; Remove Todo (cite extension)

== Summary ==

This documentary gives a brief introduction into elliptic curve cryptography

==Elliptic Curve Cryptography ==

Elliptic curve cryptography is a part of asymmetric cryptography, it is based on the mathematical hard problem to find a solution for the elliptic curve discrete logarithm. The calculations are performed on the algebraic structure of elliptic curves over finite fields, which means we compute points on a elliptic curve over finite field by applying the group operations double and add.

The scalar multiplication of a point on an elliptic curve over a finite field is equivalent to the exponentation of a number in a prime field, therefore the inversion is also called discrete logarithm.

First proposed application of elliptic curves in cryptography was random number generations, now ECC is widely used for key establishment and digital signature schemes.

==Simple Weierstrass Elliptic Curve Presentation==

* Simple Weierstrass form curve equation:
TODO need to install math extension: https://www.mediawiki.org/wiki/Extension:Math/advancedSettings#Installing_texvc
<math>y² = x³ + ax + b</math>
The elliptic curve are all points in the x,y coordinates which fulfill the cubic curve equation, whereas a and b are called the characteristic of the curve.
The curve needs to be smooth, which means that it will not contain any singularities such as a cusp or a self intersection,

[[File:Singularities.png]]

This can be also described by the term:
<math>4a^3 + 27b^2 \neq 0</math>

Another characteristic we need to introduce is the point at infinity denoted by 0 (also known as ideal point), which can be thought as identity element infinitly raised on the y axis.
Therefore our points on the elliptic curve over R² all fulfill this equation
<math>\{(x,y)∈R2 | y2=x3+ax+b, 4a3+27b2≠0\} \cup \{0\}</math>
and can be presented by:

[[File:Ecc.png]]

A point consists of 2 values P(x,y).

===Group operations on elliptic curves===
According to the group law all points support following operations:
* Point addition: <math> P+Q=R</math>
* Point doubling: <math> P=Q - 2P=R<\math

TODO:Need to install link target extension: https://www.mediawiki.org/wiki/Extension:LinkTarget
Test: <span target="_blank">https://cdn.rawgit.com/andreacorbellini/ecc/920b29a/interactive/reals-add.html</span>

<div class="toccolours mw-collapsible mw-collapsed " style="width:800px; overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Geometric derivation of the point addition by the Tangent Chord Law</div>
<div class="mw-collapsible-content">
[[File:Ecc_addition.png]]

<ref name="HMV">Hankerson, D., A. Menezes and S. Vanstome: Guide to Elliptic Curve Cryptographie. Springer Verlag New York, Inc., 1. Auflage, 2004.</ref>

Given the elliptic curve <math>E:y^2=x^3+ax+b</math> and the points <math>P=(x_1,y_1)</math> and <math>Q=(x_2,y_2)</math>, we can caculate the coordinates of the point <math>R=P+Q=(x_3,y_3)</math> as follows.
1. Calculation of <math>y_3</math>
* We know the equation from the line
<math>y=kx+d \qquad \text{concising of} \qquad k=\frac{\Delta y}{\Delta x}</math>
* Therfore
<math>k=\frac{y_2-y_1}{x_2-x_1}</math> and we can find the intersection with the y-axis and achieve d
<math> d=y_1-kx_1=\frac{y_1\cdot x_2-y_1 \cdot x_1-y_2 \cdot x_1 +y_1 \cdot x_1}{x_2-x_1}=\frac{y_1 \cdot x_2-y_2 \cdot x_1}{x_2-x_1}</math>.
* <math>y_3</math> we can find by insertion in the line equation:

<math>y_3=(-1)\bigg( \frac{y_2-y_1}{x_2-x_1}\cdot x_3 + y_1 - \frac{y_2-y_1}{x_2-x_1}\cdot x_1 \bigg)=\bigg(\frac{y_2-y_1}{x_2-x_1}\bigg)(x_1-x_3)-y_1</math>

2. Calculation of <math>x_3</math>
* Now we insert the values of the line equation into the elliptic curve equation:
<math>\begin{aligned}
(k \cdot x+d)^2 &=x^3+a \cdot x+b\\
k^2x^2+2k \cdot x\cdot d+d^2&=x^3+a \cdot x +b\\
x^3-x^2k^2+x(a-2k \cdot d)+b-d^2 &=0
\end{aligned}</math>
* The cross points can be searched by
<math>\begin{aligned}
(x-x_1)\cdot(x-x_2)\cdot(x-x_3)&=0\\
(x^2-x \cdot x_2 - x \cdot x_1 +x_1 \cdot x_2) \cdot(x-x_3)&=0\\
x^3-x^2 \cdot x_2-x^2 \cdot x_1 + x \cdot x_1 x_2 - x^2 \cdot x_3 + x \cdot x_2 x_3 + x \cdot x_1x_3-x_1x_2x_3 &=0\\
x^3 - x^2 (x_1+x_2+x_3) + x(x_1x_2+x_2x_3+x_1x_3)+x_1x_2x_3 &=0
\end{aligned}</math>
* Now we can conclude from the second term
<math>\begin{aligned}
x^3-x^2 \underline {k^2}+x(a-2k \cdot d)+b-d^2 &=0\\
x^3 - x^2 \underline {(x_1+x_2+x_3)} + x(x_1x_2+x_2x_3+x_1x_3)+x_1x_2x_3 &=0\\
k^2 &=x_1+x_2+x_3
\end{aligned}</math>
* and achieve a solution for <math>x_3</math> by:
<math>x_3=k^2-x_1-x_2 =\bigg(\frac{y_2-y_1}{x_2-x_1}\bigg)^2-x_1-x_2</math>
</div>
</div>

=== Algebraic group of points ===
The points further comply associative and commutative algebraic group laws and the handling of the neutral element:
** closure: <math>P+Q=R \forall P,Q,R \in E<\math>b
** associative: <math>P+0=0+P \forall P \in E<\math>
** identity element and inverse that: <math>P+(-P) = 0 \forall P \in E<\math>
** cummutative: <math>P+(Q+R)=(P+Q)+R \forall P,Q,R \in E<\math>

The inverse point of a point P(x,y) is therfore P(x,-y).

== Scalar Multiplication ==

=== Double and Add algorithm ===
=== Calculation in projective coordinates ===
=== Side Channel Attacks ===
=== Montgomery ladder ===

== Standardization of elliptic curves ==

== Curve25519==
Curve25519 is a highly optimized curve proposed by Daniel J. Bernstein (djb) in 2005.
The curve equation is
<math>y^2=x^3+486662x^2+x<\math> over a prime field <math>2^{255}-19</math>
=== Edward curves===
== Applications Example Elliptic curve Diffie Hellman key exchange ==

== References ==

<references/>

[[Category:Basic]]

MediaWiki:Sidebar

2019-01-16T15:52:44Z

Mtausig: Fix Basics link

MediaWiki:Sidebar

2019-01-16T15:50:44Z

Mtausig: Add "basics" category

Template:Device

2019-01-09T15:55:38Z

Mtausig: Format change (no float right for table), additional information (technologies, specification, included equipment, description)

{| class="wikitable" style=""
|+Information
|-
|'''Name'''
|{{{device_name}}}
|-
|'''Manufacturer'''
|{{{manufacturer}}}
|-
|'''Link'''
|{{{link}}}
|-
|'''Specification'''
|{{{technicalSpecification}}}
|-
|'''Technologies'''
|{{{supportedTechnologies}}}
|-
|'''Included equipment'''
|{{{includedEquipment}}}
|-
|
|{{{image_link}}}
|}

== Description ==

{{{description}}}

== Documentations ==

{{:Special:Whatlinkshere/{{FULLPAGENAME}}|hideredirs=1|hidetrans=1}}

[[Category:Hardware]]

Template:Documentation

2018-11-07T11:34:26Z

Mtausig: Fix typo

== Summary ==

Description what this documentation is about

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: git emacs

In order to complete these steps, you must have followed [[Some Other Documentation]] before.

== Description ==

=== Step 1 ===

Enter these commands in the shell

echo foo
echo bar

=== Step 2 ===

Make sure to read

* War and Peace
* Lord of the Rings
* The Baroque Cycle

== Used Hardware ==

[[Device to be used with this documentation]]
[[Maybe another device to be used with this documentation]]

== Courses ==

* [[A course where this documentation was used]] (2017, 2018)
* [[Another one]] (2018)

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Template:Documentation

2018-10-01T11:10:07Z

Mtausig: Add course references to template

== Summary ==

Description what this documentation is about

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: git emacs

In order to complete these steps, you must have followed [[Some Other Documentation]] before.

== Description ==

=== Step 1 ===

Enter these commands in the shell

echo foo
echo bar

=== Step 2 ===

Make sure to read

* War and Peace
* Lord of the Rings
* The Baroque Cycle

== Used Hardware ==

[[Device to be used with this documentation]]
[[Maybe anotger device to be used with this documentation]]

== Courses ==

* [[A course where this documentation was used]] (2017, 2018)
* [[Another one]] (2018)

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Einführendes Wahlfachprojekt

2018-10-01T11:08:22Z

Mtausig: Fix table

{| class="wikitable" style="float:right;"
|+Information
|-
|'''Studium'''
|ITTK (Informationstechnologien und Telekommunikation)
|-
|'''Semester'''
|4
|-
|'''Typ'''
|PR (Praktikum)
|}

== Documentations ==

This course has used the following documentations:

{{:Special:Whatlinkshere/{{FULLPAGENAME}}|hideredirs=1|hidetrans=1}}

[[Category:Course]]

Template:Course

2018-10-01T11:08:03Z

Mtausig: Fix table

Template:Course

2018-10-01T11:07:20Z

Mtausig: Create template for courses

{| class="wikitable" style="float:right;"
|+Information
|-
|'''Studium'''
|ITTK (Informationstechnologien und Telekommunikation)
|-
|'''Semester'''
|4
|-
|'''Typ'''
|PR (Praktikum)
|-
|
|{{{image_link}}}
|}

== Documentations ==

This course has used the following documentations:

{{:Special:Whatlinkshere/{{FULLPAGENAME}}|hideredirs=1|hidetrans=1}}

[[Category:Course]]

Category:Course

2018-10-01T11:06:22Z

Mtausig: Create course page

A list of all courses which have been using documentations from the ELVIS project.

<inputbox>
type=create
width=100
break=no
buttonlabel=Create a new course
default=(Course title)
preload=Template:Course
</inputbox>

Einführendes Wahlfachprojekt

2018-10-01T11:04:52Z

Mtausig: Create Einführendes Wahlfachprojekt

{| class="wikitable" style="float:right;"
|+Information
|-
|'''Studium'''
|ITTK (Informationstechnologien und Telekommunikation)
|-
|'''Semester'''
|4
|-
|'''Typ'''
|PR (Praktikum)
|-
|
|{{{image_link}}}
|}

== Documentations ==

This course has used the following documentations:

{{:Special:Whatlinkshere/{{FULLPAGENAME}}|hideredirs=1|hidetrans=1}}

[[Category:Course]]

Bluetooth Hacking Ubertooth

2018-10-01T10:44:09Z

Mtausig: /* Courses */ Add year to course

== Summary ==

These are the results of a student project on Bluetooth hacking using an [[Ubertooth One, 2.4 GHz wireless development platform]]

== Requirements ==

To produce the results, the book [[Hacking Internet of Things]] was used.

The [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]] was tested on the following devices:

* [[Osram Ledvance Smart+ Multicolor HomeKit Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]

== Authors ==

The project was conducted for the course [[Einführendes Wahlfachprojekt]] in the summer term 2018 by the bachelor students:

* Stefan Buschbeck
* Stefan Trinko
* Sebastian Ukleja

== Results ==

* A [[:File:BLE Hacking Buschbeck Trinko Ukleja.pdf|documentation]] about the Bluetooth protocol itself and the analysis of the students
* The [[:File:Capture Files BLE.zip|capture files]] produced with the [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]]

== Used Hardware ==

* [[Ubertooth One, 2.4 GHz wireless development platform]]
* [[Osram Ledvance Smart+ Multicolor HomeKit Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]
* [[Hacking Internet of Things]]

== Courses ==

* [[Einführendes Wahlfachprojekt]] (2018)

== References ==

[[Category:Documentation]]

Bluetooth Hacking Ubertooth

2018-10-01T10:42:32Z

Mtausig: Add link to course

Bluetooth Hacking Ubertooth

2018-09-27T09:23:07Z

Mtausig: Fix hardware used

== Summary ==

These are the results of a student project on Bluetooth hacking using an [[Ubertooth One, 2.4 GHz wireless development platform]]

== Requirements ==

To produce the results, the book [[Hacking Internet of Things]] was used.

The [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]] was tested on the following devices:

* [[Osram Ledvance Smart+ Multicolor HomeKit Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]

== Authors ==

The project was conducted for the course ''Einführendes Wahlfachprojekt'' in the summer term 2018 by the bachelor students:

* Stefan Buschbeck
* Stefan Trinko
* Sebastian Ukleja

== Results ==

* A [[:File:BLE Hacking Buschbeck Trinko Ukleja.pdf|documentation]] about the Bluetooth protocol itself and the analysis of the students
* The [[:File:Capture Files BLE.zip|capture files]] produced with the [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]]

== Used Hardware ==

* [[Ubertooth One, 2.4 GHz wireless development platform]]
* [[Osram Ledvance Smart+ Multicolor HomeKit Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]
* [[Hacking Internet of Things]]

== References ==

[[Category:Documentation]]

Bluetooth Hacking Ubertooth

2018-09-27T09:19:27Z

Mtausig: Add links to the files produced by the students

== Summary ==

These are the results of a student project on Bluetooth hacking using an [[Ubertooth One, 2.4 GHz wireless development platform]]

== Requirements ==

To produce the results, the book [[Hacking Internet of Things]] was used.

The [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]] was tested on the following devices:

* [[Osram Ledvance Smart+ Dimmable LED Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]

== Authors ==

The project was conducted for the course ''Einführendes Wahlfachprojekt'' in the summer term 2018 by the bachelor students:

* Stefan Buschbeck
* Stefan Trinko
* Sebastian Ukleja

== Results ==

* A [[:File:BLE Hacking Buschbeck Trinko Ukleja.pdf|documentation]] about the Bluetooth protocol itself and the analysis of the students
* The [[:File:Capture Files BLE.zip|capture files]] produced with the [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]]

== Used Hardware ==

* [[Ubertooth One, 2.4 GHz wireless development platform]]
* [[Osram Ledvance Smart+ Dimmable LED Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]
* [[Hacking Internet of Things]]

== References ==

[[Category:Documentation]]

File:Capture Files BLE.zip

2018-09-27T09:15:38Z

Mtausig: Capture files from a Wahlfachprojekt on Bluetooth hacking. Created by the students Stefan Buschbeck, Stefan Trinko and Sebastian Ukleja.

== Summary ==
Capture files from a Wahlfachprojekt on Bluetooth hacking.
Created by the students Stefan Buschbeck, Stefan Trinko and Sebastian Ukleja.

File:BLE Hacking Buschbeck Trinko Ukleja.pdf

2018-09-27T09:14:21Z

Mtausig: Report from a Wahlfachprojekt on Bluetooth hacking. Created by the students Stefan Buschbeck, Stefan Trinko and Sebastian Ukleja.

== Summary ==
Report from a Wahlfachprojekt on Bluetooth hacking.
Created by the students Stefan Buschbeck, Stefan Trinko and Sebastian Ukleja.

Bluetooth Hacking Ubertooth

2018-09-27T08:48:34Z

Mtausig: Create documentation for "Bluetooth hacking" Wahlfachprojekt

== Summary ==

These are the results of a student project on Bluetooth hacking using an [[Ubertooth One, 2.4 GHz wireless development platform]]

== Requirements ==

To produce the results, the book [[Hacking Internet of Things]] was used.

The [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]] was tested on the following devices:

* [[Osram Ledvance Smart+ Dimmable LED Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]

== Authors ==

The project was conducted for the course ''Einführendes Wahlfachprojekt'' in the summer term 2018 by the bachelor students:

* Stefan Buschbeck
* Stefan Trinko
* Sebastian Ukleja

== Results ==

* A documentation about the Bluetooth protocol itself and the analysis of the students:
* The capture files produced with the [[Ubertooth One, 2.4 GHz wireless development platform|Ubertooth]]

== Used Hardware ==

* [[Ubertooth One, 2.4 GHz wireless development platform]]
* [[Osram Ledvance Smart+ Dimmable LED Classic A60 10W E27]]
* [[DOG&BONE® Bluetooth-Vorhängeschloss, Rot]]
* [[EQIVA Bluetooth Smart Türschlossantrieb]]
* [[Hacking Internet of Things]]

== References ==

[[Category:Documentation]]

Template:Device

2018-09-26T15:10:38Z

Mtausig: Protected "Template:Device" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

{| class="wikitable" style="float:right;"
|+Information
|-
|'''Name'''
|{{{device_name}}}
|-
|'''Manufacturer'''
|{{{manufacturer}}}
|-
|'''Link'''
|{{{link}}}
|-
|
|{{{image_link}}}
|}

== Documentations ==

{{:Special:Whatlinkshere/{{FULLPAGENAME}}|hideredirs=1|hidetrans=1}}

[[Category:Hardware]]

Elvis Wiki:About

2018-09-26T15:07:40Z

Mtausig: Protected "Embedded Lab Vienna for IoT & Security:About" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

ELVIS is a teaching project run by the [https://www.fh-campuswien.ac.at/forschung/kompetenzzentren-fuer-forschung-und-entwicklung/kompetenzzentrum-fuer-it-security.html Competence Centre for IT-Security] at the [https://www.fh-campuswien.ac.at/ University of Applied Sciences Campus Vienna].

Elvis Wiki:About

2018-09-26T15:07:34Z

Mtausig: Create about page

MediaWiki:Sidebar

2018-09-26T15:02:06Z

Mtausig: Add link to documentations

MediaWiki:Sidebar

2018-09-26T15:01:16Z

Mtausig: Fix Hardware list

MediaWiki:Sidebar

2018-09-26T15:00:50Z

Mtausig: Add link to hardware list

Main Page

2018-09-26T14:44:43Z

Mtausig: Center MA23 logo

Main Page

2018-09-26T14:44:19Z

Mtausig: Remove "Getting Started"

Main Page

2018-09-26T14:42:25Z

Mtausig: Protected "Main Page" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

This Wiki contains documentations from the ELVIS project.

{| style="margin: auto;"
|-
| [[File:ElvisLogo.png]]
|}

You can find a [[:Category:Hardware|List of available hardware]] as well as a list of [[:Category:Documentation|documentations]].

== Acknowledgments ==

The ELVIS project is generously funded by the MA23

[[File:Ma23_logo.jpg|150px]]

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Category:Hardware

2018-09-26T14:42:14Z

Mtausig: Protected "Category:Hardware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

A list of the hardware available in the ELVIS lab.

Category:Documentation

2018-09-26T14:42:02Z

Mtausig: Protected "Category:Documentation" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

A list of all documentations created by the ELVIS project.

<inputbox>
type=create
width=100
break=no
buttonlabel=Create a new documentation
default=(Article title)
preload=Template:Documentation
</inputbox>

Template:Documentation

2018-09-26T14:41:47Z

Mtausig: Protected "Template:Documentation" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

== Summary ==

Description what this documentation is about

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: git emacs

In order to complete these steps, you must have followed [[Some Other Documentation]] before.

== Description ==

=== Step 1 ===

Enter these commands in the shell

echo foo
echo bar

=== Step 2 ===

Make sure to read

* War and Peace
* Lord of the Rings
* The Baroque Cycle

== Used Hardware ==

[[Device to be used with this documentation]]
[[Maybe anotger device to be used with this documentation]]

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Category:Documentation

2018-09-26T14:41:08Z

Mtausig: Add template to documentation creation

Template:Documentation

2018-09-26T14:36:58Z

Mtausig: Create Documentation template

== Summary ==

Description what this documentation is about

== Requirements ==

* Operating system: Ubuntu 18.04 bionic amd64
* Packages: git emacs

In order to complete these steps, you must have followed [[Some Other Documentation]] before.

== Description ==

=== Step 1 ===

Enter these commands in the shell

echo foo
echo bar

=== Step 2 ===

Make sure to read

* War and Peace
* Lord of the Rings
* The Baroque Cycle

== Used Hardware ==

[[Device to be used with this documentation]]
[[Maybe anotger device to be used with this documentation]]

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Category:Hardware

2018-09-26T14:29:04Z

Mtausig: Remove create hardware box

A list of the hardware available in the ELVIS lab.

Main Page

2018-09-26T14:28:47Z

Mtausig: Reduce MA23 logo size

User:Mtausig

2018-09-26T14:24:39Z

Mtausig: Created page with "Mathias Tausig"

Mathias Tausig