Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Where to find Kernel development Information Post 302680223 by alister on Wednesday 1st of August 2012 01:00:52 PM
Old 08-01-2012
If you want to find out what kernel developers are working on at the moment, there's probably no better way than to subscribe to their mailing list: http://lkml.org/

Regards,
Alister
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Please help me find out system information

I'm just getting started with unix and would like to know 1) how to tell how big the harddrive is 2) how to tell if there are multiple harddrive installed on the machine 3) a relitavely easy way to tell what programs are installed on the machine. I'm using Sun OS 5.6 Thanks (3 Replies)
Discussion started by: ViperD
3 Replies

2. UNIX for Dummies Questions & Answers

How do I find information about the hardware?

Hello I used to Red Hat and the common Linux commands, but now I have to deal with a SCO-Unix (Unix Ware 7). I have to find information about the hardware. What networkcard is installed? What graphiccard is installed? Which SCSI-Adapter and what kind of harddisks? What software is... (3 Replies)
Discussion started by: Fwurm
3 Replies

3. News, Links, Events and Announcements

Current Kernel Development

Information on current kernel development status & Compatibality Status. (0 Replies)
Discussion started by: killerserv
0 Replies

4. UNIX for Dummies Questions & Answers

How do I find route table information

I am trying to install a new AIX server and I am migrating off of an older AIX server. Does anyone have a quick and easy method for getting the static route information from the old server so I can just maybe copy a file over to the new server ? (1 Reply)
Discussion started by: Docboyeee
1 Replies

5. HP-UX

kernel, memory and patches information

I kind of forget easily. Is anyone remember the command to find kernel, memory and patches information of HPUX 11.0 machine? Thank you! (0 Replies)
Discussion started by: Teh Tiack Ein
0 Replies

6. HP-UX

Information about kernel modules

Hi all, what do kernel modules libaudit, klog and strlog do? Specifically I want to determine if it was possible for us to determine if kernel level auditing is enabled at all? regards (0 Replies)
Discussion started by: slash_blog
0 Replies

7. Shell Programming and Scripting

Find information from complicated strings

Hi experts, I have the file with these lines: var1=thu_13:12:32,var2=Microsoft,var3=240ms,var4=Mozilla/4.0_(sun;_MSIR_3-4;_windows.;_NET_1.1323.53 var1=thu_13:13:32,var2=Microsoft,var3=213ms,var4=Mozilla/4.0_(sun;_MSIR_3-4;_windows.;_NET_1.1323.53... (9 Replies)
Discussion started by: lalelle
9 Replies

8. Programming

Dynamic information of Kernel using multithreading

Hi , I am new to this forum. Can someone help me on this question, I have no clue how to proceed . Its urgent.. A continuous program should print out the following dynamic information (average of an interval). Internally, there should be two parameters with your program, one is the probing... (5 Replies)
Discussion started by: parkview
5 Replies

9. Shell Programming and Scripting

find information about logins

Hi, all I want to make a bash script that print all users from a system using last command. I want to print the number of user's login in the format (descending order): 5 user1 address1 4 user2 address2 I am trying the command last | awk '{print $1 " " $3}' | sort | uniq ... (9 Replies)
Discussion started by: peter20
9 Replies

10. Red Hat

Command to find the harddisk information

I tried to find the harddisk information using the command hdparm -i /dev/sda. But I couldn't get the info. Is there any similar command to find the harddisk serial number. (5 Replies)
Discussion started by: gsiva
5 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 10:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy