Sponsored Content
The Lounge What is on Your Mind? Business origins - MalWareBytes - interesting read Post 303037136 by Neo on Wednesday 24th of July 2019 12:25:20 PM
Old 07-24-2019
Yeah, so as a long time cyber security person, I have never been impressed with companies like MalwareBytes who profit off the insecurity of Windows.

I'm not accusing any company of wrong doings, but there have been many scenarios in circles of cyber security professionals where antivirus companies conspire (or work) with malware creators to have malware released into the wild and for "an antivirus company" to already have an antiviral update(s) ready.

The entire ecosystem is broken; so personally, I am not impressed with the MalwareBytes story. I do not trust any of these companies, since they are not accountable and transparent to the public.

The real "success story" would be for governments or regulators to mandate that these software companies secure their products and be responsible for consumer losses and damages, or to otherwise regulate these greedy high tech companies who are only concerned with quarterly profit reports to their stockholders. Ditto for the new breed of information brokers like FB.

The entire cybersecurity industry is a "self-licking ice cream cone", where the more malware there is, the more money anti-malware companies make. It's really dystopian.

Soon (not sure the exact time), it will be the same in AI. There will be an entire industry built around securing us from AI, hackers attacking AI, AI gone bad, etc. It's really a dystopian future where tech creates more software which needs "protectors" to protect us from the harm it will do. Meanwhile, the huge tech giants get richer, the land costs rise in high tech areas, etc.

It's corporate greed out of control, really.
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Some interesting questions

Hello All, I have some questions; 1) process1 | process2, A)now if I kill process2 what happens to process1? B) if I kill process1 what happens to process2? 2) Why kill -9 is a strong kill? If possible I would like to know what happens internally. 3) What a pipe actually do, in... (3 Replies)
Discussion started by: willhunter
3 Replies

2. Shell Programming and Scripting

interesting problem

Hi, I am new in this forum and I am glad to be a part of it. I have a problem that has two parts: 1/ extract just the timestamp from a filename: for example, I have a file called 'sales20080226144525.txt' and I want to extract just the '20080226144525' part out of it. 2/ Now, take that... (5 Replies)
Discussion started by: ChicagoBlues
5 Replies

3. Red Hat

Cron entry for every 10 mints on business day business hour

Could you “crontab” it to run every 10 minutes on work days (Mo - Fr) between 08:00 and 18:00 i know to run every 10 mints but can any one guide me how to achieve the above one (2 Replies)
Discussion started by: venikathir
2 Replies
Business::PayPal::API::MassPay(3pm)			User Contributed Perl Documentation		       Business::PayPal::API::MassPay(3pm)

NAME
Business::PayPal::API::MassPay - PayPal MassPay API SYNOPSIS
use Business::PayPal::API::MassPay; ## see Business::PayPal::API documentation for parameters my $pp = new Business::PayPal::API::MassPay ( ... ); my %response = $pp->MassPay( EmailSubject => "Here's your moola", MassPayItems => [ { ReceiverEmail => 'joe@somewhere.tld', Amount => '95.44', Note => 'Thanks for your stuff!' }, { ReceiverEmail => 'bob@elsewhere.tld', Amount => '15.31', Note => 'We owe you one' }, ] ); ); DESCRIPTION
Business::PayPal::API::MassPay implements PayPal's Mass Pay API using SOAP::Lite to make direct API calls to PayPal's SOAP API server. It also implements support for testing via PayPal's sandbox. Please see Business::PayPal::API for details on using the PayPal sandbox. MassPay Implements PayPal's Mass Pay API call. Supported parameters include: EmailSubject MassPayItems The MassPayItem parameter is a list reference of hashrefs, each containing the following fields: ReceiverEmail Amount UniqueId Note as described in the PayPal "Web Services API Reference" document. Returns a hash containing the generic response structure (as per the PayPal Web Services API). Example: my %resp = $pp->MassPay( EmailSubject => "This is the subject", MassPayItems => [ { ReceiverEmail => 'joe@test.tld', Amount => '24.00', UniqueId => "123456", Note => "Enjoy the money. Don't spend it all in one place." } ] ); unless( $resp{Ack} !~ /Success/ ) { die "Failed: " . $resp{Errors}[0]{LongMessage} . " "; } ERROR HANDLING See the ERROR HANDLING section of Business::PayPal::API for information on handling errors. EXPORT
None by default. SEE ALSO
<https://developer.paypal.com/en_US/pdf/PP_APIReference.pdf> AUTHOR
Scot Wiersdorf <scott@perlcode.org> COPYRIGHT AND LICENSE
Copyright (C) 2007 by Scott Wiersdorf This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.5 or, at your option, any later version of Perl 5 you may have available. perl v5.14.2 2009-12-07 Business::PayPal::API::MassPay(3pm)
All times are GMT -4. The time now is 04:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy