File perl-Safe.spec of Package perl-Safe

Overview Repositories Revisions Requests Users Attributes Meta

File perl-Safe.spec of Package perl-Safe

#
# spec file for package perl-Safe
#
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#

Name:           perl-Safe
Version:        2.35
Release:        0
#Upstream: CHECK(GPL-1.0+ or Artistic-1.0)
%define cpan_name Safe
Summary:        Compile and execute code in restricted compartments
License:        Artistic-1.0 or GPL-1.0+
Group:          Development/Libraries/Perl
Url:            http://search.cpan.org/dist/Safe/
Source0:        http://www.cpan.org/authors/id/R/RG/RGARCIA/%{cpan_name}-%{version}.tar.gz
Source1:        cpanspec.yml
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
%{perl_requires}

%description
The Safe extension module allows the creation of compartments in which perl
code can be evaluated. Each compartment has

* a new namespace

The "root" of the namespace (i.e. "main::") is changed to a different
  package and code evaluated in the compartment cannot refer to variables
  outside this namespace, even with run-time glob lookups and other tricks.

Code which is compiled outside the compartment can choose to place
  variables into (or _share_ variables with) the compartment's namespace
  and only that data will be visible to code evaluated in the compartment.

By default, the only variables shared with compartments are the
  "underscore" variables $_ and @_ (and, technically, the less frequently
  used %_, the _ filehandle and so on). This is because otherwise perl
  operators which default to $_ will not work and neither will the
  assignment of arguments to @_ on subroutine entry.

* an operator mask

Each compartment has an associated "operator mask". Recall that perl code
  is compiled into an internal format before execution. Evaluating perl
  code (e.g. via "eval" or "do 'file'") causes the code to be compiled into
  an internal format and then, provided there was no error in the
  compilation, executed. Code evaluated in a compartment compiles subject
  to the compartment's operator mask. Attempting to evaluate code in a
  compartment which contains a masked operator will cause the compilation
  to fail with an error. The code will not be executed.

The default operator mask for a newly created compartment is the
  ':default' optag.

It is important that you read the the Opcode manpage module documentation
  for more information, especially for detailed definitions of opnames,
  optags and opsets.

Since it is only at the compilation stage that the operator mask applies,
  controlled access to potentially unsafe operations can be achieved by
  having a handle to a wrapper subroutine (written outside the compartment)
  placed into the compartment. For example,

$cpt = new Safe;
      sub wrapper {
          # vet arguments and perform potentially unsafe operations
      }
      $cpt->share('&wrapper');

%prep
%setup -q -n %{cpan_name}-%{version}

%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}

%check
%{__make} test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%files -f %{name}.files
%defattr(-,root,root,755)
%doc Changes README

%changelog

Places

File perl-Safe.spec of Package perl-Safe

Places