ヤミRoot VoidGate
User / IP
:
216.73.216.49
Host / Server
:
146.88.233.70 / www.dev.loger.cm
System
:
Linux hybrid1120.fr.ns.planethoster.net 3.10.0-957.21.2.el7.x86_64 #1 SMP Wed Jun 5 14:26:44 UTC 2019 x86_64
Command
|
Upload
|
Create
Mass Deface
|
Jumping
|
Symlink
|
Reverse Shell
Ping
|
Port Scan
|
DNS Lookup
|
Whois
|
Header
|
cURL
:
/
usr
/
share
/
perl5
/
Config
/
Viewing: Extensions.pm
package Config::Extensions; use strict; use vars qw(%Extensions $VERSION @ISA @EXPORT_OK); use Config; require Exporter; $VERSION = '0.01'; @ISA = 'Exporter'; @EXPORT_OK = '%Extensions'; foreach my $type (qw(static dynamic nonxs)) { foreach (split /\s+/, $Config{$type . '_ext'}) { s!/!::!g; $Extensions{$_} = $type; } } 1; __END__ =head1 NAME Config::Extensions - hash lookup of which core extensions were built. =head1 SYNOPSIS use Config::Extensions '%Extensions'; if ($Extensions{PerlIO::via}) { # This perl has PerlIO::via built } =head1 DESCRIPTION The Config::Extensions module provides a hash C<%Extensions> containing all the core extensions that were enabled for this perl. The hash is keyed by extension name, with each entry having one of 3 possible values: =over 4 =item dynamic The extension is dynamically linked =item nonxs The extension is pure perl, so doesn't need linking to the perl executable =item static The extension is statically linked to the perl binary =back As all values evaluate to true, a simple C<if> test is good enough to determine whether an extension is present. All the data uses to generate the C<%Extensions> hash is already present in the C<Config> module, but not in such a convenient format to quickly reference. =head1 AUTHOR Nicholas Clark <nick@ccl4.org> =cut
Coded With 💗 by
0x6ick