<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://elvis.hcw.ac.at/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=PSimetzberger</id>
	<title>Elvis Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://elvis.hcw.ac.at/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=PSimetzberger"/>
	<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php/Special:Contributions/PSimetzberger"/>
	<updated>2026-09-10T18:07:39Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.5</generator>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=CyberChef&amp;diff=17237</id>
		<title>CyberChef</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=CyberChef&amp;diff=17237"/>
		<updated>2024-12-17T18:23:24Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Cyberchef is a tool that is used to execute various encoding, encryption, data processing and transformation tasks. It was created by the GCHQ (Government Communications Headquarters) and is also known as the &amp;quot;Cyber Swiss Army Knife&amp;quot;, because of its wide variety of operations. A link to a online version can be found in the Readme file in the official github repository &amp;lt;ref name=&amp;quot;Cyberchef&amp;quot;&amp;gt;Cyberchef. Available: https://github.com/gchq/CyberChef. Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
The whole tool can be downloaded using docker. The following command pulls the latest version of the program and starts a container. The webpage can then be seen on the localhost on port 8080 on the browser.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker run -it -p 8080:80 ghcr.io/gchq/cyberchef:latest&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, the program can be build directly. For this the repository needs to be cloned and within the folder the following commands need to be executed.&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker build --tag cyberchef --ulimit nofile=10000 .&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker run -it -p 8080:80 cyberchef&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== How to use ==&lt;br /&gt;
&lt;br /&gt;
The webpage has 4 important parts.The first one is the Operations tab. There is a list of all functions that can be executed. Double clicking on a function adds it to the second tab called recipe. Alternatively, the function can be dragged into the recipe tab This tab contains a list of all functions that will be executed. The input will go through all functions from top to bottom and the output of the function above will be the input of the function below. The third tab is for the input. Here the user can paste whatever input they want to process. The last tab is for the output. The result of the last function will be posted here. The tool also allows to save and load recipes.&lt;br /&gt;
[[File:Cyberchef.png|500px|thumb|center|Cyberchef &amp;lt;ref name=&amp;quot;BOB&amp;quot;&amp;gt;Cyberchef Webpage Available: https://gchq.github.io/CyberChef/ Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Basic]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=File:Cyberchef.png&amp;diff=17236</id>
		<title>File:Cyberchef.png</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=File:Cyberchef.png&amp;diff=17236"/>
		<updated>2024-12-17T18:17:05Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17235</id>
		<title>SHA-3</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17235"/>
		<updated>2024-12-17T18:10:51Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
SHA-3 is a cryptographic hash function and the newest addition to the SHA family. Guido Bertoni, Joan Daemen, Michael Peeters and Gilles Van Assche created the algorithm with the name Keccak. In 2012 Keccak won the american SHA-3 contest organized by NIST. On the 5th of August 2015 it was standardised, allowing for an alternative to SHA-2 (which is still considered save). &amp;lt;ref name=&amp;quot;NIST_HASH&amp;quot;&amp;gt; NIST Documentation, Available:  https://csrc.nist.gov/projects/hash-functions, Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== General information ==&lt;br /&gt;
&lt;br /&gt;
=== Hashing Algorithm ===&lt;br /&gt;
A hashing algorithm is a mathenmatical function that converts an input to a fixed-size output which is often refered as hash value or digest. Hashing is a crucial part of cyber security and widely used in data integrity, verification, cryptography and more.&lt;br /&gt;
&lt;br /&gt;
Hashing algorithms are deterministic, meaning that the same input will always result in the same output. Another characteristic is that a small change in the input leads to significant changes in the hash. Further characteristics can be found under Hashing goals.&lt;br /&gt;
&lt;br /&gt;
=== Hashing goals ===&lt;br /&gt;
&lt;br /&gt;
SHA-3 like every other hashing algorithm pursues the same 5 goals.&lt;br /&gt;
* Compression: The algorithm must produce the same fixed length output regardless of the length of the input&lt;br /&gt;
* Efficient: It must be fast to calculate the function as it will be calculated a lot.&lt;br /&gt;
* Pre-image resistance: Knowing the algorithm and output it should be infeasable to calculate the input&lt;br /&gt;
* 2nd Pre-image resistance: Given an input and output of the algorithm, it should be infeasable to calculate a second input resulting in the same output&lt;br /&gt;
* Collision resistance: Finding 2 inputs giving the same output should be implausible&lt;br /&gt;
&lt;br /&gt;
=== Hashing Process ===&lt;br /&gt;
Algorithms follow a simple 3 step process to calculate the hash.&lt;br /&gt;
* Pre-processing: The goal is to get the input in a way the algorithm can handle. This includes processes like padding or splitting the input into blocks&lt;br /&gt;
* Initialization: Initial variables and constants are set&lt;br /&gt;
* Execution: The actual hashing algorithm is executed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Calculation ==&lt;br /&gt;
&lt;br /&gt;
=== Sponge construction ===&lt;br /&gt;
The Keccak algorithm is a so called sponge construction. It is called that, because it &amp;quot;absorbs&amp;quot; the input and then &amp;quot;squeezes&amp;quot; out the output.&lt;br /&gt;
&lt;br /&gt;
The algorithm uses a 1600-bit array called state which it uses for the caluclations and which will contain the output afterwards. It is divided into 2 parts. The first one is called rate (r) and it will absorb the input. The second part is called capacity (c) and its only function is to make the algorithm more secure.&lt;br /&gt;
&lt;br /&gt;
After the state is initialized, the input message is divided into parts that are as long as the rate. If needed, the last input block will be padded by adding a 1 and then fill it up with 0 to the needed length.&lt;br /&gt;
&lt;br /&gt;
[[File:SpongeConstruction.svg.png|500px|thumb|right|Sponge Construction model &amp;lt;ref name=&amp;quot;BOB&amp;quot;&amp;gt;Sponge Construction, Available: https://de.wikipedia.org/wiki/Datei:SpongeConstruction.svg. Accessed: Oct. 01, 2024&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
The first input block is now XORed with the state. Afterwards the Keccak algorithm will be used on the state. Then the next block is XORed and the whole process repeats until all chunks are absorbed into the algorithm&lt;br /&gt;
&lt;br /&gt;
Lastly the output is &amp;quot;squeezed&amp;quot; out. The first r bits of the state are taken as the hash value. If the output length is larger than r, the Keccak algorithm will be used again on the state and the next r bits are extraced. This process can repeat until the output length is reached. &amp;lt;ref name=&amp;quot;NIST_Fips&amp;quot;&amp;gt; NIST Documentation, Available:  https://csrc.nist.gov/pubs/fips/202/final, Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keccak-p permutation ===&lt;br /&gt;
This is the core component of the SHA-3 algorithm. It contains 5 different operations which are executed in order on the state array. To ensure the hashing goals, multiple rounds of the permutation are done in one call of the algorithm. The default for SHA-3 are 24 rounds, meaning that a single call will execute the Keccak-p permutation 24 times before it returns the state. Because of this, the number of rounds is usually an additional input parameter.&lt;br /&gt;
The state is usually divided into a 5x5 matrix with 64 bits in each position.&lt;br /&gt;
[[File:Sha3.png|150px|thumb|right|Keccak-p permutation sequence&amp;lt;ref&amp;gt; Keccak-p permutation sequence &amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
* Step 1, Theta: XOR each bit with a representative value derived from neighboring columns&lt;br /&gt;
* Step 2, Rho: Rotates each lane&#039;s bits by a specific offset based on its position&lt;br /&gt;
* Step 3, Pi: Rearranges the positions of the lanes&lt;br /&gt;
* Step 4, Chi: Applies a non-linear transformation to each row using bitwise operations&lt;br /&gt;
* Step 5, Iota: XOR with round-specific constants to prevent symmetry&lt;br /&gt;
&amp;lt;ref name=&amp;quot;NIST_Fips&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[[Category:Basic]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17234</id>
		<title>SHA-3</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17234"/>
		<updated>2024-12-17T18:05:13Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
SHA-3 is a cryptographic hash function and the newest addition to the SHA family. Guido Bertoni, Joan Daemen, Michael Peeters and Gilles Van Assche created the algorithm with the name Keccak. In 2012 Keccak won the american SHA-3 contest organized by NIST. On the 5th of August 2015 it was standardised, allowing for an alternative to SHA-2 (which is still considered save). &amp;lt;ref name=&amp;quot;NIST_HASH&amp;quot;&amp;gt; NIST Documentation, Available:  https://csrc.nist.gov/projects/hash-functions, Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== General information ==&lt;br /&gt;
&lt;br /&gt;
=== Hashing Algorithm ===&lt;br /&gt;
A hashing algorithm is a mathenmatical function that converts an input to a fixed-size output which is often refered as hash value or digest. Hashing is a crucial part of cyber security and widely used in data integrity, verification, cryptography and more.&lt;br /&gt;
&lt;br /&gt;
Hashing algorithms are deterministic, meaning that the same input will always result in the same output. Another characteristic is that a small change in the input leads to significant changes in the hash. Further characteristics can be found under Hashing goals.&lt;br /&gt;
&lt;br /&gt;
=== Hashing goals ===&lt;br /&gt;
&lt;br /&gt;
SHA-3 like every other hashing algorithm pursues the same 5 goals.&lt;br /&gt;
* Compression: The algorithm must produce the same fixed length output regardless of the length of the input&lt;br /&gt;
* Efficient: It must be fast to calculate the function as it will be calculated a lot.&lt;br /&gt;
* Pre-image resistance: Knowing the algorithm and output it should be infeasable to calculate the input&lt;br /&gt;
* 2nd Pre-image resistance: Given an input and output of the algorithm, it should be infeasable to calculate a second input resulting in the same output&lt;br /&gt;
* Collision resistance: Finding 2 inputs giving the same output should be implausible&lt;br /&gt;
&lt;br /&gt;
=== Hashing Process ===&lt;br /&gt;
Algorithms follow a simple 3 step process to calculate the hash.&lt;br /&gt;
* Pre-processing: The goal is to get the input in a way the algorithm can handle. This includes processes like padding or splitting the input into blocks&lt;br /&gt;
* Initialization: Initial variables and constants are set&lt;br /&gt;
* Execution: The actual hashing algorithm is executed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Calculation ==&lt;br /&gt;
&lt;br /&gt;
=== Sponge construction ===&lt;br /&gt;
The Keccak algorithm is a so called sponge construction. It is called that, because it &amp;quot;absorbs&amp;quot; the input and then &amp;quot;squeezes&amp;quot; out the output.&lt;br /&gt;
&lt;br /&gt;
The algorithm uses a 1600-bit array called state which it uses for the caluclations and which will contain the output afterwards. It is divided into 2 parts. The first one is called rate (r) and it will absorb the input. The second part is called capacity (c) and its only function is to make the algorithm more secure.&lt;br /&gt;
&lt;br /&gt;
After the state is initialized, the input message is divided into parts that are as long as the rate. If needed, the last input block will be padded by adding a 1 and then fill it up with 0 to the needed length.&lt;br /&gt;
&lt;br /&gt;
[[File:SpongeConstruction.svg.png|500px|right|Sponge Construction model &amp;lt;ref name=&amp;quot;BOB&amp;quot;&amp;gt;Sponge Construction, Available: https://de.wikipedia.org/wiki/Datei:SpongeConstruction.svg. Accessed: Oct. 01, 2024&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
The first input block is now XORed with the state. Afterwards the Keccak algorithm will be used on the state. Then the next block is XORed and the whole process repeats until all chunks are absorbed into the algorithm&lt;br /&gt;
&lt;br /&gt;
Lastly the output is &amp;quot;squeezed&amp;quot; out. The first r bits of the state are taken as the hash value. If the output length is larger than r, the Keccak algorithm will be used again on the state and the next r bits are extraced. This process can repeat until the output length is reached. &amp;lt;ref name=&amp;quot;NIST_Fips&amp;quot;&amp;gt; NIST Documentation, Available:  https://csrc.nist.gov/pubs/fips/202/final, Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keccak-p permutation ===&lt;br /&gt;
This is the core component of the SHA-3 algorithm. It contains 5 different operations which are executed in order on the state array. To ensure the hashing goals, multiple rounds of the permutation are done in one call of the algorithm. The default for SHA-3 are 24 rounds, meaning that a single call will execute the Keccak-p permutation 24 times before it returns the state. Because of this, the number of rounds is usually an additional input parameter.&lt;br /&gt;
The state is usually divided into a 5x5 matrix with 64 bits in each position.&lt;br /&gt;
&lt;br /&gt;
[[File:Sha3.png|190px|right|&amp;lt;ref&amp;gt; Keccak-p permutation sequence &amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
* Step 1, Theta: XOR each bit with a representative value derived from neighboring columns&lt;br /&gt;
* Step 2, Rho: Rotates each lane&#039;s bits by a specific offset based on its position&lt;br /&gt;
* Step 3, Pi: Rearranges the positions of the lanes&lt;br /&gt;
* Step 4, Chi: Applies a non-linear transformation to each row using bitwise operations&lt;br /&gt;
* Step 5, Iota: XOR with round-specific constants to prevent symmetry&lt;br /&gt;
&amp;lt;ref name=&amp;quot;NIST_Fips&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[[Category:Basic]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17233</id>
		<title>SHA-3</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17233"/>
		<updated>2024-12-17T18:03:56Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
SHA-3 is a cryptographic hash function and the newest addition to the SHA family. Guido Bertoni, Joan Daemen, Michael Peeters and Gilles Van Assche created the algorithm with the name Keccak. In 2012 Keccak won the american SHA-3 contest organized by NIST. On the 5th of August 2015 it was standardised, allowing for an alternative to SHA-2 (which is still considered save). &amp;lt;ref name=&amp;quot;NIST_HASH&amp;quot;&amp;gt; NIST Documentation, Available:  https://csrc.nist.gov/projects/hash-functions, Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== General information ==&lt;br /&gt;
&lt;br /&gt;
=== Hashing Algorithm ===&lt;br /&gt;
A hashing algorithm is a mathenmatical function that converts an input to a fixed-size output which is often refered as hash value or digest. Hashing is a crucial part of cyber security and widely used in data integrity, verification, cryptography and more.&lt;br /&gt;
&lt;br /&gt;
Hashing algorithms are deterministic, meaning that the same input will always result in the same output. Another characteristic is that a small change in the input leads to significant changes in the hash. Further characteristics can be found under Hashing goals.&lt;br /&gt;
&lt;br /&gt;
=== Hashing goals ===&lt;br /&gt;
&lt;br /&gt;
SHA-3 like every other hashing algorithm pursues the same 5 goals.&lt;br /&gt;
* Compression: The algorithm must produce the same fixed length output regardless of the length of the input&lt;br /&gt;
* Efficient: It must be fast to calculate the function as it will be calculated a lot.&lt;br /&gt;
* Pre-image resistance: Knowing the algorithm and output it should be infeasable to calculate the input&lt;br /&gt;
* 2nd Pre-image resistance: Given an input and output of the algorithm, it should be infeasable to calculate a second input resulting in the same output&lt;br /&gt;
* Collision resistance: Finding 2 inputs giving the same output should be implausible&lt;br /&gt;
&lt;br /&gt;
=== Hashing Process ===&lt;br /&gt;
Algorithms follow a simple 3 step process to calculate the hash.&lt;br /&gt;
* Pre-processing: The goal is to get the input in a way the algorithm can handle. This includes processes like padding or splitting the input into blocks&lt;br /&gt;
* Initialization: Initial variables and constants are set&lt;br /&gt;
* Execution: The actual hashing algorithm is executed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Calculation ==&lt;br /&gt;
&lt;br /&gt;
=== Sponge construction ===&lt;br /&gt;
The Keccak algorithm is a so called sponge construction. It is called that, because it &amp;quot;absorbs&amp;quot; the input and then &amp;quot;squeezes&amp;quot; out the output.&lt;br /&gt;
&lt;br /&gt;
The algorithm uses a 1600-bit array called state which it uses for the caluclations and which will contain the output afterwards. It is divided into 2 parts. The first one is called rate (r) and it will absorb the input. The second part is called capacity (c) and its only function is to make the algorithm more secure.&lt;br /&gt;
&lt;br /&gt;
After the state is initialized, the input message is divided into parts that are as long as the rate. If needed, the last input block will be padded by adding a 1 and then fill it up with 0 to the needed length.&lt;br /&gt;
&lt;br /&gt;
[[File:SpongeConstruction.svg.png|500px|right|Sponge Construction model &amp;lt;ref name=&amp;quot;BOB&amp;quot;&amp;gt;Sponge Construction, Available: https://de.wikipedia.org/wiki/Datei:SpongeConstruction.svg. Accessed: Oct. 01, 2024&amp;lt;/ref&amp;gt;]]&lt;br /&gt;
&lt;br /&gt;
The first input block is now XORed with the state. Afterwards the Keccak algorithm will be used on the state. Then the next block is XORed and the whole process repeats until all chunks are absorbed into the algorithm&lt;br /&gt;
&lt;br /&gt;
Lastly the output is &amp;quot;squeezed&amp;quot; out. The first r bits of the state are taken as the hash value. If the output length is larger than r, the Keccak algorithm will be used again on the state and the next r bits are extraced. This process can repeat until the output length is reached. &amp;lt;ref name=&amp;quot;NIST_Fips&amp;quot;&amp;gt; NIST Documentation, Available:  https://csrc.nist.gov/pubs/fips/202/final, Accessed: Oct. 10, 2024&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keccak-p permutation ===&lt;br /&gt;
This is the core component of the SHA-3 algorithm. It contains 5 different operations which are executed in order on the state array. To ensure the hashing goals, multiple rounds of the permutation are done in one call of the algorithm. The default for SHA-3 are 24 rounds, meaning that a single call will execute the Keccak-p permutation 24 times before it returns the state. Because of this, the number of rounds is usually an additional input parameter.&lt;br /&gt;
The state is usually divided into a 5x5 matrix with 64 bits in each position.&lt;br /&gt;
&lt;br /&gt;
[[File:Sha3.png|190px|right|Keccak-p permutation sequence]]&lt;br /&gt;
&lt;br /&gt;
* Step 1, Theta: XOR each bit with a representative value derived from neighboring columns&lt;br /&gt;
* Step 2, Rho: Rotates each lane&#039;s bits by a specific offset based on its position&lt;br /&gt;
* Step 3, Pi: Rearranges the positions of the lanes&lt;br /&gt;
* Step 4, Chi: Applies a non-linear transformation to each row using bitwise operations&lt;br /&gt;
* Step 5, Iota: XOR with round-specific constants to prevent symmetry&lt;br /&gt;
&amp;lt;ref name=&amp;quot;NIST_Fips&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
[[Category:Basic]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=File:Sha3.png&amp;diff=17225</id>
		<title>File:Sha3.png</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=File:Sha3.png&amp;diff=17225"/>
		<updated>2024-12-17T16:50:41Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: The sequence of the Keccak-p permutation.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
The sequence of the Keccak-p permutation.&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=File:SpongeConstruction.svg.png&amp;diff=17224</id>
		<title>File:SpongeConstruction.svg.png</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=File:SpongeConstruction.svg.png&amp;diff=17224"/>
		<updated>2024-12-17T16:49:58Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: A model showing the sequence of sponge construction&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
A model showing the sequence of sponge construction&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=CyberChef&amp;diff=17223</id>
		<title>CyberChef</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=CyberChef&amp;diff=17223"/>
		<updated>2024-12-17T15:51:08Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Cyberchef is a tool that is used to execute various encoding, encryption, data processing and transformation tasks. It was created by the GCHQ (Government Communications Headquarters) and is also known as the &amp;quot;Cyber Swiss Army Knife&amp;quot;, because of its wide variety of operations. A link to a online version can be found in the Readme file in the official github repository (https://github.com/gchq/CyberChef)[1].&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
The whole tool can be downloaded using docker. The following command pulls the latest version of the program and starts a container. The webpage can then be seen on the localhost on port 8080 on the browser.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker run -it -p 8080:80 ghcr.io/gchq/cyberchef:latest&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, the program can be build directly. For this the repository needs to be cloned and within the folder the following commands need to be executed.&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker build --tag cyberchef --ulimit nofile=10000 .&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker run -it -p 8080:80 cyberchef&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== How to use ==&lt;br /&gt;
&lt;br /&gt;
The webpage has 4 important parts.The first one is the Operations tab. There is a list of all functions that can be executed. Double clicking on a function adds it to the second tab called recipe. Alternatively, the function can be dragged into the recipe tab This tab contains a list of all functions that will be executed. The input will go through all functions from top to bottom and the output of the function above will be the input of the function below. The third tab is for the input. Here the user can paste whatever input they want to process. The last tab is for the output. The result of the last function will be posted here.&lt;br /&gt;
&lt;br /&gt;
The tool also allows to save and load recipes.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* [1] https://github.com/gchq/CyberChef&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Basic]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=WebGoat&amp;diff=17222</id>
		<title>WebGoat</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=WebGoat&amp;diff=17222"/>
		<updated>2024-12-17T15:50:38Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary == &lt;br /&gt;
&lt;br /&gt;
This is a tutorial and info site on the OWASP&#039;s vulnerable web application WebGoat.&lt;br /&gt;
&lt;br /&gt;
== OWASP WebGoat ==&lt;br /&gt;
&lt;br /&gt;
The OWASP WebGoat project provides an insecure web application that demonstrates the most common client-side application flaws and explains and tests the vulnerabilities from the OWASP Top 10. Lessons, exercises and challenges are provided to give interested developers hands-on experience to test and better understand the material. When starting each lesson, the user is provided with content and interactive questions about the already explained material or demonstrations of the explained functionality through a dialog from different pages. The learning of the content is thus brought to the user in a playful, hands-on experience. The lessons are structured strictly according to the OWASP Top 10 and can be tested and reviewed individually.&lt;br /&gt;
&lt;br /&gt;
=== Learning in three steps ===&lt;br /&gt;
&lt;br /&gt;
1. Explanation of vulnerability&lt;br /&gt;
&lt;br /&gt;
The platform begins by providing a comprehensive explanation of what a vulnerability is, rather than immediately delving into the act of hacking. This approach ensures that users have a solid understanding of the security issue they are dealing with before attempting to exploit it.&lt;br /&gt;
&lt;br /&gt;
2. Learning by doing&lt;br /&gt;
&lt;br /&gt;
Once an individual gains a comprehensive understanding of the vulnerability, WebGoat guides them through practical assignments to apply their knowledge. These assignments are integrated into the learning process, encouraging active engagement and experimentation on the platform. The program follows a &#039;learning by doing&#039; approach. A &#039;doing&#039; approach can reinforce understanding of the mechanics of a vulnerability.&lt;br /&gt;
&lt;br /&gt;
3. Explanation of mitigation&lt;br /&gt;
&lt;br /&gt;
At the conclusion of each lesson or exercise, WebGoat explains mitigation techniques. It provides a summary of potential strategies that are crucial for developers and security practitioners. These strategies help secure applications against the specific vulnerability explored, offering practical insights that can be applied. This information improves the resilience of applications to potential attacks in real-world development work.&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
&lt;br /&gt;
There are three possible ways to install the programm: Standalone, Docker Image and cloning the repository (open source) &amp;lt;ref&amp;gt;WebGoat Github, &#039;&#039;WebGoat&#039;&#039;, 2022, accessed on: 02.01.2023, [Online]. Available: https://github.com/WebGoat/WebGoat&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
* Operating system: &lt;br /&gt;
** Windows 8 or higher&lt;br /&gt;
** Ubuntu Linux 20.04 LTS or higher&lt;br /&gt;
** macOS 10.14 or higher&lt;br /&gt;
** Or any other OS which is supported by Java 17&lt;br /&gt;
* Java 17 OR Docker Desktop &lt;br /&gt;
* Internet Browser of any type&lt;br /&gt;
* GIT&lt;br /&gt;
&lt;br /&gt;
=== Installation Instructions ===&lt;br /&gt;
&lt;br /&gt;
==== Run with Docker ====&lt;br /&gt;
&lt;br /&gt;
Need to insall Docker first, then you can install WebGoat as Docker Image.&lt;br /&gt;
&lt;br /&gt;
 sudo apt install docker.io&lt;br /&gt;
 sudo docker run -p 127.0.0.1:8080:8080 -p 127.0.0.1:9090:9090 -e TZ=Europe/Amsterdam webgoat/webgoat&lt;br /&gt;
&lt;br /&gt;
==== Standalone ====&lt;br /&gt;
&lt;br /&gt;
Download .jar file (Java Archive file) from https://github.com/WebGoat/WebGoat/releases&lt;br /&gt;
Make sure that you&#039;re downloading the latest version.&lt;br /&gt;
 &lt;br /&gt;
 java -Dfile.encoding=UTF-8 -Dwebgoat.port=8080 -Dwebwolf.port=9090 -jar webgoat-2023.8.jar&lt;br /&gt;
&lt;br /&gt;
==== Run from the sources ====&lt;br /&gt;
&lt;br /&gt;
Clone GitHub Repository (Open Source)&lt;br /&gt;
&lt;br /&gt;
 git clone git@github.com:WebGoat/WebGoat.git&lt;br /&gt;
&lt;br /&gt;
Compile the Project using Java 17&lt;br /&gt;
&lt;br /&gt;
 cd WebGoat&lt;br /&gt;
 git checkout &amp;lt;&amp;lt;branch_name&amp;gt;&amp;gt;&lt;br /&gt;
 # On Linux/Mac:&lt;br /&gt;
 ./mvnw clean install &lt;br /&gt;
&lt;br /&gt;
 # On Windows:&lt;br /&gt;
 ./mvnw.cmd clean install&lt;br /&gt;
&lt;br /&gt;
When the priject is compiled successfully we are ready to run the project. WebGoat is using Spring Boot. &lt;br /&gt;
 &lt;br /&gt;
 # On Linux/Mac:&lt;br /&gt;
 ./mvnw spring-boot:run&lt;br /&gt;
 # On Windows:&lt;br /&gt;
 ./mvnw.cmd spring-boot:run&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Access ===&lt;br /&gt;
* The landing page will be located at: http://localhost&lt;br /&gt;
* WebGoat will be located at: http://localhost:8080/WebGoat&lt;br /&gt;
* WebWolf will be located at: http://localhost:9090/WebWolf&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;lt;ul&amp;gt; &lt;br /&gt;
&amp;lt;li style=&amp;quot;display: inline-block;&amp;quot;&amp;gt; [[File:Webgoat1.png|thumb|none|500px|Web goat]] &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To gain access to the lessons and challenges, you need to register.&lt;br /&gt;
&lt;br /&gt;
== WebGoat Lessons ==&lt;br /&gt;
&lt;br /&gt;
The OWASP WebGoat Lessons are embedded in the WebGoat Tool. Here, various attack vectors are demonstrated using hands-on examples. In general, WebGoat contains&lt;br /&gt;
lessons, exercises and challenges. These lessons are divided into different categories and&lt;br /&gt;
contain several pages of information and exercises. The challenges are more demanding&lt;br /&gt;
and do not contain any hints. The current version 2023.4 contains 9 lessons:&lt;br /&gt;
&lt;br /&gt;
* (A1) Broken Access Control (Hijack a session, Insecure Direct Object References, Missing Function Level Access Control and Spoofing an Authenticate Cookie)&lt;br /&gt;
* (A2) Cryptographic Failures &lt;br /&gt;
* (A3) Injection (SQL Injections intro/advanced/mitigation, Path traversal, Cross Site Scripting)&lt;br /&gt;
* (A5) Security Misconfiguration (XXE)&lt;br /&gt;
* (A6) Vuln &amp;amp; Outdated Components (Vulnerable Components)&lt;br /&gt;
* (A7) Identity &amp;amp; Auth Failure (Authentication Bypasses, Insecure Login, JWT tokens, Password reset, Secure Passwords)&lt;br /&gt;
* (A8) Software &amp;amp; Data Integrity (Insecure Deserialization)&lt;br /&gt;
* (A9) Security Logging Failures (Logging Security)&lt;br /&gt;
* (A10) Server-side Request Forgery (Cross-Site Request Forgeries, Server-side Request Forgery)&lt;br /&gt;
&lt;br /&gt;
Each lesson contains further sub-chapters which each contain several pages. In the&lt;br /&gt;
first steps, the material is explained, and in the further steps it is explained by means&lt;br /&gt;
of exercises.&lt;br /&gt;
&lt;br /&gt;
In the future additional lessons corresponding to the following topics will be added:&lt;br /&gt;
&lt;br /&gt;
* Lesson about cryptography (In Progress)&lt;br /&gt;
* Lesson about path traversal (in progress)&lt;br /&gt;
* Session Management&lt;br /&gt;
* More password reset lessons&lt;br /&gt;
&lt;br /&gt;
== OWASP WebWolf ==&lt;br /&gt;
&lt;br /&gt;
=== Description ===&lt;br /&gt;
&lt;br /&gt;
Since the lessons of WebGoat cover very extensive concepts of penetration testing and&lt;br /&gt;
therefore build critical vulnerabilities into the local system to make lessons practically&lt;br /&gt;
implementable as well, OWASP decided to provide its own local tool called WebWolf.&lt;br /&gt;
WebWolf is automatically delivered with the installation of WebWolf. The tool acts as&lt;br /&gt;
a locally hosted attacker machine. This is to highlight more clearly which operations&lt;br /&gt;
need to be performed as the attacker and which need to be performed at the target&lt;br /&gt;
in order to successfully execute an exploit. Some lessons use WebWolf, for example,&lt;br /&gt;
to provide a file that must be loaded onto the target machine (e.g., for persistent XSS&lt;br /&gt;
attacks, which will be discussed in more detail later in the thesis) or to provide a&lt;br /&gt;
connection to the own environment (ReverseTCP). Since these services should not be&lt;br /&gt;
provided in the open and connected Internet, WebWolf was developed.&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
&lt;br /&gt;
WebWolf is an included tool that is directly in the repository (Git and DockerHub)&lt;br /&gt;
and should already be on the machine after downloading WebGoat. If the tool has&lt;br /&gt;
already been started via a Docker image, WebWolf is already running and should be&lt;br /&gt;
accessible at http://localhost:9090/WebWolf. If the repository is cloned locally in&lt;br /&gt;
standalone mode, the WebWolf Java Archive file still needs to be downloaded to start&lt;br /&gt;
it locally. This can be done with the following command. If WebWolf has been started&lt;br /&gt;
successfully, it will also be available under the above link.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 java -jar webwolf&amp;lt;&amp;lt;version&amp;gt;&amp;gt;.jar [--server.port=9090][server.address=localhost]&lt;br /&gt;
&lt;br /&gt;
=== Use ===&lt;br /&gt;
&lt;br /&gt;
WebWolf in the current version (8.2.2) provides the following functionalities:&lt;br /&gt;
&lt;br /&gt;
* File Hosting Service&lt;br /&gt;
* Landing Page for incoming requests&lt;br /&gt;
* Email Server with Client&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Documentation]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=CyberChef&amp;diff=17221</id>
		<title>CyberChef</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=CyberChef&amp;diff=17221"/>
		<updated>2024-12-17T15:49:14Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: Created page with &amp;quot;Cyberchef is a tool that is used to execute various encoding, encryption, data processing and transformation tasks. It was created by the GCHQ (Government Communications Headquarters) and is also known as the &amp;quot;Cyber Swiss Army Knife&amp;quot;, because of its wide variety of operations. A link to a online version can be found in the Readme file in the official github repository (https://github.com/gchq/CyberChef)[1].  == Installation == The whole tool can be downloaded using docke...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Cyberchef is a tool that is used to execute various encoding, encryption, data processing and transformation tasks. It was created by the GCHQ (Government Communications Headquarters) and is also known as the &amp;quot;Cyber Swiss Army Knife&amp;quot;, because of its wide variety of operations. A link to a online version can be found in the Readme file in the official github repository (https://github.com/gchq/CyberChef)[1].&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
The whole tool can be downloaded using docker. The following command pulls the latest version of the program and starts a container. The webpage can then be seen on the localhost on port 8080 on the browser.&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker run -it -p 8080:80 ghcr.io/gchq/cyberchef:latest&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, the program can be build directly. For this the repository needs to be cloned and within the folder the following commands need to be executed.&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker build --tag cyberchef --ulimit nofile=10000 .&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;&amp;lt;i&amp;gt;docker run -it -p 8080:80 cyberchef&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== How to use ==&lt;br /&gt;
&lt;br /&gt;
The webpage has 4 important parts.The first one is the Operations tab. There is a list of all functions that can be executed. Double clicking on a function adds it to the second tab called recipe. Alternatively, the function can be dragged into the recipe tab This tab contains a list of all functions that will be executed. The input will go through all functions from top to bottom and the output of the function above will be the input of the function below. The third tab is for the input. Here the user can paste whatever input they want to process. The last tab is for the output. The result of the last function will be posted here.&lt;br /&gt;
&lt;br /&gt;
The tool also allows to save and load recipes.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
* [1] https://github.com/gchq/CyberChef&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
	<entry>
		<id>https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17220</id>
		<title>SHA-3</title>
		<link rel="alternate" type="text/html" href="https://elvis.hcw.ac.at/wiki/index.php?title=SHA-3&amp;diff=17220"/>
		<updated>2024-12-17T15:37:46Z</updated>

		<summary type="html">&lt;p&gt;PSimetzberger: Created page with &amp;quot; SHA-3 is a cryptographic hash function and the newest addition to the SHA family. Guido Bertoni, Joan Daemen, Michael Peeters and Gilles Van Assche created the algorithm with the name Keccak. In 2012 Keccak won the american SHA-3 contest organized by NIST. On the 5th of August 2015 it was standardised, allowing for an alternative to SHA-2 (which is still considered save)[2].  == General information ==  === Hashing Algorithm === A hashing algorithm is a mathenmatical fun...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
SHA-3 is a cryptographic hash function and the newest addition to the SHA family. Guido Bertoni, Joan Daemen, Michael Peeters and Gilles Van Assche created the algorithm with the name Keccak. In 2012 Keccak won the american SHA-3 contest organized by NIST. On the 5th of August 2015 it was standardised, allowing for an alternative to SHA-2 (which is still considered save)[2].&lt;br /&gt;
&lt;br /&gt;
== General information ==&lt;br /&gt;
&lt;br /&gt;
=== Hashing Algorithm ===&lt;br /&gt;
A hashing algorithm is a mathenmatical function that converts an input to a fixed-size output which is often refered as hash value or digest. Hashing is a crucial part of cyber security and widely used in data integrity, verification, cryptography and more.&lt;br /&gt;
&lt;br /&gt;
Hashing algorithms are deterministic, meaning that the same input will always result in the same output. Another characteristic is that a small change in the input leads to significant changes in the hash. Further characteristics can be found under Hashing goals.&lt;br /&gt;
&lt;br /&gt;
=== Hashing goals ===&lt;br /&gt;
&lt;br /&gt;
SHA-3 like every other hashing algorithm pursues the same 5 goals.&lt;br /&gt;
* Compression: The algorithm must produce the same fixed length output regardless of the length of the input&lt;br /&gt;
* Efficient: It must be fast to calculate the function as it will be calculated a lot.&lt;br /&gt;
* Pre-image resistance: Knowing the algorithm and output it should be infeasable to calculate the input&lt;br /&gt;
* 2nd Pre-image resistance: Given an input and output of the algorithm, it should be infeasable to calculate a second input resulting in the same output&lt;br /&gt;
* Collision resistance: Finding 2 inputs giving the same output should be implausible&lt;br /&gt;
&lt;br /&gt;
=== Hashing Process ===&lt;br /&gt;
Algorithms follow a simple 3 step process to calculate the hash.&lt;br /&gt;
* Pre-processing: The goal is to get the input in a way the algorithm can handle. This includes processes like padding or splitting the input into blocks&lt;br /&gt;
* Initialization: Initial variables and constants are set&lt;br /&gt;
* Execution: The actual hashing algorithm is executed&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Calculation ==&lt;br /&gt;
&lt;br /&gt;
=== Sponge construction ===&lt;br /&gt;
The Keccak algorithm is a so called sponge construction. It is called that, because it &amp;quot;absorbs&amp;quot; the input and then &amp;quot;squeezes&amp;quot; out the output.&lt;br /&gt;
&lt;br /&gt;
The algorithm uses a 1600-bit array called state which it uses for the caluclations and which will contain the output afterwards. It is divided into 2 parts. The first one is called rate (r) and it will absorb the input. The second part is called capacity (c) and its only function is to make the algorithm more secure.&lt;br /&gt;
&lt;br /&gt;
After the state is initialized, the input message is divided into parts that are as long as the rate. If needed, the last input block will be padded by adding a 1 and then fill it up with 0 to the needed length.&lt;br /&gt;
&lt;br /&gt;
The first input block is now XORed with the state. Afterwards the Keccak algorithm will be used on the state. Then the next block is XORed and the whole process repeats until all chunks are absorbed into the algorithm&lt;br /&gt;
&lt;br /&gt;
Lastly the output is &amp;quot;squeezed&amp;quot; out. The first r bits of the state are taken as the hash value. If the output length is larger than r, the Keccak algorithm will be used again on the state and the next r bits are extraced. This process can repeat until the output length is reached. [1]&lt;br /&gt;
&lt;br /&gt;
=== Keccak-p permutation ===&lt;br /&gt;
This is the core component of the SHA-3 algorithm. It contains 5 different operations which are executed in order on the state array. To ensure the hashing goals, multiple rounds of the permutation are done in one call of the algorithm. The default for SHA-3 are 24 rounds, meaning that a single call will execute the Keccak-p permutation 24 times before it returns the state. Because of this, the number of rounds is usually an additional input parameter.&lt;br /&gt;
The state is usually divided into a 5x5 matrix with 64 bits in each position.&lt;br /&gt;
&lt;br /&gt;
* Step 1, Theta: XOR each bit with a representative value derived from neighboring columns&lt;br /&gt;
* Step 2, Rho: Rotates each lane&#039;s bits by a specific offset based on its position&lt;br /&gt;
* Step 3, Pi: Rearranges the positions of the lanes&lt;br /&gt;
* Step 4, Chi: Applies a non-linear transformation to each row using bitwise operations&lt;br /&gt;
* Step 5, Iota: XOR with round-specific constants to prevent symmetry&lt;br /&gt;
[1]&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* [1] https://csrc.nist.gov/pubs/fips/202/final&lt;br /&gt;
&lt;br /&gt;
* [2] https://csrc.nist.gov/projects/hash-functions&lt;br /&gt;
&lt;br /&gt;
[[Category:Basic]]&lt;/div&gt;</summary>
		<author><name>PSimetzberger</name></author>
	</entry>
</feed>