Update status of document about permissions

After applying several updates to the permissions document the status
needs to be updated to reflect reality. To do so add some small tweaks.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

content/concepts/permissions.md

@@ -10,10 +10,8 @@ aliases = [
 ]
 outputs = [ "html", "pdf-in",]
 date = "2017-02-22"
-lastmod = "2021-11-10"
+lastmod = "2022-01-07"
 
-status = "Requires Update"
-statusDescription = "Describes use of Mildenhall and other legacy frameworks which have been dropped in `v2022dev2`. Reviews now quite out of date version of Android, suspect things have changed in Android. Targets automotive use-cases specifically. Mentions wiki which no longer exists."
 +++
 
 This document extends the higher-level [Applications] and [Security]
@@ -164,7 +162,7 @@ obtained by sending messages to the [XDG portals].
 
 Many intermediate levels of Internet access are possible, but for the
 purposes of this document we do not consider them. See the
-[Egress filtering design notes on the Apertis wiki][Egress filtering]
+[Egress filtering design notes on the Apertis website][Egress filtering]
 for initial work on finer-grained control.
 
 #### Security implications
@@ -878,7 +876,7 @@ iOS calendaring.
 ### Inter-app communication interfaces
 
 Inter-app communication has not been designed in detail, but the
-draft design on the Apertis wiki suggests that it might be modelled
+draft design on the Apertis website suggests that it might be modelled
 in terms of [interface discovery], with app-bundles able to implement
 "public interfaces" that are made visible to other app-bundles.
 The draft design has some discussion of how [restricting interface providers]
@@ -947,25 +945,11 @@ the Newport download manager), or developed for a particular vendor.
 Platform services should continue to contain their own AppArmor profiles,
 polkit rules and other security metadata.
 
-### Driving cameras
-
-Some vehicles have external cameras for purposes such as facilitating
-reversing, watching for hazards in the vehicle's blind spots, or improving
-night vision by using thermal imaging.
-
-Our understanding is that images from these cameras should only be made
-available to platform components or to specialized built-in app-bundles,
-so they are outside the scope of this document.
-
 ### Infotainment cameras
 
 [Android]({{< ref "#android" >}}) and [iOS]({{< ref "#ios" >}}) mobile phones and tablets typically have one or more
 cameras directed at the user or their surroundings, intended for photography,
-videoconferencing, augmented reality and entertainment. Our understanding is
-that this is not a normal use-case for an automotive operating system that
-should minimize driver distraction.
-
-If a vehicle does have such cameras, their use cases and security
+videoconferencing, augmented reality and entertainment. The use cases and security
 implications are very similar to audio recording, so we believe there
 is no need to describe them in detail in this document.