ActivePerl discussion

Perl and ActivePerl usage questions; Perl practices and programming questions; Perl questions that don't fit other categories

Perl CVE-2013-1667 Input Rehashing Denial of Service Vulnerability

Does this apply to active perl I know that it applies to the more generic version of Perl 5.14.x. Will ActiveState release a product specific patch to address this issue?

Suggestions on migrating from Windows Server 2003

I'm running Perl on a Windows 2003 Server. The time has come to finally move to a more current version of Windows and I was wondering if you guys have any suggestions or warnings. Am I going to have any problems with Windows Server 12 or 16?

Though I've used Perl for 20 years, I've only installed/reinstalled it or any packages like GD or some .pdf scripts a couple of times, so from that angle I'm a beginner.

We also use MDaemon for the email part of what we do.

Thanks for any help,


pack for 0x0A creates the invalid value

I created the following perl source'

my $val = 10;
open(OUT, ">", "out.bin") || die "cannot open file\n";
print OUT pack("C", $val);

I expect the content of out.bin is 0x0A, but it is 0x0A0D.
"0x0D" is added after 0x0A.
I also get 0x000A0D in case of pack("S", $val), and 0x0000000A0D in case of pack("V", $val).

I can get the correct result in case of $val=9 or $val=11.

Is this a bug for ActivePerl?
Tested with 5.26.1 for x64, 5.26.0 for x86, and 5.24.2 for x86.


Perl Saxon


I am looking for a solution to use Saxon in Perl
we need to filter a lot of XML files with XSLT but the customer does not have software for that.
Want to know if it is possible with Perl!

thnx for your advice

Problem with umlauts ÄÖÜ and UTF8

use utf8;
use diagnostics;

binmode(STDOUT, ":utf8");
binmode(STDERR, ":utf8");

print "ÄÖÜ\n";

print "Perl Version: $]\n";
print "Perl executable: $^X\n";

The result is

Perl Version: 5.024003
Perl executable: C:\Perl64\bin\perl.exe

It works well with Cygwin, but not with Active Perl on Windows 10.

What is wrong there?
Why does it not work?

Thank you!

Is Perl dying?

I've been searching through the Internet for an active Perl forum and for the most part am very discouraged by the fact that there are no answers given.

This forum for instance: I hardly see any activities for weeks on end. And over at Perl Guru, same.

Is Perl a dying language?

sad :(


Has anyone gotten DBD::MySQL to work with SSL in ActiveState Perl? I have the following code:

use warnings;
use strict;
use DBI;

my $dbname = "database";
my $host = "";
my $port = "3306";
my $user = "username";
my $pass = "password";
my $cakey = "ca-cert.pem";
my $clientkey = "win-key.pem.nopass";
my $clientcert = "win-cert.pem";

my $dsn = DBI->connect("dbi:mysql:dbname=$dbname;host=$host;port=$port;mysql_ssl=1;mysql_ssl_ca_file=$cakey;mysql_ssl_client_key=$clientkey;mysql_ssl_client_cert=$clientcert","$user","$pass",

Perl 2017 CVE's: CVE-2017-12883, CVE-2017-12837, CVE-2017-12814


We were asked by customers to upgrade Perl to version with fix for following vulnerabilities.

1 CVE-2017-12883 Buffer overflow in the S_grok_bslash_N function in regcomp.c in Perl 5 before 5.24.3-RC1 and 5.26.x before 5.26.1-RC1 allows remote attackers to disclose sensitive information or cause a denial of service (application crash) via a crafted regular expression with an invalid '\N{U+...}' escape.

Perl command line interpreter has stopped working


Iam new to Perl programming, and just started grasping the concept of a scripting language. here is my problem i am using the win32::ODBC Perl Package to read a table data from sql database. but when the code reaches a specific line the perl crashes with the popup saying "Perl command line interpreter has stopped working". and the same set of code is used in many other places to retrieve data from db successfully.

Error log from Event Viewer

Faulting application name: perl.exe, version:, time stamp: 0x599f96cf

DBD-mysql Problem

This is a 'shot-in-the-dark' question but I'm at a loss otherwise.

I've been developing a Perl script that connects to a MySQL DB. For the past couple of days, everything has been swell. This morning, I ran another test and when I tried to connect to my DB, I got a message in Komodo saying 'No such file or directory'.

Since I don't believe in malicious fairies or gremlins, I must have accidentally deleted or changed something in the past 24 hours. I've tried reinstalling the package, etc. but nothing seems to work.