Studio:Transferring Files - Revision history

Timd: Text replace - 'Category: Miscellaneous' to 'Category:Studio:Miscellaneous'

2009-08-21T15:36:03Z

Text replace - 'Category: Miscellaneous' to 'Category:Studio:Miscellaneous'

← Older revision		Revision as of 15:36, 21 August 2009
Line 416:		Line 416:
	</source>		</source>

	[[Category: Miscellaneous]]		[[Category:Studio:Miscellaneous]]

Timd: Transferring Files moved to Studio:Transferring Files

2009-08-18T23:33:16Z

Transferring Files moved to Studio:Transferring Files

← Older revision	Revision as of 23:33, 18 August 2009
(No difference)

Mikee: /* netcat */

2008-12-02T22:26:57Z

netcat

← Older revision		Revision as of 22:26, 2 December 2008
Line 7:		Line 7:
	==netcat==		==netcat==

	While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the ~~LinuxTestAgent framework~~ utilities (''%STRIDE_DIR%\SDK\Linux\lib\perl\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.		While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the Linux SDK utilities (''%STRIDE_DIR%\SDK\Linux\lib\perl\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.

	==custom device tools==		==custom device tools==

Mikee: /* netcat */

2008-12-02T22:23:46Z

netcat

← Older revision		Revision as of 22:23, 2 December 2008
Line 7:		Line 7:
	==netcat==		==netcat==

	While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\~~frameworks~~\~~LinuxTestAgent~~\~~scripts~~\~~utility~~\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.		While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\SDK\Linux\lib\perl\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.

	==custom device tools==		==custom device tools==

Mikee at 17:37, 8 October 2008

2008-10-08T17:37:23Z

← Older revision		Revision as of 17:37, 8 October 2008
Line 8:		Line 8:

	While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\frameworks\LinuxTestAgent\scripts\utility\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.		While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\frameworks\LinuxTestAgent\scripts\utility\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.

			==custom device tools==

			If your device runs a proprietary OS and has a filesystem, it is likely that someone has developed custom tools for transferring data and/or files to the device. You should consult with your system team to determine what options are available for these non-standard systems. If it turns out that communication channels are available on the device for file transfer, it is likely that you could craft perl code to automate the communcation. For instance, perl has several libraries available for doing [http://search.cpan.org/~bbirth/Win32-SerialPort-0.19/lib/Win32/SerialPort.pm serial communication]. Other data interfaces are also probably available - we recommend searching for available packages at [http://search.cpan.org CPAN] to see if something suits your needs.

	==STRIDE Runtime Payloads==		==STRIDE Runtime Payloads==
Line 22:		Line 26:
	#include <sr.h>		#include <sr.h>

			/* this is the number of bytes we attempt to read
			* and send in one message. You may want to tune
			* this parameter for efficiency with your stdio
			* implementation and STRIDE runtime. In general,
			* larger chunks will result in fewer broadcast
			* messages which should improve transfer time
			*/
	#define FILETRANSFER_DATA_CHUNK 1024*8		#define FILETRANSFER_DATA_CHUNK 1024*8
	#define MAX_FILE_PATH 255		#define MAX_FILE_PATH 255

Mikee at 17:22, 8 October 2008

2008-10-08T17:22:53Z

← Older revision		Revision as of 17:22, 8 October 2008
Line 278:		Line 278:
	use MIME::Base64;		use MIME::Base64;
	use IO::File;		use IO::File;
	use Time::HiRes qw(gettimeofday tv_interval);		use Time::HiRes qw(gettimeofday tv_interval sleep);

	use vars qw($ascript $messages $studio);		use vars qw($ascript $messages $studio);
Line 310:		Line 310:
	$transfer->ParameterList->{file_path} = $remote;		$transfer->ParameterList->{file_path} = $remote;
	$transfer->CallNonBlocking();		$transfer->CallNonBlocking();
			sleep(0.5); #allow the transfer_file function to startup and subscribe

	my $totalBytes = 0;		my $totalBytes = 0;
Line 331:		Line 332:
	}		}
	else {		else {
	~~$studio->Output->PrintMessage(~~"~~WARN: never~~ received READY message");		die "Never received READY message";
	}		}
	}		}

