GSP/GSP-Agent-Windows
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial Windows agent repository

Browse source
This commit is contained in:
Frank Harris 2026-06-08 10:45:20 -05:00
commit a0db0c2e5b
10589 changed files with 3844063 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

340
OGP64/usr/share/doc/rebase/COPYING Normal file
View file

@ -0,0 +1,340 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

176
OGP64/usr/share/doc/rebase/NEWS Normal file
View file

@ -0,0 +1,176 @@
$Id$
4.6.1
==============================================================================
* Make rebaseall a wrapper around /etc/postinstall/0p_000_autorebase.dash
(Cygwin only).
4.3.0
==============================================================================
* Add --oblivious/-O option: do not touch files already in the
database nor the rebase database itself (operation with database
is implied), only process files given with -T or on the command
line. This option can be used to rebase before testing in the
build directory without disturbing the installed packages on the
system.
4.2.0
==============================================================================
* Add --no-dynamicbase option to rebase.
* Change rebaseall to call rebase with the --no-dynamicbase option.
* Change rebaseall to use improved sed regular expressions to
generate the rebase file list.
* Change peflagsall to no longer default to enabling the --dynamicbase
option.
* Add .oct to the default peflagsall suffix list.
4.1.0
==============================================================================
* Add rebase/rebaseall touch file (i.e., -t option) support.
* Add rebaseall setup (i.e., -p option) support.
* Add .oct to the default rebaseall suffix list.
4.0.1
==============================================================================
* Change rebaseall to call rebase instead of ./rebase.
* Configure with --sysconfdir=/etc.
4.0.0
==============================================================================
* rebase and peflags now support operations on 64 bit objects.
* New rebase database functionality (see README).
* New developer application rebase-dump for displaying database contents.
* New platform support: x86_64-w64-mingw32, i686-pc-msys.
* peflags now supports short options for almost all flags.
peflags -v prints detailed information about the flags set in the
file header.
* rebase now supports long options including improved -h/--help
information.
* rebase -s/--database allows to keep a database of rebased DLLs.
This information is used in subsequent calls with the -s/--database
option to keep the entire list of DLLs in a good shape, address-wise.
* rebase -i/--info prints base address and size of DLLs given on
the command line, sorted by base address. A trailing '*' in the
last column is printed if a DLL collides with another adjacent DLL
in the list. rebase -i -s can be used to check if the DLLs in the
database are still in a good shape.
* On Cygwin, rebase actively avoids colliding with the Cygwin DLL
it is running under.
* rebaseall skips mingw directories automatically.
* rebaseall now uses the new rebase database facility.
* The imagehelper library has been much improved:
- Now supports reading and rebasing 64 bit binaries.
- New functions ReBaseImage64 and GetImageInfos64.
- Support long paths up to 32K characters.
- General API cleanup.
3.0.2
==============================================================================
* Autoconfify. Silence build warnings. Add support for building (natively,
for each platform) on mingw, msys, and cygwin. Support dash/ash usage.
Add workaround for broken getopt_long on MSYS.
3.0.1
==============================================================================
* Placeholder.
3.0:
==============================================================================
* New peflags utility allows to manipulate the following
flags in DLLs:
peflags [OPTIONS] [-T filelist | -] file(s)...
-d, --dynamicbase [BOOL] Image base address may be
relocated using address space
layout randomization (ASLR)
-t, --tsaware [BOOL] Image is Terminal Server aware
as well as a number of other flags (see --help output).
By default, cygwin DLLs have 0 for both flags. Setting -d1
for all DLLs (except cygwin1.dll) may be useful on Windows
Vista and above. Setting -t1 on all executables may be useful
on Windows Terminal Server.
Use '-v' (or any of the flag arguments with no BOOL) to
see the current flag settings for a given DLL or list of
DLLs.
* New peflagsall utility. You remember your SATs, right:
peflagsall:peflags::rebaseall:rebase
The following are the changes to rebaseall:
* Exclude cyglsa64.dll from rebase list
2.4.4:
==============================================================================
* Change rebaseall to prevent "Argument list too long" errors as
reported in:
http://www.cygwin.com/ml/cygwin/2005-09/msg00836.html
* Change rebase to use modern method to find the image's
IMAGE_NT_SIGNATURE as suggested in:
http://www.cygwin.com/ml/cygwin/2006-02/msg00645.html
* Change imagehelper library so it compiles under gcc 3.4.x
(and hopefully later) as suggested in an email from Jens Dill.
* Change rebaseall to use a tighter regular expression when
creating the rebase list.
2.4.3:
==============================================================================
The following are the changes to rebaseall:
* Changes to support Cygwin's CYGWIN=transparent_exe option.
2.4.2:
==============================================================================
The following are the changes to rebaseall:
* Change zcat to "gzip -d -c" and egrep to "grep -E" to avoid the possibly
of invoking a (bash) shell script.
2.4.1:
==============================================================================
The following are the changes to rebaseall:
* Change the "only ash processes are running" check to support 9X/Me.
* Add setting PATH to support environments that do not have Cygwin's bin
in the Windows' system PATH.
2.4:
==============================================================================
The following are the changes to rebaseall:
* Change to exit with rebase's exit code instead of unconditionally
exiting with zero (Axel Naumann).
* Convert from bash to ash script.
* Remove obsolete Apache hack.
* Add support for spaces in file and directory paths.
* Add rebasing of .so files too.
* Add suffix option (i.e., -s) to support rebasing of DLLs with
non-standard extensions.
* Add support to verify that only ash processes are running or exit.

