Parrot 4.2 beta testers program

palinuro · August 24, 2018, 4:45pm

Parrot 4.2 is almost ready and we 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 https://community.parrotsec.org/t/parrot-4-2-development-discussions

These are the instructions for Parrot 4.2 beta testers:

download zone
if you want to become a Parrot beta tester, you have to download the latest beta images from Index of /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).

This report have to be posted as a comment to this topic.

In case of confidential reports, we also take in consideration all the reports sent to palinuro AT parrotsec DOT org or team AT parrotsec DOT 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 we 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 us to keep this topic as clean as possible. Discussions have their dedicated topic https://community.parrotsec.org/t/parrot-4-2-development-discussions

Tests done on older versions of the system make no sense for us, 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

palinuro · August 27, 2018, 8:36pm

That’s my little report

ABSTRACT

Parrot 4.2 does not involve very important upgrades like some previous versions.
This release is more aimed on including new debian updates and integrate some minor fixes and security patches on top of Parrot 4.1.

What worked out of the box

Almost everything worked out of the box at first run on several machines with different hardware.
Applications started smoothly and the sandbox worked for almost every program as it is supposed to work.
Pentest tools probably need deeper tests before the final release (and i will do them), but all the tests done against metasploitable2 and other vulnhub machines were positive as expected.

What needs to be fixed

MUST:

keepassxc sandbox profile
fix armitage unrecognized RHOSTS var
replace firefox-esr with firefox

WISH:

update metasploit-framework
try to patch some tools that are broken upstream (hashcat mostly)

palinuro · August 27, 2018, 8:37pm

few days remaining before the final release

Serverket · August 28, 2018, 2:02am

My Report so far…

ABSTRACT
Almost all updates integrated perfectly (I made a clean install so I got 4.2 from 4.1 (for the sake of testing), I got a graphical issue related to Compton which was fixed with the latest version, I used Marco meanwhile which happened to be as good as Compton. There was a gimp-gmic package issue (it was broken for a while), I relate this to the transition of some dependencies it uses. Vega still has an issue which can be fixed by using update-alternatives to switch the Java version needed.

What Worked Out of the Box
Everything but Vega. Most Used pentesting Tools run over JRE, the latest versions of these programs suggest that they are not fully tested with the current Java version but so far I didn’t have any problem with their features.

What Needs to be Fixed
MUST:
Vega (for the sake of the “out of the box” concept)

WISH:
Keeping the changing-MAC support in Anonsurf
Ribbon support over LibreOffice (Notebookbar)
TheFatRat as preinstalled tool

dmknght · August 28, 2018, 2:07am

Hi! Is there any news about Parrot default theme? As i remember, the “invisible cursor” while renaming file / folder is still happening and I think border color should be enabled for easier view.
p/s: intel released opencl on github and it is much better than beignet. I hope Parrot will include this driver soon. https://github.com/intel/compute-runtime

palinuro · August 28, 2018, 1:08pm

remember that this topic is not the proper place where to ask such questions, please use the development discussions thread instead
https://community.parrotsec.org/t/parrot-4-2-development-discussions

anyways parrot 4.2 includes a new theme where the invisible cursor bug seems to be disappeared as the edit cursor has a higher contrast

of course themes settings are included in the home directory of the users which is not updated with system upgrades to not overwrite user customization, and people with parrot 4.1 or earlier have to manually change the theme

palinuro · August 30, 2018, 3:26pm

new updated (and mostly fixed) beta images are now available for x86 32bit too

palinuro · August 31, 2018, 2:07am

Parrot 4.2 will be released on Monday

anguson · August 31, 2018, 5:22pm

Hey pallnuro, thank you so much for all the effort you put into this project. I got into pentesting a year ago running Kali with the seperate user as my main OS on my Dell Venue Pro 7140 laptop, but this as you can imagine can cause a lot of troubles for.eg recent KDE image of Kali DE is broken even if you add a new user, so ParrotOS is perfect for people like us, who want to do their workload on one machine.

I am currently on ParrotOS 4.2 Beta-testing and was wondering if I can keep my current OS and if yes, how can I update it to the stable release ? I am really looking forawrd to it.

Only one thing I would like to fix, and I am not sure if you can help, is to get the system to recognize my soundcard broadwell-rt286. It used to work well with the previous releases of ParrotOS but after the update “sudo apt full-upgrade” it is not recognized. I am not sure if that is the right place to post my findings, if not feel free to direct me to the correct section.

Report and observations:
Sound card works with all recent versions and kernels of Kali Linux and ParrotOS.

Release:

└──╼ $uname -a
Linux parrot 4.17.0-parrot17-amd64 #1 SMP Parrot 4.17.17-1parrot17 (2018-08-27) x86_64 GNU/Linux

Dmesg output:

lspci:

Sound preferences:

Alsamixer soundcards:

If you need any more details please do let me know I will be happy to help. I would love to get it to work as I have noticed others had filled similar reports, I have tried suggestions on this forum but to no avail.

I have read that it might be kernel related problem, is there a way to downgrade it ?

anguson · August 31, 2018, 8:32pm

I proudly would like to announce for anyone having the same troubles as me that a solution lies in getting debian sound firmware as the one updated by ParrotOS seems to break it, at least in my case. Once I installed firmware from:

https://packages.debian.org/search?keywords=firmware-intel-sound

I magically got the sound working!

Also worth noting that during upgrade you might get this:

The following packages will be DOWNGRADED:
firmware-intel-sound

to fix it, run:
sudo apt-mark hold firmware-intel-sound

palinuro · September 1, 2018, 2:00am

if you installed the iso image ending in -beta2 thenvi suggest you to re-install the system, otherwise if you installed the iso ending with -2018.08.30, then you can keep it, but make sure to disable some unwanted services running in background, like redsocks, redis, ooenvas-manager, openvas-scanner and samba/smbd

palinuro · September 1, 2018, 2:01am

please create a dedicated topic for your sound issue amd give yourself the answer. this would help other people with your issue to easily find the topic with your solution

dmknght · September 1, 2018, 4:41am

I’ve tested Parrot 4.2 beta 2018.8.30 from Singapore mirror. New ARK Theme is good but cursor (when rename file /folder) is still too hard to see. And it is using firefox-esr by default (I think it should be firefox quatumn). Not sure about firefox-esr but cursor theme should be fixed soon.
p/s: i modified Parrot theme before but i don’t remember that line. I hope i can make a pull request soon before Parrot release

palinuro · September 1, 2018, 1:05pm

please make a pull request for the cursor

anyways firefox is now the default browser in the final 4.2 images, feel free to download them and help us seed the torrent

dmknght · September 1, 2018, 2:07pm

Hey i’ve installed fresh Parrot 4.2 iso to my system (replace old one) and i am having super delay after type username and password (lightdm). I don’t know what is happening. Live mode didn’t have this problem. systemd-analysis didn’t show me any useful thing about this bug. I am trying to track this bug. Can you help me about commands to track it?

dmknght · September 1, 2018, 2:11pm

my /var/log/lightdm/lightdm.log

[+0.02s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.02s] DEBUG: Starting Light Display Manager 1.18.3, UID=0 PID=823
[+0.02s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.02s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.02s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.02s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registered seat module xlocal
[+0.02s] DEBUG: Registered seat module xremote
[+0.02s] DEBUG: Registered seat module unity
[+0.04s] DEBUG: Monitoring logind for seats
[+0.04s] DEBUG: New seat added from logind: seat0
[+0.04s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.04s] DEBUG: Seat seat0: Starting
[+0.04s] DEBUG: Seat seat0: Creating greeter session
[+0.22s] DEBUG: Seat seat0: Creating display server of type x
[+0.23s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than the configured minimum of 7 so not replacing it
[+0.23s] DEBUG: Quitting Plymouth
[+0.30s] DEBUG: Using VT 7
[+0.31s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.31s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.31s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.31s] DEBUG: DisplayServer x-0: Launching X Server
[+0.31s] DEBUG: Launching process 833: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.31s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.31s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.31s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.34s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.34s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+3.88s] DEBUG: Got signal 10 from process 833
[+3.88s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+3.88s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+3.91s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+3.91s] DEBUG: Session pid=865: Started with service 'lightdm-greeter', username 'lightdm'
[+4.03s] DEBUG: Session pid=865: Authentication complete with return value 0: Success
[+4.03s] DEBUG: Seat seat0: Session authenticated, running command
[+4.03s] DEBUG: Session pid=865: Running command /usr/sbin/lightdm-gtk-greeter
[+4.03s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+4.03s] DEBUG: Session pid=865: Logging to /var/log/lightdm/seat0-greeter.log
[+4.57s] DEBUG: Activating VT 7
[+4.57s] DEBUG: Activating login1 session c1
[+4.57s] DEBUG: Seat seat0 changes active session to c1
[+4.57s] DEBUG: Session c1 is already active
[+6.24s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+9.94s] DEBUG: Greeter start authentication for dmknght
[+9.94s] DEBUG: Session pid=914: Started with service 'lightdm', username 'dmknght'
[+10.01s] DEBUG: Session pid=914: Got 1 message(s) from PAM
[+10.01s] DEBUG: Prompt greeter with 1 message(s)
[+14.42s] DEBUG: Continue authentication
[+14.43s] DEBUG: Session pid=914: Authentication complete with return value 0: Success
[+14.43s] DEBUG: Authenticate result for user dmknght: Success
[+14.43s] DEBUG: User dmknght authorized
[+14.44s] DEBUG: Greeter sets language en_US.utf8
[+14.50s] DEBUG: Greeter requests session lightdm-xsession
[+14.50s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+14.50s] DEBUG: Session pid=865: Sending SIGTERM
[+14.57s] DEBUG: Greeter closed communication channel
[+14.57s] DEBUG: Session pid=865: Exited with return value 0
[+14.57s] DEBUG: Seat seat0: Session stopped
[+14.57s] DEBUG: Seat seat0: Greeter stopped, running session
[+14.57s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+14.58s] DEBUG: Session pid=914: Running command /etc/X11/Xsession default
[+14.58s] DEBUG: Creating shared data directory /var/lib/lightdm/data/dmknght
[+14.58s] DEBUG: Session pid=914: Logging to .xsession-errors
[+198.80s] DEBUG: Activating VT 7
[+198.80s] DEBUG: Activating login1 session 2
[+198.80s] DEBUG: Seat seat0 changes active session to 
[+198.80s] DEBUG: Seat seat0 changes active session to 2
[+198.80s] DEBUG: Session 2 is already active

dmknght · September 1, 2018, 2:12pm

my ~/.xsession-errors

Xsession: X session started for dmknght at Sat Sep  1 20:57:54 +07 2018
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/dmknght/.Xauthority
localuser:dmknght being added to access control list
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=dmknght
dbus-update-activation-environment: setting LANGUAGE=en_US:en
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/dmknght
dbus-update-activation-environment: setting QT4_IM_MODULE=fcitx
dbus-update-activation-environment: setting DESKTOP_SESSION=lightdm-xsession
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LOGNAME=dmknght
dbus-update-activation-environment: setting GTK_IM_MODULE=fcitx
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting GDM_LANG=en_US.utf8
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lightdm-xsession
dbus-update-activation-environment: setting XAUTHORITY=/home/dmknght/.Xauthority
dbus-update-activation-environment: setting XMODIFIERS=@im=fcitx
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/dmknght
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=lightdm-xsession
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting QT_IM_MODULE=fcitx
dbus-update-activation-environment: setting PWD=/home/dmknght
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/mate:/usr/local/share/:/usr/share/
dbus-update-activation-environment: setting CLUTTER_IM_MODULE=xim
x-session-manager[1098]: WARNING: Unable to find provider '' of required component 'dock'
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
cat: '~/.keymap-selected': No such file or directory
Initializing caja-xattr-tags extension
Initializing caja-image-converter extension
Initializing caja-open-terminal extension

(mate-volume-control-applet:1361): Gdk-CRITICAL **: 20:58:25.142: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(blueman-applet:1351): Gdk-CRITICAL **: 20:58:25.145: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

(mate-panel:1252): GLib-GObject-CRITICAL **: 20:58:25.178: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(mate-panel:1252): GLib-GObject-CRITICAL **: 20:58:25.179: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(mate-panel:1252): GLib-GObject-CRITICAL **: 20:58:25.180: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(mate-panel:1252): GLib-GObject-CRITICAL **: 20:58:25.639: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(mate-panel:1252): GLib-GObject-CRITICAL **: 20:58:25.889: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Reading profile /etc/firejail/firefox.profile
Reading profile /etc/firejail/firefox-common.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-interpreters.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 11029, child pid 11032
Warning: skipping pango for private /etc
Warning: skipping asound.conf for private /etc
Warning: skipping pki for private /etc
Warning: skipping crypto-policies for private /etc
Warning fcopy: skipping /etc/alternatives/fakeroot.sv.1.gz, cannot find inode
Warning fcopy: skipping /etc/alternatives/wine.pl.1.gz, cannot find inode
Warning fcopy: skipping /etc/alternatives/faked.sv.1.gz, cannot find inode
Private /etc installed in 1190.49 ms
Warning: An abstract unix socket for session D-BUS might still be available. Use --net or remove unix from --protocol set.
Post-exec seccomp protector enabled
Warning fseccomp: syscall "ni_syscall" not available on this platform
Warning fseccomp: syscall "umount" not available on this platform
Seccomp list in: @clock,@cpu-emulation,@debug,@module,@obsolete,@raw-io,@reboot,@resources,@swap,acct,add_key,bpf,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,ni_syscall,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount,umount2,userfaultfd,vhangup,vmsplice, check list: @default-keep, prelist: adjtimex,clock_adjtime,clock_settime,settimeofday,modify_ldt,lookup_dcookie,perf_event_open,process_vm_writev,delete_module,finit_module,init_module,_sysctl,afs_syscall,create_module,get_kernel_syms,getpmsg,putpmsg,query_module,security,sysfs,tuxcall,uselib,ustat,vserver,ioperm,iopl,kexec_load,kexec_file_load,reboot,set_mempolicy,migrate_pages,move_pages,mbind,swapon,swapoff,acct,add_key,bpf,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount2,userfaultfd,vhangup,vmsplice,
Child process initialized in 1415.90 ms
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information

dmknght · September 1, 2018, 2:34pm

output of $LIBGL_DEBUG=verbose glxinfo | grep error
Looks like Parrot 4.2 is having serious Mesa bug after install

libGL: Can't open configuration file /home/dmknght/.drirc: No such file or directory.
libGL: pci id for fd 4: 8086:0166, driver i965
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
libGL: Can't open configuration file /home/dmknght/.drirc: No such file or directory.
libGL: Can't open configuration file /home/dmknght/.drirc: No such file or directory.
libGL: Using DRI3 for screen 0
libGL: Can't open configuration file /home/dmknght/.drirc: No such file or directory.
    GLX_ARB_create_context, GLX_ARB_create_context_no_error, 
libGL: Can't open configuration file /home/dmknght/.drirc: No such file or directory.
    GL_KHR_context_flush_control, GL_KHR_debug, GL_KHR_no_error, 
libGL: Can't open configuration file /home/dmknght/.drirc: No such file or directory.
    GL_KHR_context_flush_control, GL_KHR_debug, GL_KHR_no_error, 
    GL_KHR_context_flush_control, GL_KHR_debug, GL_KHR_no_error,

dmknght · September 1, 2018, 4:05pm

After reboot and run this command$systemd-analyze blame
found this
3min 30.171s phpsessionclean.service
And found this file
$cat /lib/systemd/system/phpsessionclean.service

[Unit]
Description=Clean php session files

[Service]
Type=oneshot
ExecStart=/usr/lib/php/sessionclean
ProtectHome=true
ProtectSystem=true
PrivateTmp=true

I’m gonna remove this and hope it will be okay

grix · September 2, 2018, 2:53am

after update to Parrot 4.2 beta. so far

Desktop takes a long time to initialize after Booting than 4.0