Business origins - MalWareBytes - interesting read Post: 303037136

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

07-24-2019

Administrator

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.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

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...

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...

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

LEARN ABOUT DEBIAN

business::paypal::api::reauthorizationrequest

Business::PayPal::API::ReauthorizationRequest(3pm)	User Contributed Perl Documentation	Business::PayPal::API::ReauthorizationRequest(3pm)

NAME

       Business::PayPal::API::ReauthorizationRequest - PayPal ReauthorizationRequest API

SYNOPSIS

	 use Business::PayPal::API::ReauthorizationRequest;

	 ## see Business::PayPal::API documentation for parameters
	 my $pp = new Business::PayPal::API::ReauthorizationRequest ( ... );

	 my %response = $pp->DoReauthorizationRequest (
						AuthorizationID => $transid,
						Amount		=> $amount,
						CurrencyID	=> $currencyID
						);

DESCRIPTION

       Business::PayPal::API::ReauthorizationRequest implements PayPal's DoReauthorizationRequest 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.

   DoReauthorizationRequest
       Implements PayPal's DoReauthorizationRequest API call. Supported parameters include:

	 AuthorizationID
	 Amount
	 currencyID (defaults to 'USD' if not supplied)

       as described in the PayPal "Web Services API Reference" document. The default currencyID setting is 'USD' if not otherwise specified. The
       DoReauthorization is not allowed before the three day grace period set for the original AuthorizeRequest.

       Returns a hash containing the results of the transaction.

       Example:

	 my %resp = $pp->DoReauthorizationRequest (
					    AuthorizationID => $trans_id,
					    Amount	    => '15.00',
					    CurrencyID	    => 'USD'
					     );

	 unless( $resp{Ack} !~ /Success/ ) {
	     for my $error ( @{$response{Errors}} ) {
		 warn "Error: " . $error->{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

       Danny Hembree <danny@dynamical.org>

COPYRIGHT AND LICENSE

       Copyright (C) 2006 by Danny Hembree

       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::ReauthorizationRequest(3pm)