Parrot Security OS 4.2 Beta Released

Read the Vietnamese version

ParrotSec 4.2 Beta for testers program
   Parrot 4.2 is almost ready and ParrotSec Dev Team want you to test it and report us what works and what needs to be fixed before the final release.

   This is not the proper place where to post your ideas and tips. Use the Parrot 4.2 development discussions topic to discuss opinions and ideas: Parrot 4.2 development discussions - Development - Parrot Community

   These are the instructions for Parrot Security OS 4.2 beta testers:
    * If you want to become a Parrot Beta tester, you have to download the latest beta images from https://archive.parrotsec.org/parrot/iso/testing/

    * Things that need to be tested: Use the system in all the possible conditions both in live mode and installed on virtual machines and real hardware, both in standard and uncommon configurations, but please don’t report errors for configurations that are not meant to work on Debian.

    * How to report bugs: We expect our beta testers to write a final report that collects the result of all their tests, and to report both working and broken things, and eventually suggest how to solve issues (if a solution is known by the tester).

    * The report have to be posted as a comment to this topic.

   In case of confidential reports, ParrotSec Dev Team also take in consideration all the reports sent to palinuro@parrotsec.org or team@parrotsec.org, but we strongly prefer comments to this topic.

   What a beta tester is not supposed to do?
      Parrot is not a software, it is a whole operating system. An operating system, by definition, is a collection of many many system components and completely independent programs that ParotSec Team don’t develop.

      Reports released after the final stable release may not be taken in consideration, but if you spot something important, we may decide to schedule a new emergency release that addresses critical bugs, but we consider these cases as exceptions, and latecomers are usually just ignored

      If a parrot bug is caused by a bug in a specific parrot software, that bug should be reported to that program developers, and not to the Parrot Developers.

      Brief comments are not full reports. Don’t comment to this topic if you don’t have a complete report. So help ParrotSec Team to keep this topic as clean as possible. Discussions have their dedicated topic: Parrot 4.2 development discussions - Development - Parrot Community

      Tests done on older versions of the system make no sense for ParotSec Team, as the purpose of this beta testing program is to spot issues on the ISO files for Parrot 4.2 that the release team proposes during the Beta testing phase.

ParrotSec 4.2 development discussions
   Parrot 4.2 is ready and the first beta images are available for Beta testers
   Let’s start this topic to collect the latest suggestions for this new release.

   RULES:
    * This topic is not the proper place where to report bugs, and the beta testers have their own topic where to report parrot 4.2 bugs.
    * We are not going to implement suggestions that involve drastic system changes in any way, but we are open to listen to your opinions and ideas.

    Parrot Security OS 4.2 beta testers program: https://community.parrotsec.org/t/parrot-4-2-beta-testers-program/

And have something to say about GitHackTools or Parrot Security OS 4.2 Beta? Comment below or share this post from GitHackTools Facebook, GitHackTools Twitter and GitHackTools Google Plus.