Author Topic: MBAE 1.10.x "Perpetual Beta"  (Read 1862 times)

0 Members and 1 Guest are viewing this topic.

Offline ky331

  • LzD Friends
  • Hero Member
  • *****
  • Posts: 620
    • View Profile
MBAE 1.10.x "Perpetual Beta"
« on: July 23, 2017, 11:20:13 AM »
MBAE (Anti-EXPLOIT), which is now in a "perpetual beta" phase, has released version 1.10.1.24   The main difference/feature:   what used to be premium features are now available to ALL/free users!

The following information was copied/pasted from https://forums.malwarebytes.com/topic/205225-mbae-110-latest-standalone-beta/


New Features:

    Added Dynamic Hooking Feature to manage conflicts
    Opened up Premium shields to Free users as part of MBAE Beta
    Opened up addition of custom shields feature to Free users as part of MBAE Beta


 Fixes:

    Fixed dll uninjection issues resulting in ghost process
    Fixed dll uninjection issues with chrome extensions
    Fixed false positive with FLTLDR.exe
    Fixed false positive with QTTabBar plugin in Opera


-----------------------------------------------------------------

It is anticipated that existing MBAE users will be automatically updated to 1.10 "soon".   For anyone wishing to try it out now, it can be downloaded from  https://malwarebytes.box.com/s/xhbp0e8xyj4iom093gdtwyervxva0zxh

(Remark: MBAM 3.x PREMIUM automatically includes the anti-exploit protection.)

Offline winchester73

  • Half a bubble off plumb
  • Administrator
  • Hero Member
  • *****
  • Posts: 7220
  • Liverpool FC - YNWA
    • View Profile
Re: MBAE 1.10.x "Perpetual Beta"
« Reply #1 on: July 23, 2017, 12:29:07 PM »
An important note to add ...

"Perpetual beta" is a term used to describe a product that is never fully finished ... it is released but remains in a permanent state of advanced open development and customer testing, adding new features (that may not be fully tested) as the software vendor deems necessary.  As such, users are essentially de facto testers.

If you choose to beta test, you accept the inherent risks associated with using pre-release software. Beta testers should use the software at their own risk.  This means you should back up your computer to ensure that you can restore it prior to the beta installation.  Perpetual beta software is NOT recommended for mission critical machines.
Speak softly, but carry a big Winchester ... Winchester Arms Collectors Association member

Offline Digerati

  • LzD Friends
  • Hero Member
  • *****
  • Posts: 1059
    • View Profile
Re: MBAE 1.10.x "Perpetual Beta"
« Reply #2 on: July 23, 2017, 02:25:48 PM »
Quote
"Perpetual beta" is a term used to describe a product that is never fully finished ... it is released but remains in a permanent state of advanced open development and customer testing, adding new features (that may not be fully tested) as the software vendor deems necessary.  As such, users are essentially de facto testers.
I used to be one of 5 or so hardware guys in a large software development company (Northrop Grumman IT - NGIT) with over 400 developers at my site alone. One of my "other hats" was that of an Alpha and Beta tester. That's where I first heard the term "perpetual beta". The "official" definition was as you described above.

However, the unofficial or real reason for the "perpetual" moniker, as explained to me by several developers who worked tech support on our help desk, was as a "cop-out" excuse to avoid blame and responsibility should the "beta" program break a customer's computer.  :( After all, people should know they should never run beta software on a production machine.  ::)

Fortunately, NGIT is a decent company and they eventually realized this practice might, at the very least, "give the appearance" of a deceptive practice - not "transparent", and as a way to shirk responsibility. Not cool! Especially since most of our clients were government departments and agencies, that is, taxpayer funded. So the practice was stopped - and rightfully so, IMO.

Our programs did, of course, remain in "perpetual beta" - that is, under constant development. But that was "in-house" only. When a beta version was determined to be stable, it was then RFD (released for deployment) as a final version or update - not subject to any cop-out excuses.  :)

Only clients who volunteered as beta testers, and who certified they understood the potential consequences of using beta software, got the beta versions. All other clients only received the stable RFD versions. IMO, that's how it should work.
 
Quote
Perpetual beta software is NOT recommended for mission critical machines.
Beta software in general, perpetual or not, is NOT recommended for mission critical systems.

Bill (AFE7Ret)
Freedom is NOT Free!
2007 - 2018