Login or Register to Ask a Question and Join Our Community


Shell Programming and Scripting

Logging/Reading Interprocess Communications

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Logging/Reading Interprocess Communications
# 1  
Old 04-05-2010
Logging/Reading Interprocess Communications
Greetings,

I'm posting this in the shell scripting forum because I'm hoping this can be done in BASH or PERL. If not, I'm still open to suggestions of other ways to do it:

I've got an iPhone app that's sending some encrypted (SSL) traffic to a server and I'd like to be able to read the traffic. If I understand correctly, the app must send it's request through "/usr/libexec/securityd". I know the process isn't called until the app runs.

Does anybody know of a way I can read/log the requests going to the "/usr/libexec/securityd" process? Perhaps I can rename the process, intercept the requests, log them, and forward them on the real process? I'm not sure if that's feasible or not but it's a thought.

Any other ideas are welcomed as well! Thanks!
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Linux

Syslog not logging successful logging while unlocking server's console

When unlocking a Linux server's console there's no event indicating successful logging Is there a way I can fix this ? I have the following in my rsyslog.conf auth.info /var/log/secure authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies

2. UNIX for Dummies Questions & Answers

In UNIX which following type of file is used for network communications

a) FIFO B) SOCKET C) DIRECTORY D) BLOCK PLEASE SUGGEST ME THE ANSWER Do not post classroom or homework problems in the main forums. Homework and coursework questions can only be posted in this forum under special homework rules. Please review the rules, which you agreed to when you... (0 Replies)
Discussion started by: raghugowda
0 Replies

3. Shell Programming and Scripting

perl and communications

Any idea on how to set up a perl script on the client end to listen and respond to commands on a set port? Ive tried this before in the past and thinking about trying it again. Just looking for a starting point. (2 Replies)
Discussion started by: adelsin
2 Replies

4. UNIX for Dummies Questions & Answers

Interprocess Communication

Hiya Everybody just joined, Not sure if this is the right section:o I require abit of an assistance with IPC! I know there are different types of IPC porcesses like signals, semaphores, mutexes, shared memory, message queues, pipes and sockets. Now say a system has a number of... (4 Replies)
Discussion started by: G.I.Joe
4 Replies

5. UNIX for Advanced & Expert Users

linux communications modes

what r the ways in which a linux application communicate with an external system like linux or windows? (1 Reply)
Discussion started by: shil
1 Replies

6. UNIX for Advanced & Expert Users

Interprocess communication status

hello gurus, I was wondering if someone would help me shed more light on this command. What I know so far is ipcs - stands for inter-process communication status and it reports on the following types of system resources. 1) Message queues 2) Shared memory and 3) Semaphores Please explain... (4 Replies)
Discussion started by: jerardfjay
4 Replies

7. UNIX for Advanced & Expert Users

Pipe, interprocess communication

Earlier I posted a question regarding this issue. I managed to go a step further. Anyway, this is another similar question Write a programme that creates a ring of three processes connected by pipes. The first process should prompt the user for a string and then send it to the second process .... (2 Replies)
Discussion started by: scmay
2 Replies

8. UNIX for Advanced & Expert Users

Interprocess communication using pipes and fork

I'm very worried. I have an assignment that is due in 3 weeks, and also tute exercises which I can't seem to understand and work out. Okay, the question: The parent process will convert the command arguments into integer values using atoi() and store them into an integer array which you will... (2 Replies)
Discussion started by: scmay
2 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

checkbashisms

CHECKBASHISMS(1)					      General Commands Manual						  CHECKBASHISMS(1)

NAME

       checkbashisms - check for bashisms in /bin/sh scripts

SYNOPSIS

       checkbashisms script ...
       checkbashisms --help|--version

DESCRIPTION

       checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
       of bashisms.  It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.

       Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported  by  POSIX";
       this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.

       In  cases  where  POSIX	and  Debian  Policy  disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
       options for stricter checking.

OPTIONS

       --help, -h
	      Show a summary of options.

       --newline, -n
	      Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)

       --posix, -p
	      Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).

       --force, -f
	      Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
	      to be a shell wrapper).

       --extra, -x
	      Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
	      tive which may be ignored.  For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.

       --version, -v
	      Show version and copyright information.

EXIT VALUES

       The exit value will be 0 if no possible bashisms or other problems were detected.  Otherwise it will be the sum of the following error val-
       ues:

       1      A possible bashism was detected.

       2      A file was skipped for some reason, for example, because it was unreadable or not found.	The warning message will give details.

SEE ALSO

       lintian(1).

AUTHOR

       checkbashisms  was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
       Julian Gilbey <jdg@debian.org>.

DEBIAN
								 Debian Utilities						  CHECKBASHISMS(1)