Linux-Development-Sys Digest #796, Volume #7     Mon, 24 Apr 00 13:13:10 EDT

Contents:
  Problems with MACRO in glibc include (Sangohn Christian)
  Re: .DLL not present in W2K, MICROSOFT GUILTY OF COVERUP! (Stephen Harris)
  Re: How To Protect Memory From Swapping ??? (Nate Eldredge)

----------------------------------------------------------------------------

From: Sangohn Christian <[EMAIL PROTECTED]>
Subject: Problems with MACRO in glibc include
Date: Sun, 23 Apr 2000 17:11:59 +0200
Reply-To: [EMAIL PROTECTED]

Hi!

I�d like to use the macro defined as follows in the /usr/include/unistd.h:

#ifdef __USE_GNU

/* Evaluate EXPRESSION, and repeat as long as it returns -1 with `errno'
   set to EINTR.  */

# define TEMP_FAILURE_RETRY(expression) \
  (__extension__                                                              \
    ({ long int __result;                                                     \
       do __result = (long int) (expression);                                 \
       while (__result == -1L && errno == EINTR);                             \
       __result; }))                                                          \


But despite of 
#include <unistd.h>                     /* UNIX Standard functions */
#define __USE_GNU 1 /*  */
in my header file and/or -D__USE_GNU as compiler flag, the macro is still
not referenced and is considered undeclared by the compiler.

What am I doing wrong and what should I do?

TIA

------------------------------

Crossposted-To: 
comp.os.linux.advocacy,comp.os.ms-windows.advocacy,comp.os.ms-windows.nt.advocacy,comp.os.linux.networking,comp.os.linux.security,comp.os.ms-windows.networking.tcp-ip
From: [EMAIL PROTECTED] (Stephen Harris)
Subject: Re: .DLL not present in W2K, MICROSOFT GUILTY OF COVERUP!
Date: Sun, 23 Apr 2000 14:59:38 GMT

Chad Myers ([EMAIL PROTECTED]) wrote:

: There was no backdoor. Illegal DLL?  Later, only after the WSJ printed the FUD,
: was there a minor buffer overrun found. However, the "!seineew era..." string
: was not a password, and NO ONE has yet successfully used it as a password to
: obtain anything from a server with FP98 extensions.

I really shouldn't be drawn into this however...

1) There is a buffer overflow (unrelated to the original shouting)
2) The weenie string _is_ a password by any sane definition of the word,
   because it is a shared secret used by the FP98 code to obfuscate the
   communications chanel
3) A related bug allows anyone with author privs to read files from other
   peoples sites on a shared hosting machine - this bug requires the weenie
   password to generate the request properly.
4) The code has been demonstrated in real life by Rain Forest Puppy
4a) Read RFP's humorous take on the current ranting.  Very funny, but
    quite accurate!
5) Microsoft admitted a fault, then retracted the admission.
6) This has nothing to do with any of the articles.  Followups mis-set
-- 
                                 Stephen Harris
                 [EMAIL PROTECTED]   http://www.spuddy.org/
      The truth is the truth, and opinion just opinion.  But what is what?
       My employer pays to ignore my opinions; you get to do it for free.      
  * Meeeeow ! Call  Spud the Cat on > 01708 442043 < for free Usenet access *

------------------------------

From: Nate Eldredge <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.linux.development,comp.os.linux.development.apps,linux.dev.c-programming,linux.redhat.development
Subject: Re: How To Protect Memory From Swapping ???
Date: 23 Apr 2000 11:52:14 -0700

David Steuber <[EMAIL PROTECTED]> writes:

> [EMAIL PROTECTED] (fvw) writes:
> 
> ' Correct, or mlockall. You need to be root for this to work under
> linux though.
> 
> Can the app be owned by root and have the suid bit set?

Yes, that's just like being root.  Be careful, though, that the user
doesn't end up doing more rootly stuff than mlockall :)  It's best to
call it as soon as possible and then drop root privileges.

> What about kernel drivers?  It seems to me that they are the type of
> application that would most need to have locked memory for soft
> realtime requirements.

Kernel memory is always locked.  It's never paged out unless
specifically requested, AFAIK.

-- 

Nate Eldredge
[EMAIL PROTECTED]

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.development.system) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Development-System Digest
******************************

Reply via email to