[pcre-dev] [Bug 2469] Portability fix for secure_getenv usag…

Top Page

Reply to this message
Author: admin
Date:  
To: pcre-dev
Subject: [pcre-dev] [Bug 2469] Portability fix for secure_getenv usage
https://bugs.exim.org/show_bug.cgi?id=2469

Petr Pisar <ppisar@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppisar@???


--- Comment #5 from Petr Pisar <ppisar@???> ---
Linux mremap(2) supports it in a different way. From a manual:

       If  the value of old_size is zero, and old_address refers to a shareable
mapping
       (see mmap(2) MAP_SHARED), then mremap() will create a new mapping  of 
the  same
       pages.  new_size will be the size of the new mapping and the location of
the new
       mapping may be specified with new_address; see the description  of 
MREMAP_FIXED
       below.   If  a new mapping is requested via this method, then the
MREMAP_MAYMOVE
       flag must also be specified.


But I worry MAP_REMAPDUP won't help you because you should get a failure on
changing the permissions from writeable to executable if the security policy is
correctly enforced.

--
You are receiving this mail because:
You are on the CC list for the bug.