libc re-bassing


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers libc re-bassing
# 1  
Old 03-24-2008
And now for your question:

every program that you execute has two basic portions:
1 - code section
2 - data section
well there are more sections but if i start explaining, i will have to devote the whole day
code section is the section that the processor executes - i mean the instructions
and data section is where all the data is stored like integer values, constants and stuff - this is also called text section

libc addresses get randomized because of various factors like the amount of space that kernel occupys in the RAM or RAM size itself, when libc is loaded, etc
.text will be static - coz its the text section devoted for storing data. Remember every process has a certain portion of memory reserved for it?
You say .text is static because you are actually calculating the offset address from where the code starts in the memory. In real if you calculate .text will be in different parts of memory in each and every computer

Now please explain me: what does egress has to do with it? I mean egress is a packet filtering tool as far as my knowledge goes. How would it scan the computer's memory and find out about this? If you are sending some sort of shell code to spawn a remote shell egress CANNOT detect it. well it can if it start comparing the text segement offset address from the packet's beginning. but a normal filter like egress cannot do that.This is the job of an IDS (snort?)

If you really want deeper knowledge in this field about bypassing firewalls or IDS check out phrack.org. Sorry i cannot provide you with the exact link as i dont access phrack from work (they are kind of picky)

BTW langley cyber attack was a DDOS attack and not targeted on libc though.

~s4g3
 
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Red Hat

RPM Install error: libc.so.6 is needed by

I have an application rpm which when installed is failing to get installed with error error: Failed dependencies: libc.so.6 is needed by testSam-4.7.x86_64 libc.so.6(GLIBC_2.0) is needed by testSam-4.7.x86_64 libc.so.6(GLIBC_2.1) is needed by testSam-4.7.x86_64 ... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

2. UNIX for Advanced & Expert Users

libc.so.1 (SUNW_1.22.7) => (version not found)

What package would I need to get this file? SUNW_1.22.7. Please help. thank you. :) (5 Replies)
Discussion started by: SystemAddict
5 Replies

3. AIX

Dependent modules libc.a and libpthreads.a

Hello I am trying to install ActivePerl Pro Studio and I am seeing the following errors. Could not load program ./setup: Symbol resolution failed for setup because: Symbol ___memcmp (number 1) is not exported from dependent module /usr/lib/libc.a(shr.o). ... (2 Replies)
Discussion started by: flagman5
2 Replies

4. HP-UX

hpux-itanium 64 bit problem for libC

i am trying to build on hpux-itanium 64 bit platform. my application needs to link to 64 bit version of the library libCsup.so This library is present in /usr/lib/hpux64/libCsup.so I am specifying the location of this library as linker flags LDFLAGS := -Wl,-N -Wl,+s... (0 Replies)
Discussion started by: skyineyes
0 Replies

5. Linux

Deploying Qt on CentOS - libc.so.6 update problem

I am developing a simple client-server (TCP) application using QT. The server side is to run on CentOS. I am developing both the server and client programs using Ubuntu. I am now attempting to deploy an experimental version of the server application on the CentOS server, but I am not yet... (2 Replies)
Discussion started by: David Brown
2 Replies

6. AIX

Problem restoring libc.a (AIX 5.3)

Hi, The symbolic link from /usr/lib/libc.a to /usr/ccs/lib/libc.a was deleted by accident. So we are trying to restore it, but we have some problems. After booting from CD, and access the rootvg volume group (without mounting the system), we tried to execute the next commands: mount /dev/hd4... (1 Reply)
Discussion started by: NicoAIX
1 Replies

7. Programming

path for libc.a

how can i determine the path for libc.a? i wonder where it is located in my unix machine (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies

8. Programming

xldb WARNING: libC.a(ansi_32.o) has been stripped

Hi, When i start the Debugger i get this warning: xldb WARNING: /usr/lpp/xlC/lib/libC.a(ansi_32.o) has been stripped. anyone know what this warning means? xldb is a Debugger under AIX. Lazzar (2 Replies)
Discussion started by: Lazzar
2 Replies
Login or Register to Ask a Question
LIBC(7) 						     Linux Programmer's Manual							   LIBC(7)

NAME
libc - overview of standard C libraries on Linux DESCRIPTION
The term "libc" is commonly used as a shorthand for the "standard C library", a library of standard functions that can be used by all C programs (and sometimes by programs in other languages). Because of some history (see below), use of the term "libc" to refer to the stan- dard C library is somewhat ambiguous on Linux. glibc By far the most widely used C library on Linux is the GNU C Library <http://www.gnu.org/software/libc/>, often referred to as glibc. This is the C library that is nowadays used in all major Linux distributions. It is also the C library whose details are documented in the rel- evant pages of the man-pages project (primarily in Section 3 of the manual). Documentation of glibc is also available in the glibc manual, available via the command info libc. Release 1.0 of glibc was made in September 1992. (There were earlier 0.x releases.) The next major release of glibc was 2.0, at the beginning of 1997. The pathname /lib/libc.so.6 (or something similar) is normally a symbolic link that points to the location of the glibc library, and exe- cuting this pathname will cause glibc to display various information about the version installed on your system. Linux libc In the early to mid 1990s, there was for a while Linux libc, a fork of glibc 1.x created by Linux developers who felt that glibc develop- ment at the time was not sufficing for the needs of Linux. Often, this library was referred to (ambiguously) as just "libc". Linux libc released major versions 2, 3, 4, and 5 (as well as many minor versions of those releases). For a while, Linux libc was the standard C library in many Linux distributions. However, notwithstanding the original motivations of the Linux libc effort, by the time glibc 2.0 was released, it was clearly superior to Linux libc, and all major Linux distributions that had been using Linux libc soon switched back to glibc. (Since this switch occurred over a decade ago, man-pages no longer takes care to document Linux libc details. Nevertheless, the history is visible in vestiges of information about Linux libc that remain in some manual pages, in particular, references to libc4 and libc5.) Other C libraries There are various other less widely used C libraries for Linux. These libraries are generally smaller than glibc, both in terms of fea- tures and memory footprint, and often intended for building small binaries, perhaps targeted at development for embedded Linux systems. Among such libraries are uClibc (http://www.uclibc.org/) and dietlibc (http://www.fefe.de/dietlibc/). Details of these libraries are gen- erally not covered by the man-pages project. SEE ALSO
syscalls(2), feature_test_macros(7), man-pages(7), standards(7) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2012-08-05 LIBC(7)