- What’s in the High Sierra 10.13.4 update?
- macOS High Sierra 10.13.4 fixes APFS encryption password disclosure bug
- Changing Stories: Ovid’s Metamorphoses on canvas, 81 – Pythagoras and vegetarianism
- What’s in Sierra Security Update 2018-002?
- macOS High Sierra 10.13.4, Sierra and El Cap Security Update 2018-002, and Safari 11.1 released (updated)
- Inside iCloud Drive: uploading a file
Posted: 30 Mar 2018 10:21 AM PDT
Apple was a little more forthcoming in the list of improvements and fixes in macOS High Sierra 10.13.4, although it still doesn’t seem to account for a 2.3 GB update, even allowing for all the EFI firmware upgrades which came with it.
My list of components of macOS Sierra 10.12.6 which are included in 10.13.4 released on 29/30 March 2018 includes:
The bundled EFI firmware update should increment the reported Boot ROM version of every Mac, apart from those which have already undergone update during beta-testing of this update. I have updated my full listing of version numbers to take this into account.
Apple doesn’t explain what has changed in the EFI updates; from reports during 10.13.4 beta-testing, these should include further fixes for Meltdown/Spectre vulnerabilities.
Posted: 30 Mar 2018 07:05 AM PDT
The latest update to High Sierra, bringing it to 10.13.4, does fix the bug discovered by Sarah Edwards when making an APFS encrypted volume in Disk Utility – in both its original form (fixed in 10.13.2) and the form which remained into 10.13.3.
Although erasing a disk and creating an APFS container still result in
That is a very quick turnaround by Apple, in fixing the remaining bug in less than a week, and reinforces my opinion that this was an oversight of which Apple had been unaware.
Hopefully Apple will soon amend the list of security fixes for the 10.13.4 update to credit Sarah Edwards with reporting this bug, and making it explicit that it is now fixed.
Posted: 30 Mar 2018 04:30 AM PDT
Ovid opens the fifteenth and final book of his Metamorphoses by continuing his account of the early rulers of Rome. With the apotheosis of Romulus, the next is his successor Numa, whom he uses as narrator for an overview of the Metamorphoses in Pythagorean philosophical terms.
Fame nominates Numa as successor to Romulus as the ruler of Rome. Numa had left Cures, the town of his birth, to travel to Crotona (Crotone), in the far south of the Italian peninsula, where he visited Croton, its ruler.
This is Ovid’s cue for a story about Myscelus, who founded Crotona. Hercules appeared to him in a dream, and told him to travel to the river Aesar, despite his being forbidden from leaving his native land of Argos. Driven by dreams of Hercules, Myscelus tried to leave but was accused of treason, and appealed to Hercules to save him from the mandatory death penalty.
At that time, trial juries voted by casting black or white pebbles into an urn; being undoubtedly guilty, all those cast in Myscelus’ case were black when they were placed in the urn:
Myscelus was therefore able to sail to found Crotona on the River Aesar.
After he had fled Samos, Ovid tells us that Pythagoras lived in exile at Crotona, and this leads to a long discourse on his doctrines and philosophy. Having assured us of Pythagoras’ diligent observation of the world around him and careful analysis of what he saw, Ovid starts with an exhortation to vegetarianism.
Within this discourse, Ovid makes reference to preceding sections and themes of Metamorphoses. Pythagoras’ words hark back to the Golden Age, which was covered in Book 1. Pythagoras lays claim to reincarnation too, saying that in a previous life he had been Euphorbus, who had been killed by Menelaus in the Trojan War. This leads Pythagoras on to discussing change and transformation, the central theme of these fifteen books.
Pythagoras sees change in the waves of the sea, in the sequence of day and night, in the four seasons, in the ageing of humans, and in the transformation of the elements (earth, air, water, and fire):
Pythagoras then illustrates this constant change with a long list of places whose geography had changed in recorded history, and of locations which cause change in those who visit them. After those, he returns to the theme of change in animals, telling the legend of the Phoenix which is reborn from the ashes of its parent. This leads on to consideration of some great cities which have fallen, and the chance to point out that Troy never fell completely, as it reached its destiny of founding the city and empire of Rome.
Finally, Pythagoras returns to the subject of vegetarianism:
Sadly, coverage of the opening of this book in visual art has been essentially absent, but Pythagoras has inspired some great paintings, and is my focus here.
A great many prints and other representations of Pythagoras recall the first image that I have been able to find, by Raphael.
In his magnificant fresco in the Palazzo Apostolico, The School of Athens painted in about 1509-11, Raphael includes Pythagoras at the lower left corner.
This detail shows Pythagoras writing in a large book, with a chalk drawing on a small blackboard in front of his left foot. Others are looking over his shoulder and studying what he is doing.
Despite the popularity of Ovid’s Metamorphoses over the centuries, very little seems to have been written or painted about its lengthy advocacy of a vegetarian diet and lifestyle. It did, though, inspire one exceptional painting.
Peter Paul Rubens collaborated with Frans Snyders to paint Pythagoras Advocating Vegetarianism in about 1618-20. The mathematician and philosopher sits to the left of centre, with a group of followers further to the left. The painting is dominated by its extensive display of fruit and vegetables, which is being augmented by three nymphs and two satyrs. One of the latter seems less interested in the food than he is in one of the nymphs.
Today, Pythagoras is best known for his geometric discoveries, rather than the doctrines detailed by Ovid. Fyodor Bronnikov’s painting of Pythagoreans Celebrate Sunrise from 1869 is perhaps more in keeping with the Classical perception. These followers are decidedly musical, holding between them four lyres, a harp, and a flute, and worshipping the rising sun.
The English translation of Ovid above is taken from Ovid. Metamorphoses. Tr. Brookes More. Boston. Cornhill Publishing Co. 1922, at Perseus. I am very grateful to Perseus at Tufts for this.
Posted: 30 Mar 2018 04:09 AM PDT
The following components of macOS Sierra 10.12.6 have been updated in Security Update 2018-002 released on 29/30 March 2018:
As is usual, these extend well beyond the short list of security fixes provided by Apple.
Installed separately at the same time is an update of the Gatekeeper database to version 138 dated 29 March 2018.
Additionally, EFI firmware updates are installed for all Macs, incrementing the reported Boot ROM version. This iMac17,1 went from 0147 B00 to 0151 B00. I have now updated my list of EFI firmware versions to reflect these changes.
Apple doesn’t explain what has changed in the EFI updates; from reports during 10.13.4 beta-testing, these are very likely to include further fixes for Meltdown/Spectre vulnerabilities.
Although a separate download, Safari 11.1 also brings several improvements and fixes.
Posted: 30 Mar 2018 02:33 AM PDT
Overnight (UTC), Apple has released the update to High Sierra 10.13.4, Safari 11.1, and security updates to El Capitan and Sierra.
Fixes and improvements to High Sierra include:
There is no mention of any extension of APFS support to include Fusion Drives, and the APFS documentation no longer makes any reference to Fusion Drives, which appears ominous.
I will look in detail at the complete content of the 10.13.4 update in a future article.
Important security fixes include:
All Macs should undergo EFI update with this installation. Updating Sierra typically brings two complete chimed restarts, and is quite a lengthy process. No mention is made by Apple of the EFI firmware update, nor do the security release notes explain that further fixes are included there, although they are believed to address Meltdown/Spectre issues.
I have now updated my list of EFI firmware versions to reflect these changes.
Unusually, these updates were not released simultaneously with the corresponding iOS and other updates, but were delayed by several hours. I have now confirmed that 10.13.4 does fix recently-reported issues with unintentional release of APFS encryption passwords in the log.
As usual, the updates are available from the App Store. Standalone updates are also now available from:
The latter were not made avilable until 1200 UTC 30 March.
(Updated again 1550 UTC 30 March to include EFI update info.)
Posted: 29 Mar 2018 11:30 PM PDT
Having got Cirrus as a tool to look at what iCloud does, here’s what I have seen when copying a single 1 MB file from a local folder into the top level of my iCloud Drive. This account is based largely on what happens in High Sierra 10.13.3, although it is broadly similar to the sequences that I have seen in Sierra 10.12.6. High Sierra’s log messages are, in this case, rather clearer.
The intent to move/copy a file to iCloud Drive lands first with CloudDocs, which posts an [INFO] message for the File System Event:
Among the steps undertaken next is the retrieval/generation of a QuickLook thumbnail, which in this case failed, as there is no known QuickLook plugin for a file with the extension .data.
This is presumably the (very early) point at which the file appears at its destination, as CloudDocs calls for the file to be uploaded there. This is performed under the control of CloudKit, which classifies this as a ‘Modify Records Operation’ with a shortened name of Upload:
This triggers a complex sequence of state transitions in
CloudKit then adds a child operation to the Upload to fetch a record from the PCS cache; as this is a new file, there is no such record, so CloudKit creates a new one. It then proceeds to start the upload of the asset:
MMCS then activates and chunks the data to be transferred, and asks for a Put complete request. It then goes idle again.
CloudKit next adds a child operation to request an asset token, the URL for the user partition in iCloud. This leads through a series of exchanges to CloudKit providing MMCS with another set of options, to put the item to iCloud. Once again, MMCS chunks the data to be transferred, which is then passed up to the iCloud servers.
CloudKit then announces that it has completed the Upload Assets operation:
CloudDocs finally publishes a notice announcing the completion of the upload:
This appears in little more than a second after the start of the whole sequence, at which stage the Finder’s iCloud sync progress indicator is still incomplete. In this case, there were two further series of exchanges involving
The second was triggered by an incoming message from APS, Apple’s Push Service, which was initially handled by CloudDocs. This triggered a CloudKit operation to fetch record zone changes, or a ‘Sync down (push triggered)’. My interpretation of that is that the iCloud service pushed my Mac a request for it to synchronise with iCloud Drive, which was to propagate the change that had just been made in its contents, by my Mac!
Eventually, CloudDocs reported:
It then applied the changes, which reflected the upload of my test file to iCloud Drive:
This was about 3.5 seconds after the start of this series of processes, and roughly coincided with the moment that the progress icon was removed from the Finder window. The upload was complete.
I have summarised the main blocks of exchanges, using the same colour code as in Cirrus, in the following diagram, which gives you an idea of how complex it is to execute a single action. Look through the log entries in Cirrus, and you should be able to trace the processes.
These should give you an idea of the sequence of events which you should see during a normal and successful upload of a test file to iCloud Drive. They exclude all the network transfer work, which is performed by com.apple.mDNSResponder, com.apple.network,
I have also not considered the role of com.apple.duetactivityscheduler (DAS), the dispatching system which seems to schedule the transfer of data. If you are still running Sierra, you should bear in mind that Macs which are left running Sierra continuously for periods over five days can suffer failure of the DAS subsystem; that could explain failure to transfer files to iCloud. A simple indicator of that problem is the resulting failure in timed automatic Time Machine backups, another feature dispatched by DAS.
You can examine DAS in detail using Consolation 3, or DispatchView (from Downloads above).
|You are subscribed to email updates from The Eclectic Light Company. |
To stop receiving these emails, you may unsubscribe now.
|Email delivery powered by Google|
|Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States|