Bug 181085

Summary: [macOS, iOS] Adopt new secure coding APIs in WebKit
Product: WebKit Reporter: Brent Fulgham <bfulgham>
Component: WebKit Misc.Assignee: Brent Fulgham <bfulgham>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, david_quesada, thorton, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch thorton: review+

Brent Fulgham
Reported 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'.
Attachments
Patch (23.63 KB, patch)
2018-01-02 17:10 PST, Brent Fulgham 		thorton: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Brent Fulgham
Comment 1 2018-01-02 17:09:14 PST
<rdar://problem/34837397>
Brent Fulgham
Comment 2 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.
Brent Fulgham
Comment 3 2018-01-02 17:10:31 PST
Created attachment 330355 [details] Patch
Brent Fulgham
Comment 4 2018-01-02 21:10:39 PST
Committed r226353: <https://trac.webkit.org/changeset/226353>
David Quesada
Comment 5 2018-01-03 11:22:05 PST
*** Bug 181252 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.