I'm working on adding anti-hammering code to SurfShop to be able to
temporarily ban visitors if they enter certain "keywords" into the query
string, or if they repeatedly hammer the cart. I've also set it up to be able
to permanently block foreign IP's of t
I keep getting emails from Authorize.net about their upcoming
disablement of TLS 1.0 and TLS 1.1 and I need to know if that has anything to
do with Perl or not. I don't have any code in SurfShop that references either
SSL or TLS, so maybe that's handled by Perl itself or a
> On Jan 25, 2018, at 10:43 AM, Darryl Philip Baker
> wrote:
>
> If you do not know TLS 1.0 and TLS 1.1 have a vulnerability in the design of
> the protocol and they are being deprecated. Currently only TLS 1.2 now and
> TLS 1.3 when finalized are considered safe. TLS 1.2 was defined in August
> On Jan 24, 2018, at 2:37 AM, Brandon Parncutt
> wrote:
>
> fail2ban would surely be the best bet here.
Thanks, Brandon. I'll look into that if I can't find a pure Perl
solution. It needs to be easily distributed with an OSS script.
Frank
> On Jan 25, 2018, at 11:37 AM, David Precious wrote:
>
> then that uses LWP::UserAgent under the hood for the communication with
> authorize.net; it doesn't set any SSL/TLS-specific options when calling
> LWP::UserAgent, unless you're causing it to yourself.
>
> LWP::UserAgent will use LWP::Pro
Basic time question here. Looking at sites such as
http://perldoc.perl.org/functions/time.html, I'm not seeing what the time()
function is based on. Does it return the time of the server, or UTC? Is it
affected by any timezone setting on the server or in a script?
I tested
> On Jan 29, 2018, at 12:18 PM, Octavian Rasnita wrote:
>
> from: perldoc -f time
>
> timeReturns the number of non-leap seconds since whatever time the
> system considers to be the epoch, suitable for feeding to
> "gmtime" and "localtime". On most systems the epoch is
