Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
05be93a1
Commit
05be93a1
authored
Aug 27, 2002
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add strong security warning about the rexec module.
Closes SF patch #600861. Minor markup changes.
parent
05d01cbc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
5 deletions
+17
-5
Doc/lib/librexec.tex
Doc/lib/librexec.tex
+17
-5
No files found.
Doc/lib/librexec.tex
View file @
05be93a1
...
...
@@ -5,7 +5,6 @@
\modulesynopsis
{
Basic restricted execution framework.
}
This module contains the
\class
{
RExec
}
class, which supports
\method
{
r
_
eval()
}
,
\method
{
r
_
execfile()
}
,
\method
{
r
_
exec()
}
, and
\method
{
r
_
import()
}
methods, which are restricted versions of the standard
...
...
@@ -15,10 +14,23 @@ Code executed in this restricted environment will
only have access to modules and functions that are deemed safe; you
can subclass
\class
{
RExec
}
to add or remove capabilities as desired.
\note
{
The
\class
{
RExec
}
class can prevent code from performing
unsafe operations like reading or writing disk files, or using TCP/IP
sockets. However, it does not protect against code using extremely
large amounts of memory or processor time.
}
\begin{notice}
[warning]
While the
\module
{
rexec
}
module is designed to perform as described
below, it does have a few known vulnerabilities which could be
exploited by carefully written code. Thus it should not be relied
upon in situations requiring ``production ready'' security. In such
situations, execution via sub-processes or very careful
``cleansing'' of both code and data to be processed may be
necessary. Alternatively, help in patching known
\module
{
rexec
}
vulnerabilities would be welcomed.
\end{notice}
\begin{notice}
The
\class
{
RExec
}
class can prevent code from performing unsafe
operations like reading or writing disk files, or using TCP/IP
sockets. However, it does not protect against code using extremely
large amounts of memory or processor time.
\end{notice}
\begin{classdesc}
{
RExec
}{
\optional
{
hooks
\optional
{
, verbose
}}}
Returns an instance of the
\class
{
RExec
}
class.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment