USB Armory - Revision history

VSpudil: /* Initial Operation of INTERLOCK */

2024-12-17T20:38:41Z

Initial Operation of INTERLOCK

← Older revision		Revision as of 20:38, 17 December 2024
Line 220:		Line 220:


	[[File:Screenshot_INTERLOCK_Menu_GUI.png\|thumb\|center\|500px\|Screenshot INTERLOCK ~~Menu~~ GUI]]		[[File:Screenshot_INTERLOCK_Menu_GUI.png\|thumb\|center\|500px\|Screenshot INTERLOCK GUI]]

VSpudil: /* Initial Operation of INTERLOCK */

2024-12-17T20:28:52Z

Initial Operation of INTERLOCK

← Older revision		Revision as of 20:28, 17 December 2024
Line 218:		Line 218:
	=== Initial Operation of INTERLOCK ===		=== Initial Operation of INTERLOCK ===
	Once the USB Armory with the INTERLOCK application installed is connected to a computer's USB interface, it behaves exactly as described in section [https://wiki.elvis.science/index.php?title=USB_Armory#Initial_Operation_of_the_Operating_System Initial Operation of the Operating System]. By default, the USB Armory immediately starts booting. After the system of the INTERLOCK application on the USB Armory has booted, it uses an Ethernet-over-USB emulation (CDC Ethernet) to communicate with the computer to which it is connected. The USB Armory assigns itself the IP address 10.0.0.1. The web interface of the INTERLOCK application can now be accessed using a web browser at the link https://10.0.0.1, with the default username <b>armory</b> and the default password <b>usbarmory</b>.		Once the USB Armory with the INTERLOCK application installed is connected to a computer's USB interface, it behaves exactly as described in section [https://wiki.elvis.science/index.php?title=USB_Armory#Initial_Operation_of_the_Operating_System Initial Operation of the Operating System]. By default, the USB Armory immediately starts booting. After the system of the INTERLOCK application on the USB Armory has booted, it uses an Ethernet-over-USB emulation (CDC Ethernet) to communicate with the computer to which it is connected. The USB Armory assigns itself the IP address 10.0.0.1. The web interface of the INTERLOCK application can now be accessed using a web browser at the link https://10.0.0.1, with the default username <b>armory</b> and the default password <b>usbarmory</b>.


	[[File:Screenshot_INTERLOCK_Menu_GUI.png\|thumb\|center\|500px\|Screenshot INTERLOCK Menu GUI]]		[[File:Screenshot_INTERLOCK_Menu_GUI.png\|thumb\|center\|500px\|Screenshot INTERLOCK Menu GUI]]


	<b>NOTE:</b> A DHCP server runs by default. Alternatively, the IP address of the host interface can be statically set to 10.0.0.2/24.		<b>NOTE:</b> A DHCP server runs by default. Alternatively, the IP address of the host interface can be statically set to 10.0.0.2/24.

VSpudil: /* Initial Operation of INTERLOCK */

2024-12-17T20:28:43Z

Initial Operation of INTERLOCK

← Older revision		Revision as of 20:28, 17 December 2024
Line 218:		Line 218:
	=== Initial Operation of INTERLOCK ===		=== Initial Operation of INTERLOCK ===
	Once the USB Armory with the INTERLOCK application installed is connected to a computer's USB interface, it behaves exactly as described in section [https://wiki.elvis.science/index.php?title=USB_Armory#Initial_Operation_of_the_Operating_System Initial Operation of the Operating System]. By default, the USB Armory immediately starts booting. After the system of the INTERLOCK application on the USB Armory has booted, it uses an Ethernet-over-USB emulation (CDC Ethernet) to communicate with the computer to which it is connected. The USB Armory assigns itself the IP address 10.0.0.1. The web interface of the INTERLOCK application can now be accessed using a web browser at the link https://10.0.0.1, with the default username <b>armory</b> and the default password <b>usbarmory</b>.		Once the USB Armory with the INTERLOCK application installed is connected to a computer's USB interface, it behaves exactly as described in section [https://wiki.elvis.science/index.php?title=USB_Armory#Initial_Operation_of_the_Operating_System Initial Operation of the Operating System]. By default, the USB Armory immediately starts booting. After the system of the INTERLOCK application on the USB Armory has booted, it uses an Ethernet-over-USB emulation (CDC Ethernet) to communicate with the computer to which it is connected. The USB Armory assigns itself the IP address 10.0.0.1. The web interface of the INTERLOCK application can now be accessed using a web browser at the link https://10.0.0.1, with the default username <b>armory</b> and the default password <b>usbarmory</b>.

			[[File:Screenshot_INTERLOCK_Menu_GUI.png\|thumb\|center\|500px\|Screenshot INTERLOCK Menu GUI]]

	<b>NOTE:</b> A DHCP server runs by default. Alternatively, the IP address of the host interface can be statically set to 10.0.0.2/24.		<b>NOTE:</b> A DHCP server runs by default. Alternatively, the IP address of the host interface can be statically set to 10.0.0.2/24.

VSpudil: /* Initial Operation of the Operating System */

2024-12-17T20:15:36Z

Initial Operation of the Operating System

← Older revision		Revision as of 20:15, 17 December 2024
Line 117:		Line 117:
	The connection can be established via SSH to 10.0.0.1, using the default username <b>usbarmory</b> and the password <b>usbarmory</b>.		The connection can be established via SSH to 10.0.0.1, using the default username <b>usbarmory</b> and the password <b>usbarmory</b>.


	<b>NOTE:</b> A DHCP server runs by default. Alternatively, the IP address of the host interface can be statically set to 10.0.0.2/24.<ref>USB armory - Debian base image release 20240702, https://github.com/usbarmory/usbarmory-debian-base_image/releases/tag/20240702</ref>		<b>NOTE:</b> A DHCP server runs by default. Alternatively, the IP address of the host interface can be statically set to 10.0.0.2/24.<ref>USB armory - Debian base image release 20240702, https://github.com/usbarmory/usbarmory-debian-base_image/releases/tag/20240702</ref>


	It is known that the USB Armory is not automatically recognized as a network adapter on certain Microsoft Windows installations and does not appear under <code>Control Panel\Network and Internet\Network Connections</code>. This is most likely caused by an issue with the RNDIS driver, which the USB Armory uses to establish a network connection over USB.		It is known that the USB Armory is not automatically recognized as a network adapter on certain Microsoft Windows installations and does not appear under <code>Control Panel\Network and Internet\Network Connections</code>. This is most likely caused by an issue with the RNDIS driver, which the USB Armory uses to establish a network connection over USB.

VSpudil: /* INTERLOCK */

2024-12-17T20:05:25Z

INTERLOCK

← Older revision		Revision as of 20:05, 17 December 2024
Line 200:		Line 200:
	== INTERLOCK ==		== INTERLOCK ==
	The INTERLOCK application is an encryption frontend specifically developed for use with the USB Armory Mk I and MK II, but it can also be used on other devices. The main interface consists of a web-based file manager that runs on an encrypted partition and is hosted by a JSON application server (e.g., on the USB Armory). Through this file manager, files can be uploaded to or downloaded from the partition encrypted using Linux Unified Key Setup (LUKS). Additionally, it supports symmetric and asymmetric cryptographic operations on individual files.<ref>INTERLOCK, https://github.com/usbarmory/interlock</ref>		The INTERLOCK application is an encryption frontend specifically developed for use with the USB Armory Mk I and MK II, but it can also be used on other devices. The main interface consists of a web-based file manager that runs on an encrypted partition and is hosted by a JSON application server (e.g., on the USB Armory). Through this file manager, files can be uploaded to or downloaded from the partition encrypted using Linux Unified Key Setup (LUKS). Additionally, it supports symmetric and asymmetric cryptographic operations on individual files.<ref>INTERLOCK, https://github.com/usbarmory/interlock</ref>


	=== Downloading INTERLOCK ===		=== Downloading INTERLOCK ===

VSpudil: /* Interlock */

2024-12-17T20:04:52Z

Interlock

@@ Line 198: / Line 198: @@
     .) python2 test_press.py
-== Interlock ==
+== INTERLOCK ==
 == Alternatives ==

VSpudil: /* Initial Operation of the Operating System */

2024-12-17T20:02:16Z

Initial Operation of the Operating System

← Older revision		Revision as of 20:02, 17 December 2024
Line 124:		Line 124:

	A possible solution to this problem is to use a virtual machine with USB passthrough and Linux as the operating system, as Linux natively provides the required usbX driver. Another possible solution is to follow the current troubleshooting suggestions provided by the manufacturer, which mainly focus on installing alternative drivers or enabling the use of already installed alternative drivers.<ref>Host communication, https://github.com/usbarmory/usbarmory/wiki/Host-communication</ref>		A possible solution to this problem is to use a virtual machine with USB passthrough and Linux as the operating system, as Linux natively provides the required usbX driver. Another possible solution is to follow the current troubleshooting suggestions provided by the manufacturer, which mainly focus on installing alternative drivers or enabling the use of already installed alternative drivers.<ref>Host communication, https://github.com/usbarmory/usbarmory/wiki/Host-communication</ref>
	You can find current troubleshooting suggestions from the manufacturer under the section "Setup & Connection Sharing: Windows 7, 8, 10" at the Link https://github.com/usbarmory/usbarmory/wiki/Host-communication.		You can find current troubleshooting suggestions from the manufacturer under the section "Setup & Connection Sharing: Windows 7, 8, 10" at the Link https://github.com/usbarmory/usbarmory/wiki/Host-communication#setup--connection-sharing-windows-7-8-10.

VSpudil at 19:05, 17 December 2024

2024-12-17T19:05:02Z

← Older revision		Revision as of 19:05, 17 December 2024
Line 197:		Line 197:
	7. Simulate clicking the button:		7. Simulate clicking the button:
	.) python2 test_press.py		.) python2 test_press.py

			== Interlock ==

	== Alternatives ==		== Alternatives ==

