Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 18.188.91.223
66 Domain
8.0.30
amvm
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
perl-Net-LibIDN-0.12 /
[ HOME SHELL ]
Name
Size
Permission
Action
Artistic
5.97
KB
-rw-r--r--
Changes
2.23
KB
-rw-r--r--
README
3.91
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README
Net/LibIDN version 0.12 ======================= This module provides Perl bindings for GNU Libidn by Simon Josefsson (http://www.gnu.org/software/libidn/) in way that was heavily inspired by PHP bindings for the same library done by Turbo Fredriksson (http://php-idn.bayour.com/). INSTALLATION To install this module type the following: perl Makefile.PL [--with-libidn=<LIBPATH> --with-libidn-inc=<INCPATH> --disable-tld] make make test make install Installing under Cygwin: Sergei Koladka reports that the first make line above needs to be replaced by make LD_RUN_PATH="/usr/lib" LDLOADLIBS="/usr/lib/libidn.a \/usr/lib/libiconv.dll.a" assuming that Libidn was compiled with --prefix=/usr. You also will need to remove the >>die "This module requires GNU Libidn..."<<-line and manually set $libidn either to 2 or 1 depending on whether you have/want to use TLD checking support. DEPENDENCIES This module requires these other modules and libraries: GNU Libidn >=0.5.0 Linux hint: If Makefile.PL says that it cannot find GNU Libidn, even though you compiled/installed it, consider adding the location of the Libidn .so files to /etc/ld.so.conf. Also, take a look at the --with-libidn and --with-libidn-inc options. COPYRIGHT AND LICENCE Perl Module Net::LibIDN Copyright 2003-2009, Thomas Jacob, Internet24.de All rights reserved This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version, or b) the "Artistic License" which comes with this Kit. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public License or the Artistic License for more details. You should have received a copy of the Artistic License with this Kit, in the file named "Artistic". If not, I'll be glad to provide one. You should also have received a copy of the GNU General Public License along with this program in the file named "Copying". If not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA or visit their web page on the internet at http://www.gnu.org/copyleft/gpl.html. For those of you that choose to use the GNU General Public License, my interpretation of the GNU General Public License is that no Perl script falls under the terms of the GPL unless you explicitly put said script under the terms of the GPL yourself. Furthermore, any object code linked with perl does not automatically fall under the terms of the GPL, provided such object code only adds definitions of subroutines and variables, and does not otherwise impair the resulting interpreter from executing any standard Perl script. I consider linking in C subroutines in this manner to be the moral equivalent of defining subroutines in the Perl language itself. You may sell such an object file as proprietary provided that you provide or offer to provide the Perl source, as specified by the GNU General Public License. (This is merely an alternate way of specifying input to the program.) You may also sell a binary produced by the dumping of a running Perl script that belongs to you, provided that you provide or offer to provide the Perl source as specified by the GPL. (The fact that a Perl interpreter and your code are in the same binary file is, in this case, a form of mere aggregation.) This is my interpretation of the GPL. If you still have concerns or difficulties understanding my intent, feel free to contact me. Of course, the Artistic License spells all this out for your protection, so you may prefer to use that.
Close