Administrator Guide

● UPX is not a software protection tool; by requiring that you use the unmodified UPX version for your proprietary programs
we make sure that any user can decompress your program. This protects both you and your users as nobody can hide
malicious code - any program that cannot be decompressed is highly suspicious by definition.
● You can integrate all or part of UPX and UCL into projects that are compatible with the GNU GPL, but obviously you cannot
grant any special exceptions beyond the GPL for our code in your project.
● We want to actively support manufacturers of virus scanners and similar security software. Please contact us if you would
like to incorporate parts of UPX or UCL into such a product.
Markus F.X.J. Oberhumer [e-mail]
Laszlo Molnar [e-mail]
Linz, Austria, 25 Feb 2000
Additional License(s)
The UPX license file is at http://upx.sourceforge.net/upx-license.html.
VIM
vim 7.2
http://www.vim.org/
vim-base 7.2
http://www.vim.org/
VIM LICENSE
I) There are no restrictions on distributing unmodified copies of Vim except that they must include this license text. You can also
distribute unmodified parts of Vim, likewise unrestricted except that they must include this license text. You are also allowed to
include executables that you made from the unmodified Vim sources, plus your own usage examples and Vim scripts.
II) It is allowed to distribute a modified (or extended) version of Vim, including executables and/or source code, when the
following four conditions are met:
1) This license text must be included unmodified.
2) The modified Vim must be distributed in one of the following five ways:
a) If you make changes to Vim yourself, you must clearly describe in the distribution how to contact you. When the maintainer
asks you (in any way) for a copy of the modified Vim you distributed, you must make your changes, including source code,
available to the maintainer without fee. The maintainer reserves the right to include your changes in the official version of Vim.
What the maintainer will do with your changes and under what license they will be distributed is negotiable. If there has been no
negotiation then this license, or a later version, also applies to your changes.
The current maintainer is Bram Moolenaar <[e-mail]>. If this changes it will be announced in appropriate places (most
likely vim.sf.net, ww.vim.org and/or comp.editors). When it is completely impossible to contact the maintainer, the obligation to
send him your changes ceases. Once the maintainer has confirmed that he has received your changes they will not have to be
sent again.
b) If you have received a modified Vim that was distributed as mentioned under a) you are allowed to further distribute it
unmodified, as mentioned at I). If you make additional changes the text under a) applies to those changes.
c) Provide all the changes, including source code, with every copy of the modified Vim you distribute. This may be done in the
form of a context diff. You can choose what license to use for new code you add. The changes and their license must not
restrict others from making their own changes to the official version of Vim.
d) When you have a modified Vim which includes changes as mentioned under c), you can distribute it without the source code
for the changes if the following three conditions are met:
- The license that applies to the changes permits you to distribute the changes to the Vim maintainer without fee or restriction,
and permits the Vim maintainer to include the changes in the official version of Vim without fee or restriction.
- You keep the changes for at least three years after last distributing the corresponding modified Vim. When the maintainer or
someone who you distributed the modified Vim to asks you (in any way) for the changes within this period, you must make them
available to him.
- You clearly describe in the distribution how to contact you. This contact information must remain valid for at least three years
after last distributing the corresponding modified Vim, or as long as possible.
147