VSpudil: /* Getting Started */

2024-12-17T18:51:41Z

Getting Started

← Older revision		Revision as of 18:51, 17 December 2024
Line 85:		Line 85:

	=== Downloading an Operating System ===		=== Downloading an Operating System ===
	To obtain a valid operating system image, there are essentially two options for the USB Armory. A precompiled operating system binary provided by the manufacturer can be downloaded, or the manufacturer's instructions can be followed to manually create and compile an Linux Debian based operating system image according to individual requirements. <ref>Preparing a bootable image, https://github.com/usbarmory/usbarmory/wiki/Preparing-a-bootable-image</ref>		To obtain a valid operating system image, there are essentially two options for the USB Armory. A precompiled operating system binary provided by the manufacturer can be downloaded, or the manufacturer's instructions can be followed to manually create and compile an Linux Debian based operating system image according to individual requirements.<ref>Preparing a bootable image, https://github.com/usbarmory/usbarmory/wiki/Preparing-a-bootable-image</ref>

	The official operating system for the USB Armory is Debian Linux (bullseye). However, images of other Linux distributions as well as an image of the SkiffOS operating system for the USB Armory Mk II are also offered by the manufacturer. The list of images available from the manufacturer as of October 2024 is as follows: <ref>Available images, https://github.com/usbarmory/usbarmory/wiki/Available-images</ref>:		The official operating system for the USB Armory is Debian Linux (bullseye). However, images of other Linux distributions as well as an image of the SkiffOS operating system for the USB Armory Mk II are also offered by the manufacturer. The list of images available from the manufacturer as of October 2024 is as follows:<ref>Available images, https://github.com/usbarmory/usbarmory/wiki/Available-images</ref>

VSpudil: /* Getting Started */

2024-12-17T18:44:58Z

Getting Started

← Older revision		Revision as of 18:44, 17 December 2024
Line 83:		Line 83:
	== Getting Started ==		== Getting Started ==
	The USB Armory requires a valid operating system to boot either from the external MicroSD card or the internal eMMC (USB Armory Mk II). The following describes the installation on a MicroSD card:		The USB Armory requires a valid operating system to boot either from the external MicroSD card or the internal eMMC (USB Armory Mk II). The following describes the installation on a MicroSD card:


	=== Downloading an Operating System ===		=== Downloading an Operating System ===
Line 95:		Line 94:

	You can find the following Pre-Image files at this link: https://github.com/usbarmory/usbarmory/wiki/Available-images		You can find the following Pre-Image files at this link: https://github.com/usbarmory/usbarmory/wiki/Available-images


	=== Installation of the Operating System ===		=== Installation of the Operating System ===