<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/pepe2k/scripts/sercomm-crypto.py, branch v21.02.1</title>
<subtitle>Staging tree of Piotr Dymacz</subtitle>
<id>https://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.1</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/pepe2k/atom?h=v21.02.1'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/'/>
<updated>2020-06-02T06:37:54Z</updated>
<entry>
<title>scripts: support Sercomm crypto</title>
<updated>2020-06-02T06:37:54Z</updated>
<author>
<name>Álvaro Fernández Rojas</name>
</author>
<published>2020-06-02T06:37:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/pepe2k/commit/?id=7f1250a7fea716a13c1678a14dbc417ff57e461f'/>
<id>urn:sha1:7f1250a7fea716a13c1678a14dbc417ff57e461f</id>
<content type='text'>
Sercomm firmwares are encrypted with AES 256 CBC.
The key is generated with a custom algorithm from the firmware tag:
	char key[32];
	char version[32];
	char iv[32];
	char random[32];
	char size[32];
Key must be generated with Sercomm's algorithm. However, the rest of the
header can be empty. IV and random are set to 0 on purpose.

Signed-off-by: Álvaro Fernández Rojas &lt;noltari@gmail.com&gt;
</content>
</entry>
</feed>
