PDA

View Full Version : SecuROM README.txt



HykCraft
08-23-2007, 09:25 PM
Here's what I found on my Vista machine.. took a while to find the hidden folders because they are placed in different areas than in XP.

readme.txt

-----------------------------------------------------------------------------------------------------------------------------
PLEASE DO NOT DELETE THE FILES IN THIS FOLDER BECAUSE YOU MIGHT LOOSE ESSENTIAL DIGITAL RIGHTS.
READ BELOW
-----------------------------------------------------------------------------------------------------------------------------

Technical Information for the PC Administrator:

The files securom_v7_01.dat and securom_v7_01.bak have been created during the installation of a SecuROM protected application.
It guarantees more user convenience because the original disc does not have to be in the local drive at all times anymore.
It is necessary for copy protected CDs, demo versions and protected software downloaded from the Internet.
The file contains your licences for all products which are SecuROM protected, therefore it will not be deleted automatically.

-----------------------------------------------------------------------------------------------------------------------------
PLEASE DO NOT DELETE THE FILE BECAUSE YOU MIGHT LOOSE ESSENTIAL DIGITAL RIGHTS.
-----------------------------------------------------------------------------------------------------------------------------

The information contained in securom_v7_01.dat will not be transferred to any other computer without your permission.

This security system is connected with a MS Windows Service called "SecuROM User Access Service".
This module is started automatically when launching a protected application if the user is logged in with Windows administrator rights.
In case users do not have administrator rights we recommend to keep it running.

See www.securom.com for further information

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

The following text is reproduced here to comply with OpenSSL license terms:

================================================== ==================
Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.

3. All advertising materials mentioning features or use of this
software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
endorse or promote products derived from this software without
prior written permission. For written permission, please contact
openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL"
nor may "OpenSSL" appear in their names without prior written
permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
================================================== ==================

This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com). This product includes software written by Tim
Hudson (tjh@cryptsoft.com).
================================================== ==================

They can't even spell "lose" right.. with LOOSE.. lol.

Hiromoon
08-23-2007, 09:45 PM
Actually that's a common mistake.

Interesting to note:

This security system is connected with a MS Windows Service called "SecuROM User Access Service".
This module is started automatically when launching a protected application if the user is logged in with Windows administrator rights.
In case users do not have administrator rights we recommend to keep it running.

HykCraft
08-23-2007, 09:47 PM
Yeah, I was kinda hoping someone else would point that out too.

Hiromoon
08-23-2007, 09:49 PM
While not an EULA, that's kinda binding right there.

Course, it'd help if people actually knew what SecuRom actually DID. While a Rootkit finder may tag it, a bit of research into whether or not it actually does what it says right there would help out alot.