Kind of reverse engineering Post: 302773877

Sponsored Content

Operating Systems Linux Kind of reverse engineering Post 302773877 by Smiling Dragon on Friday 1st of March 2013 12:43:26 AM

03-01-2013

Registered User

I'd say that you would want to trace the program. On linux, the strace and ptrace commands would be the tools of choice I'd say. I typically use strace with the '-f' flag to instruct it to follow any child processes it starts.

You'll be able to see any raw writes and reads to the serial device.

To get deeper and actually capture the exact data flow, you'd likely need to create a named pipe, connect that to a script that just dumps all data it seems and then passes it on to the serial port, then point the code you are reverse engineering at your new dummy "serial port" device.

You might also be able to do something crafty with a windows PC and two serial ports. Connect one to the linux host, the other to the STB. Then write a short program to capture all serial traffic on either port, and send it to the other - ie a packet sniffer for serial traffic.
(I say windows just because it sounds like you are more comfortable coding on that)

Smiling Dragon

View Public Profile for Smiling Dragon

Find all posts by Smiling Dragon

4 More Discussions You Might Find Interesting

1. Programming

Performance engineering concepts

Hello, I would like get idea about performance enginering from basic to advanced level. Do anyone know a place where i can find some videos related to performance engineering ?

2. Shell Programming and Scripting

Sampling and Binning- Engineering problem

Hi everyone! Can you please help me with some shell scripting? I have an input file input.txt It has 3 columns (Time, Event, Value) Time event Value 03:38:22 A 57 03:38:23 A 56 03:38:24 B 24 03:38:25 C 51 03:38:26 B 7 03:38:26 ...

3. Shell Programming and Scripting

awk, shell script reverse engineering app generator - project

Hi, this is fantastic forum for shell programming and scripting, so please let me to introduce you with my very old concept to have web form/s with radio, select, input fields and have an application generating valid, syntax error free scripting code. The same or alike questions are asked...

4. Solaris

Legacy Ultra60 with Solaris 5.7 SCSI device reverse engineering

I'm looking for help with a legacy system. I have some obsolete equipment connected to an Ultra 60 running Solaris 5.7 with the binary for a 32 bit driver. The driver is rejected by newer versions of solaris, which run 64 bit kernels. I hope to reverse engineer the driver so that I can...

LEARN ABOUT DEBIAN

cyclades-serial-client

cyclades-serial-client(8)												 cyclades-serial-client(8)

NAME

       cyclades-serial-client Serial Port Interface for Cyclades Terminal Servers

SYNOPSIS

       cyclades-serial-client (start | stop | restart | status) [devname]

DESCRIPTION

       For  each  physical  port listed in cyclades-devices file, cyclades-serial-client controls the status of the corresponding cyclades-ser-cli
       interface.

OPTIONS

       cyclades-serial-client must be invoked with one of the (start, stop, restart or status), and optionaly with a argument associated to a spe-
       cific device.  In this case, the action spedified as the option will be performed only for this device.

       If this argument was not supplied, the action will be performed for all devices listed in cyclades-devices file. The mandatory options are:

       start  -  Starts the cyclades-ser-cli program, using parameters supplied in the cyclades-devices  file. If this program is already running,
	      a message will be displayed, and no additional copy will be started.

       stop   - Stops the cyclades-ser-cli program(s), by issuing a SIGTERM signal.

       restart
	      - Simulates a hangup to cyclades-ser-cli program(s), by issuing a SIGUSR1 signal.

       status - Checks the status of cyclades-ser-cli programs(s).

EXAMPLES

       Assuming the the following cyclades-devices file configuration:

       /dev/ctty01:pr3k:1:rtelnet: /dev/ctty02:pr3k:2:socket:

       1 . Start all devices: cyclades-serial-client start Messages: "Starting /dev/ctty01  <==>  pr3k:1  interface"  "Starting  /dev/ctty02  <==>
       pr3k:2 interface"

       2 . Try to start them again: cyclades-serial-client start Messages: "cyclades-serial-client : /dev/ctty01 already active" "cyclades-serial-
       client : /dev/ctty02 already active"

       3 . Stop only /dev/ctty01 device: cyclades-serial-client stop /dev/ctty01 Messages: "Stopping /dev/ctty01 <==> pr3k:2 interface"

       4 . Checking status: cyclades-serial-client status Messages: "/dev/ctty01 (rtelnet at pr3k:1) is inactive" "/dev/ctty02 ( socket at pr3k:2)
       active, pid 2983"

       5  .  Start  a  non-valid  device  cyclades-serial-client start /dev/xtty01 Messages: "cyclades-serial-client : device /dev/xtty01 does not
       exist"

SEE ALSO

       cyclades-ser-cli(1), cyclades-devices(5)

															 cyclades-serial-client(8)