Mikee: /* Source (implementation) */

2008-10-07T00:09:17Z

Source (implementation)

← Older revision		Revision as of 00:09, 7 October 2008
Line 134:		Line 134:
	palWait(dwNID, &dwEvents);		palWait(dwNID, &dwEvents);
	if (dwEvents & palSTOP_EVENT) {		if (dwEvents & palSTOP_EVENT) {
			/* repost the stop event */
			palNotify(dwNID, palSTOP_EVENT);
	goto transfer_done;		goto transfer_done;
	}		}
Line 191:		Line 193:
	palWait(dwNID, &dwEvents);		palWait(dwNID, &dwEvents);
	if (dwEvents & palSTOP_EVENT) {		if (dwEvents & palSTOP_EVENT) {
			/* repost the stop event */
			palNotify(dwNID, palSTOP_EVENT);
	break;		break;
	}		}

Mikee: /* Host Implementation */

2008-10-06T23:29:47Z

Host Implementation

← Older revision		Revision as of 23:29, 6 October 2008
Line 327:		Line 327:
	}		}
	else {		else {
	$studio->Output->PrintMessage("WARN: never ~~receive~~ READY message");		$studio->Output->PrintMessage("WARN: never received READY message");
	}		}
	}		}
Line 387:		Line 387:
	In order to execute a transfer, you could simply call this function like this:		In order to execute a transfer, you could simply call this function like this:
	<source lang="perl">		<source lang="perl">
	# to fetch from the ~~targert~~		# to fetch from the target device
	TransferFile(		TransferFile(
	Send => 0,		Send => 0,
Line 393:		Line 393:
	HostFilePath => 'c:/file_from_target');		HostFilePath => 'c:/file_from_target');

	# to send to the target		# to send to the target device
	TransferFile(		TransferFile(
	Send => 1,		Send => 1,

Mikee: /* netcat */

2008-10-06T23:27:22Z

netcat

← Older revision		Revision as of 23:27, 6 October 2008
Line 7:		Line 7:
	==netcat==		==netcat==

	While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\frameworks\LinuxTestAgent\scripts\utility\TargetUtilities.pm''). This module ~~provide~~ '''RemoteGet''' and '''RemotePut''' methods that use telnet to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own ~~file transfer~~ solution.		While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\frameworks\LinuxTestAgent\scripts\utility\TargetUtilities.pm''). This module provides '''RemoteGet''' and '''RemotePut''' methods that use [http://en.wikipedia.org/wiki/Telnet telnet] to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own netcat-based solution.

	==STRIDE Runtime Payloads==		==STRIDE Runtime Payloads==

Mikee: /* netcat */

2008-10-06T23:26:07Z

netcat

← Older revision		Revision as of 23:26, 6 October 2008
Line 7:		Line 7:
	==netcat==		==netcat==

	While ~~it's not uncommon for~~ FTP and SCP ~~to be~~ omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\frameworks\LinuxTestAgent\scripts\utility\TargetUtilities.pm''). This module provide '''RemoteGet''' and '''RemotePut''' methods that use telnet to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own file transfer solution.		While FTP and SCP are often omitted from embedded linux builds, it's not uncommon to have [http://en.wikipedia.org/wiki/Netcat netcat] available (particularly if you are using [http://www.busybox.net/ BusyBox] for your tools implementation). Netcat provides simple sockets based data transfer capability. It is possible to craft perl code that can transfer files using basic sockets communication and netcat on the target side. STRIDE provides one such implementation in the LinuxTestAgent framework utilities (''%STRIDE_DIR%\frameworks\LinuxTestAgent\scripts\utility\TargetUtilities.pm''). This module provide '''RemoteGet''' and '''RemotePut''' methods that use telnet to establish a remote session with the device and netcat to transfer files. If you have these services available, you can likely use this module without modification. If you require some other form of login or remote process invocation, you might find it helpful to refer to this module when implementing your own file transfer solution.

	==STRIDE Runtime Payloads==		==STRIDE Runtime Payloads==