393
OGP64/usr/share/doc/rebase/README Normal file
View file

@ -0,0 +1,393 @@
$Id$
Abstract:
================================================================================
The Cygwin rebase distribution contains four utilities, rebase, rebaseall,
peflags, and peflagsall. The first utility is modeled after Microsoft's SDK
rebase. However, instead of linking rebase against Microsoft's imagehlp
library, it is linked against Ralf Habacker's imagehelper library.
The following are the advantages of using Ralf's library:
1. rebase can be a Cygwin application. If rebase is linked against
Microsoft's imagehlp library, then it must be a Mingw application.
This is because imagehlp is dependent on Microsoft's C runtime and
therefore cannot be used in an application that is dependent on
another C runtime (i.e., Cygwin).
2. With recent improvements, libimagehelper supports operations on
64bit objects, and can itself be compiled as either a 32bit or
64bit library.
3. rebase can be used on Windows Me. For some reason, Microsoft's
imagehlp.dll does not function properly on this platform.
4. Ralf's imagehelper library also provides FixImage() which fixes
bad relocations in DLLs that can be caused by stripping.
I would like to thank Ralf Habacker for providing the imagehelper
library. This library has enabled me to create a rebase utility that
is usable by all Cygwin user (regardless of platform) on all DLLs
(regardless of stripping).
I would like to thank Chuck Wilson for providing peflags and peflagsall. This
enables Cygwin to take advantage of the Address Space Layout Randomization
facility on Windows Vista and later.
Background
================================================================================
The rebaseall utility is a convenient way for users that suffer from the
Cygwin rebase problem to rebase their entire system (i.e., all of their
DLLs). The following is a list of known Cygwin applications that are
affected by the rebase problem:
Apache
Perl
Python
The rebase problem is due to fork() failing when it is unable to load
DLLs in the child at the same address as in the parent. This is caused
by DLLs which have conflicting base addresses. An error message like
the following will be displayed when the problem is triggered:
C:\cygwin\bin\python.exe: *** unable to remap C:\cygwin\bin\cygssl.dll to same address as parent(0xDF0000) != 0xE00000
On Cygwin, rebaseall has been replaced by the postinstall script
/etc/postinstall/0p_000_autorebase.dash, provided by the _autorebase
package. This script runs every time Cygwin's setup program is run.
See /usr/share/doc/Cygwin/_autorebase.README.
For the convenience of users who may wish to rebase between runs of
setup, rebaseall is now a wrapper around that postinstall script.
On Vista and newer, it is possible to employ the Address Space Layout
Randomization facility to help solve the image load address clashing
problem:
Since Windows relies on relocations instead of position
independent code, a DLL must be loaded at the same address
in each process that uses it to allow the physical memory
used by the DLL to be shared. To facilitate this behaviour,
a global bitmap called _MiImageBitMap is used to represent
the address space from 0x50000000 to 0x78000000. The bitmap
is 0x2800 bits in length with each bit representing 64KB
of memory. As each DLL is loaded, its position is recorded
by setting the appropriate bits in the bitmap to mark the
memory where the DLL is being mapped. When the same DLL
is loaded in another process, its section object is reused
and it is mapped at the same virtual addresses.
https://web.archive.org/web/20080913064223/http%3A%2F%2Ftaossa.com%2Farchive%2Fbh08sotirovdowd.pdf
Thus, IF all cygwin dlls (except cygwin1.dll) -- or, at least the
ones for which you often get the *** unable to remap *** error --
are marked ASLR-compatible, then the Windows runtime loader can be
coerced into ensuring that the DLLs are loaded at the same memory
location for all concurrent processes. After using the peflagsall
utility to mark the dlls appropriately, you may need to reboot to
cause Windows to take notice.
Requirements:
================================================================================
The following packages or later are required to build and/or execute Cygwin
rebase/peflags, and/or rebaseall/peflagsall:
binutils 2.20.51-2
cygwin 1.7.9-1
dash 0.5.6.1-2
gcc4 4.3.4-4
coreutils 8.10-1
grep 2.6.3-1
gzip 1.4-1
sed 4.2.1-1
w32api 3.17-2
Install:
================================================================================
Cygwin rebase does not require any special installation procedures.
If the database is used, Cygwin and MSYS rebase will expect to find the
databases:
/etc/rebase.db.i386
/etc/rebase.db.x86_64
For MinGW, the database location is deduced as
<location-of-rebase.exe>/../etc/rebase.db.i386
<location-of-rebase.exe>/../etc/rebase.db.x86_64
rebaseall, by default, uses the database.
Usage:
================================================================================
Use the following procedure to rebase your entire system:
1. shutdown all Cygwin processes and services
2. start ash or dash (do not use bash or a terminal emulator like rxvt
or mintty). The easiest way to do this is to use Windows Explorer
and navigate to the top level of your cygwin installation, and
double-click ash.exe or dash.exe in the bin/ directory.
3. execute /bin/rebaseall (in the ash/dash window)
If you get any errors due to DLLs being in-use or read-only, then take the
appropriate action and rerun rebaseall. Otherwise, you run the risk of fork()
failing.
Use a similar procedure to set the peflags for all cygwin executables and
dlls on your entire system:
1. shutdown all Cygwin processes and services
2. start ash or dash (do not use bash or a terminal emulator like rxvt
or mintty). The easiest way to do this is to use Windows Explorer
and navigate to the top level of your cygwin installation, and
double-click ash.exe or dash.exe in the bin/ directory.
3. execute /bin/peflagsall (in the ash window)
Both procedures may be combined into a single, 4-step procedure if desired.
Note that by default, peflagsall will set the tsaware flag on all executables
(ash.exe and peflags.exe themselves excluded), and will remove the dynamicbase
flag on all 'dll', 'so' and 'oct' files (cygwin1.dll and cyglsa64.dll excluded).
If you are used to using the -s option with rebaseall, to add additional
suffixes to the rebase list (such as .oct), be warned that peflags behaves
differently. If you specify custom suffixes, you must restate the default
ones, AND explicitly specify what action to perform; peflagsall disables
all default behavior when custom settings are used. For instance:
peflagsall -s oct -s dll -s so -s exe -d 1 -t 1
^^^^^^ ^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^
custom restate default restate
suffix suffixes default actions
Whereas rebaseall only has a single action, and new suffixes are added
to the existing default set of suffixes. See 'Command line syntax', in
the next section.
Command line syntax
================================================================================
rebaseall (MinGW and MSYS only)
--------------------------------------------------------------------------------
The following is the rebaseall command line syntax:
rebaseall [-b BaseAddress] [-o Offset] [-s DllSuffix] [-T FileList | -] [-4|-8] [-p] [-t] [-v]
where:
-b => base address used by rebase (default: 0x70000000)
-o => offset between each DLL rebased (default: 0x10000 MinGW/MSYS, 0x0 Cygwin)
-p => skip test for running ash or dash only. This option is supposed to
be used by Cygwin's setup tool. Only use it if you know what you're
doing!
-s => specify DLL suffix, use multiple if necessary (default: dll, so, oct)
-T => specify filelist (or stdin) to list additional files
-4 => operate only on 32bit objects (ignore 64bit objects) (*)
-8 => operate only on 64bit objects (ignore 32bit objects) (*)
-t => change modification timestamp of successfully rebased files
-v => verbose (default: off)
(*) -4 and -8 are mutually exclusive. -4 is the default if rebaseall is
executed in a 32bit environment; -8 is the default if rebaseall is executed
64bit environment.
rebaseall now uses the database functionality provided by rebase. See the
description below.
peflagsall
--------------------------------------------------------------------------------
The following is the peflagsall command line syntax:
peflagsall [-p extra_args] [-d bool] [-t bool] [-s suffix] [-T FileList | -] [-vnh]
When invoked with no arguments, peflagsall modifies every cygwin exe|dll|so|oct
on the system: .exe files have their tsaware flag set, while .dll, .so and .oct
files have their dynamicbase flag removed. However, if any of [-d|-t|-s] are
specified then ONLY the actions so specified will occur.
-p extra_args pass extra_args to peflags.exe
-d bool set the dynamicbase flag to 'bool' on all specified files
-t bool set the tsaware flag to 'bool' on all specified files
-s suffix search for all files with the specified suffix(es)
default: 'exe|dll|so|oct'
-T FileList in addition to files located via the normal search and
suffix list, also operate on files listed in FileList
May be '-' which indicates stdin
-n do not modify any files, but display the peflags commands
-k keep all temporary files
-v verbose mode
-h show this help
bool may be '0', '1', 'true', 'false', 'yes', or 'no'
Note: peflagsall will NOT set the dynamicbase flag on executables, nor will
it set the tsaware flag on dlls. If you must do this, use peflags itself
rebase
--------------------------------------------------------------------------------
The following is the rebase command line syntax:
rebase [OPTIONS] [FILE]...
Rebase PE files, usually DLLs, to a specified address or address range.
-4, --32 Only rebase 32 bit DLLs. (*)
-8, --64 Only rebase 64 bit DLLs. (*)
-b, --base=BASEADDRESS Specifies the base address at which to start rebasing.
-s, --database Utilize the rebase database to find unused memory
slots to rebase the files on the command line to.
(Implies -d).
If -b is given, too, the database gets recreated.
-O, --oblivious Do not change any files already in the database
and do not record any changes to the database.
(Implies -s).
-i, --info Rather then rebasing, just print the current base
address and size of the files. With -s, use the
database. The files are ordered by base address.
A '*' at the end of the line is printed if a
collisions with an adjacent file is detected.
One of the options -b, -s, -O or -i is mandatory. If no rebase database
exists yet, -b is required together with -s.
-d, --down Treat the BaseAddress as upper ceiling and rebase
files top-down from there. Without this option the
files are rebased from BaseAddress bottom-up.
With the -s option, this option is implicitly set.
-n, --no-dynamicbase Remove PE dynamicbase flag from rebased DLLs, if set.
-o, --offset=OFFSET Specify an additional offset between adjacent DLLs
when rebasing. Default is no offset.
-t, --touch Use this option to make sure the file's modification
time is bumped if it has been successfully rebased.
Usually rebase does not change the file's time.
-T, --filelist=FILE Also rebase the files specified in FILE. The format
of FILE is one DLL per line.
-q, --quiet Be quiet about non-critical issues.
-v, --verbose Print some debug output.
-V, --version Print version info and exit.
-h, --help, --usage This help.
(*) -4 and -8 are mutually exclusive. -4 is the default if rebase.exe itself
was compiled as a 32bit application; -8 is the default if rebase.exe is
a 64bit application.
There are actually two separate database files, for 32bit and 64bit objects.
On Cygwin and MSYS, these are:
/etc/rebase.db.i386
/etc/rebase.db.x86_64
For MinGW, the database location is deduced as
<location-of-rebase.exe>/../etc/rebase.db.i386
<location-of-rebase.exe>/../etc/rebase.db.x86_64
The (optional) database allows to easily rebase new DLLs so that they don't
collide with other DLLs which already have been rebased. Because rebaseall uses
the database, rebaseall will now only rebase new DLLs, or those DLLs which
have been updated -- e.g. their current ImageBase does not match the value in
the database, or their size has changed (grown) such that they no longer 'fit'
in the previously-assigned location. (If an updated DLL still fits in its
previously-assigned location, it will be rebased back to that location).
Thus, the (optional) database allows to keep an installation in a stable
state, and only modifies the ImageBase of DLLs when absolutely necessary.
A complete rebase can be forced by (a) specifying -b to either rebase.exe
itself, or to rebaseall, or (b) deleting the existing database files and
re-running rebase/rebaseall.
peflags
--------------------------------------------------------------------------------
The following is the peflags command line syntax:
Usage: peflags [OPTIONS] file(s)...
Sets, clears, or displays various flags in PE files (that is,
exes and dlls). For each flag, if an argument is given, then
the specified flag will be set or cleared; if no argument is
given, then the current value of that flag will be displayed.
-d, --dynamicbase [BOOL] Image base address may be relocated using
address space layout randomization (ASLR)
-f, --forceinteg [BOOL] Code integrity checks are enforced
-n, --nxcompat [BOOL] Image is compatible with data execution
prevention
-i, --no-isolation [BOOL] Image understands isolation but do not
isolate the image
-s, --no-seh [BOOL] Image does not use SEH. No SE handler may
be called in this image
-b, --no-bind [BOOL] Do not bind this image
-W, --wdmdriver [BOOL] Driver uses the WDM model
-t, --tsaware [BOOL] Image is Terminal Server aware
-w, --wstrim [BOOL] Aggressively trim the working set.
-l, --bigaddr [BOOL] The application can handle addresses
larger than 2 GB
-S, --sepdbg [BOOL] Debugging information was removed and
stored separately in another file.
-T, --filelist FILE Indicate that FILE contains a list
of PE files to process
-v, --verbose Display diagnostic information
-V, --version Display version information
-h, --help Display this help
BOOL: may be 1, true, or yes - indicates that the flag should be set
if 0, false, or no - indicates that the flag should be cleared
if not present, then display symbolicly the value of the flag
Valid forms for short options: -d, -d0, -d1, -dfalse, etc
Valid forms for long options : --tsaware, --tsaware=true, etc
To set a value, and display the results symbolic, repeat the option:
--tsaware=true --tsaware -d0 -d
Source:
================================================================================
Cygwin rebase builds OOTB under Cygwin, MinGW, and MSYS. It also can be compiled
using the 64bit mingw64 compiler: x86_64-w64-mingw32-gcc. Cross compilation is
(somewhat) supported, but YMMV.
Build:
================================================================================
See build.sh in the source archive for my exact build recipe for configuring,
making, and packaging this distribution.
Test:
================================================================================
rebase does not contain any regression tests.
peflagsall may be invoked with the -n, -k, and -v options to allow inspection
of what it WOULD do, without actually doing it.
peflags will make no changes to any files unless it is given an flagname
argument *with* a boolean value for that flag (0 or 1). If no boolean argument
is provided, then peflags will merely display the current value of the flag in
the specified files.
Issues:
================================================================================
The following are the known Cygwin rebase issues:
1. rebase does not handle in-use DLLs.
2. rebase skips read-only DLLs.
These issues also apply to the peflags utility.
Homepage:
================================================================================
The primary rebase web site is:
https://sourceware.org/cygwin-apps/
Download:
================================================================================
Access to the git development sources is available:
git clone https://cygwin.com/git/cygwin-apps/rebase.git
Mailing Lists:
================================================================================
Please report problems, suggestions, etc. to <cygwin@cygwin.com>.
Maintainer:
================================================================================
Jason Tishler <jason@tishler.net>

4
OGP64/usr/share/doc/rebase/Todo Normal file
View file

@ -0,0 +1,4 @@
$Id$
Change rebaseall to handle in-use DLLs.
Change rebase to indicate why it considers a DLLs not to be rebaseable.