Sponsored Content
Top Forums Shell Programming and Scripting When comparing binary files, show human readable result? Post 303043371 by RudiC on Sunday 26th of January 2020 02:34:01 PM
Old 01-26-2020
How about
Code:
cmp -bl file[12] | awk '{LSTR = LSTR $3; RSTR = RSTR $5} END {print "left: ", LSTR; print "right:", RSTR}'
left:  69360bac2b3b7af4a4a67f6962
right: e1ccb4ce590a49a5905c05dc86

Unfortunately, this does not display the hyphens as they are identical in both files.


EDIT: alternatively, try

Code:
diff <(strings file1) <(strings file2)
12c12
< *69a3604b-ac2b-43b7-af84-0a4a67fc6962
---
> *e1accb44-ce59-40a4-9a85-0905c05cdc86

this might suffer if UTF-8 chars greater than 127 are close / around the strings of interest...


EDIT: or


Code:
cmp -bl file[12] | awk 'NR == 1 {OUT = sprintf ("xxd -pc1 -s%d ", X = $1 - 1)} END {OUT = OUT sprintf ("-l%d file", $1 - X); print OUT "1"; print "printf \"0A\n\""; print OUT "2"; print "printf \"0A\n\""}' | sh | xxd -p -r
69a3604b-ac2b-43b7-af84-0a4a67fc6962
e1accb44-ce59-40a4-9a85-0905c05cdc86


Last edited by RudiC; 01-26-2020 at 04:03 PM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

formatting output in human readable numbers

Hi, The following command provides the usage in 1024-byte blocks du -ks * | sort -n | echo "$1" ... 1588820 user10 2463140 user11 2464096 user12 5808484 user13 6387400 user14 ..... I am trying to produce an output of first coulmn by multiplying by 1024 so that the output should... (11 Replies)
Discussion started by: ghazi
11 Replies

2. Shell Programming and Scripting

script to convert epoch into human-readable

This is what I have to start out with more file 1208217600 1208131200 1193806800 I want to convert the epoch column into a human-readable format. My file has hundreds of these epoch times that I want to loop through and convert. (The epoch time is really the last column of the line) ... (3 Replies)
Discussion started by: snoman1
3 Replies

3. UNIX for Dummies Questions & Answers

How to make user's qutoa in human readable format?

$ quota Disk quotas for user cqlouis (uid 1254): Filesystem blocks quota limit grace files quota limit grace /dev/sdb1 64 300000 320000 8 0 0 $ I want to make the output of command quota in human readable format? How to? As we... (2 Replies)
Discussion started by: cqlouis
2 Replies

4. Shell Programming and Scripting

Human readable sizes in Solaris bdf

hay every body i need script like bdf -h in hp-ux there is no option like solaris df -h it is only bdf -k so i need the output with GBytes (8 Replies)
Discussion started by: maxim42
8 Replies

5. Shell Programming and Scripting

Convert epoch to human readable date & time format

Hello I have log file from solaris system which has date field converted by Java application using System.currentTimeMillis() function, example is 1280943608380 which equivalent to GMT: Wed, 04 Aug 2010 17:40:08 GMT. Now I need a function in shell script which will convert 1280943608380... (3 Replies)
Discussion started by: Yaminib
3 Replies

6. UNIX for Dummies Questions & Answers

Make netstat human readable?

Is there any way to make netstat output the information in a more human readable format? even if it's not exact? I don't even care if it has to round up/down to the nearest Meg to make it work. I wind up having to stare at netstat running for while and I wish I could get it to output things in a... (10 Replies)
Discussion started by: MrEddy
10 Replies

7. UNIX for Dummies Questions & Answers

Display Directories with their sizes in human readable format

Hi, I want to list all the directories present in a particular location and want to display their sizes as well. I know "ls -lh" but it doesn't show the size of the complete directory. So i want something like dir1 266 MB dir2 2 KB dir3 22 MB ... ... file1 10 Kb ..... Thanks Sarbjit (4 Replies)
Discussion started by: sarbjit
4 Replies

8. Shell Programming and Scripting

Making big find command more human readable

This does not work. One line works but my pattern are about 100 characters long and it is messy to read. When I try to use several lines it does not two' find "$inputDirectory" \( -name 'very long pattern1' -o -name 'very long pattern2' -o -name... (1 Reply)
Discussion started by: Michael Stora
1 Replies

9. Shell Programming and Scripting

Convert epoch time stamp into human readable format

Can someone help me to write a shell script to convert epoch timestamp into human readable format 1394553600,"test","79799776.0","19073982.728571","77547576.0","18835699.285714" 1394553600,"test1","80156064.0","19191275.014286","62475360.000000","14200554.720000"... (10 Replies)
Discussion started by: Moon1234
10 Replies

10. Programming

How to parse .nessus file to get result in human readable format?

Scripting Language: bash shell script, python I want to parse .nessus file in human readable format. If any one have any ideas please help me. (2 Replies)
Discussion started by: sk151993
2 Replies
UNHIDE(8)						      System Manager's Manual							 UNHIDE(8)

