Making NFS mount appear in Nautilus bookmarks when using Google Chrome

Fresh install of Ubuntu 17.10 and my NFS shares would not appear in Nautilus when I tried to save anything by Google Chrome.
Fix was adding user to my fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#     

         
# / was on /dev/nvme0n1p3 during installation
UUID=b84c5842-*************/               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=E844-8B4E  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
192.168.1.*:/home/b-real/nas  /home/b-real/nas/ nfs user,auto 0 0

When you don’t want nothing to do with Facebook.

Then you block it. Can’t do it completely block it since other people are using it so it will ble locally:

sudo nano /etc/hosts

Paste this in. Reboot might be needed. You will need the IPv6 also.

#facebook
127.0.0.1 api.ak.facebook.com
127.0.0.1 api.connect.facebook.com
127.0.0.1 api.facebook.com
127.0.0.1 app.facebook.com
127.0.0.1 apps.facebook.com
127.0.0.1 ar-ar.facebook.com
127.0.0.1 badge.facebook.com
127.0.0.1 blog.facebook.com
127.0.0.1 connect.facebook.com
127.0.0.1 connect.facebook.net
127.0.0.1 de-de.facebook.com
127.0.0.1 developers.facebook.com
127.0.0.1 es-la.facebook.com
127.0.0.1 external.ak.fbcdn.net
127.0.0.1 facebook.com
127.0.0.1 facebook.de
127.0.0.1 facebook.fr
127.0.0.1 fb.me
127.0.0.1 fbcdn.net
127.0.0.1 fr-fr.facebook.com
127.0.0.1 hi-in.facebook.com
127.0.0.1 it-it.facebook.com
127.0.0.1 ja-jp.facebook.com
127.0.0.1 login.facebook.com
127.0.0.1 profile.ak.fbcdn.net
127.0.0.1 pt-br.facebook.com
127.0.0.1 ssl.connect.facebook.com
127.0.0.1 static.ak.connect.facebook.com
127.0.0.1 static.ak.fbcdn.net
127.0.0.1 www.facebook.com
127.0.0.1 www.facebook.de
127.0.0.1 www.facebook.fr
127.0.0.1 zh-cn.facebook.com

#Facebook IPv6
#fe80::1%lo0 localhost
::1 api.ak.facebook.com
::1 api.connect.facebook.com
::1 api.facebook.com
::1 app.facebook.com
::1 apps.facebook.com
::1 ar-ar.facebook.com
::1 badge.facebook.com
::1 blog.facebook.com
::1 connect.facebook.com
::1 connect.facebook.net
::1 de-de.facebook.com
::1 developers.facebook.com
::1 es-la.facebook.com
::1 external.ak.fbcdn.net
::1 facebook.com
::1 facebook.de
::1 facebook.fr
::1 fb.me
::1 fbcdn.net
::1 fr-fr.facebook.com
::1 hi-in.facebook.com
::1 it-it.facebook.com
::1 ja-jp.facebook.com
::1 login.facebook.com
::1 profile.ak.fbcdn.net
::1 pt-br.facebook.com
::1 ssl.connect.facebook.com
::1 static.ak.connect.facebook.com
::1 static.ak.fbcdn.net
::1 www.facebook.com
::1 www.facebook.de
::1 www.facebook.fr
::1 zh-cn.facebook.com

Google GPG Error Ubuntu

Problem

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: dl.google.com/linux/chrome/d… stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E

W: Failed to fetch dl.google.com/linux/chrome/d… The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E

W: Some index files failed to download. They have been ignored, or old ones used instead.

Fix

wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -

OpenSSL in Debian Unstable drops TLS 1.0/1.1 support (debian.org)

Kurt just uploaded a version of OpenSSL to unstable that disables
the TLS 1.0 and 1.1 protocol. This currently leaves TLS 1.2 as the
only supported SSL/TLS protocol version.

This will likely break certain things that for whatever reason
still don’t support TLS 1.2. I strongly suggest that if it’s not
supported that you add support for it, or get the other side to
add support for it.

OpenSSL made a release 5 years ago that supported TLS 1.2. The
current support of the server side seems to be around 90%. I hope
that by the time Buster releases the support for TLS 1.2 will be
high enough that I don’t need to enable them again.

https://lists.debian.org/debian-devel-announce/2017/08/msg00004.html

Fail0verflow demonstrate Linux and Steam running on Firmware 4.05

Marcan42 of Fail0verflow fame was at the CCC33 event this year, to explain how Fail0verflow exploited the PS4 hardware in order to run Linux on the PS4.

Marcan42 explained how the base of the hack consisted in a man-in-the-middle attack of the PCIE bus on the PS4, with the rest of the presentation focused on why several patches were required on the linux kernel for it to run on a PS4.
https://www.youtube.com/watch?v=6hxEUm-pHUE&feature=youtu.be
Towards the end of the demonstration, Marcan ran Steam on the PS4 to confirm 3D Hardware acceleration was working.

Asked if Fail0verflow planned to release an exploit for a firmware higher than 1.76 (PS4s running firmware 1.76, the only publicly exploited firmware, can be found but are expensive), Marcan answered that his whole presentation was running on a 4.05 PS4, but also confirmed that Fail0verflow do not intend to release any exploit for the PS4, as their focus is 100% on the Linux port (for which all of their work is already available on github) and they want to avoid typical scene drama.

Download Fail0verflow’s Linux port for the PS4

Fail0verflow’s work on the PS4 can be downloaded on Github