Bug 181085 - [macOS, iOS] Adopt new secure coding APIs in WebKit
Summary: [macOS, iOS] Adopt new secure coding APIs in WebKit
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Brent Fulgham
URL:
Keywords: InRadar
: 181252 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-12-21 09:40 PST by Brent Fulgham
Modified: 2018-01-03 11:22 PST (History)
4 users (show)

See Also:

Attachments
Patch (23.63 KB, patch)
2018-01-02 17:10 PST, Brent Fulgham 		thorton: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Fulgham 2017-12-21 09:40:55 PST 
Switch away from older NSKeyedArchiver/NSKeyedUnarchive methods that supported non-NSSecureCoding serialization.

This patch switches the last remaining 'insecure' cases to 'secure'.
Comment 1 Brent Fulgham 2018-01-02 17:09:14 PST 
<rdar://problem/34837397>
Comment 2 Brent Fulgham 2018-01-02 17:10:22 PST 
It looks like NSView/UIView do not support NSSecureCoding, so we can't completely switch WKWebView to NSSecureCoding. But we can make sure it's ready when the time comes.
Comment 3 Brent Fulgham 2018-01-02 17:10:31 PST 
Created attachment 330355 [details]
Patch
Comment 4 Brent Fulgham 2018-01-02 21:10:39 PST 
Committed r226353: <https://trac.webkit.org/changeset/226353>
Comment 5 David Quesada 2018-01-03 11:22:05 PST 
*** Bug 181252 has been marked as a duplicate of this bug. ***