NAME
unhide -- forensic tool to find hidden processes SYNOPSIS
unhide [OPTIONS] TEST_LIST DESCRIPTION
unhide is a forensic tool to find processes hidden by rootkits, Linux kernel modules or by other techniques. It detects hidden processes using six techniques. OPTIONS
-f Write a log file (unhide.log) in the current directory. -h Display help -m Do more checks. As of 2010-11-21 version, this option has only effect for the procfs, procall, checkopendir and checkchdir tests. Implies -v -r Use alternate version of sysinfo check in standard tests -V Show version and exit -v Be verbose, display warning message (default : don't display). This option may be repeated more than once. TEST_LIST The checks to do consist of one or more of the following tests. The standard tests are the aggregation of one or more elementary test(s). Standard tests : The brute technique consists of bruteforcing the all process IDs. This technique is only available on Linux 2.6 kernels. The proc technique consists of comparing /proc with the output of /bin/ps. The procall technique combinates proc and procfs tests. This technique is only available on Linux 2.6 kernels. The procfs technique consists of comparing information gathered from /bin/ps with information gathered by walking in the procfs. With -m option, this test makes more checks, see checkchdir test. This technique is only available on Linux 2.6 kernels. The quick technique combines the proc, procfs and sys techniques in a quick way. It's about 20 times faster but may give more false posi- tives. This technique is only available on Linux 2.6 kernels. The reverse technique consists of verifying that all threads seen by ps are also seen in procfs and by system calls. It is intended to ver- ify that a rootkit has not killed a security tool (IDS or other) and make ps showing a fake process instead. This technique is only available on Linux 2.6 kernels. The sys technique consists of comparing information gathered from /bin/ps with information gathered from system calls. Elementary tests : The checkbrute technique consists of bruteforcing the all process IDs. This technique is only available on Linux 2.6 kernels. The checkchdir technique consists of comparing information gathered from /bin/ps with information gathered by making chdir() in the procfs. With the -m option, it also verify that the thread appears in its "leader process" threads list. This technique is only available on Linux 2.6 kernels. The checkgetaffinity technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getaffinity() system function. This technique is only available on Linux 2.6 kernels. The checkgetparam technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getparam() system function. This technique is only available on Linux 2.6 kernels. The checkgetpgid technique consists of comparing information gathered from /bin/ps with the result of call to the getpgid() system func- tion. This technique is only available on Linux 2.6 kernels. The checkgetprio technique consists of comparing information gathered from /bin/ps with the result of call to the getpriority() system function. This technique is only available on Linux 2.6 kernels. The checkRRgetinterval technique consists of comparing information gathered from /bin/ps with the result of call to the sched_rr_get_inter- val() system function. This technique is only available on Linux 2.6 kernels. The checkgetsched technique consists of comparing information gathered from /bin/ps with the result of call to the sched_getscheduler() system function. This technique is only available on Linux 2.6 kernels. The checkgetsid technique consists of comparing information gathered from /bin/ps with the result of call to the getsid() system function. This technique is only available on Linux 2.6 kernels. The checkkill technique consists of comparing information gathered from /bin/ps with the result of call to the kill() system function. Note : no process is really killed by this test. This technique is only available on Linux 2.6 kernels. The checknoprocps technique consists of comparing the result of the call to each of the system functions. No comparison is done against /proc or the output of ps. This technique is only available on Linux 2.6 kernels. The checkopendir technique consists of comparing information gathered from /bin/ps with information gathered by making opendir() in the procfs. This technique is only available on Linux 2.6 kernels. The checkproc technique consists of comparing /proc with the output of /bin/ps. This technique is only available on Linux 2.6 kernels. The checkquick technique combines the proc, procfs and sys techniques in a quick way. It's about 20 times faster but may give more false positives. This technique is only available on Linux 2.6 kernels. The checkreaddir technique consists of comparing information gathered from /bin/ps with information gathered by making readdir() in /proc and /proc/pid/task. This technique is only available on Linux 2.6 kernels. The checkreverse technique consists of verifying that all threads seen by ps are also seen in procfs and by system calls. It is intended to verify that a rootkit has not killed a security tool (IDS or other) and make ps showing a fake process instead. This technique is only available on Linux 2.6 kernels. The checksysinfo technique consists of comparing the number of process seen by /bin/ps with information obtained from sysinfo() system call. This technique is only available on Linux 2.6 kernels. The checksysinfo2 technique is an alternate version of checksysinfo test. It might (or not) work better on kernel patched for RT, preempt or latency and with kernel that don't use the standard scheduler. It's also invoked by standard tests when using the -r option This technique is only available on Linux 2.6 kernels. Exit status: 0 if OK, 1 if a hidden or fake thread is found. BUGS
Report unhide bugs on the bug tracker on sourceforge (http://sourceforge.net/projects/unhide/) SEE ALSO
unhide-tcp (8). AUTHOR
This manual page was written by Francois Marier francois@debian.org and Patrick Gouin. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foun- dation. LICENSE
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Administration commands October 2010 UNHIDE(8)
All times are GMT -4. The time now is 02:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy