Re: Exporting a public key from the secure enclave

> On May 15, 2017, at 3:46 PM, Jens Alfke wrote: > > Is there a specific reason you’re trying to work with the secure enclave > directly, and not just the keychain? > > In my experience the Keychain APIs are mind-curdlingly horrible to work with, > and the newer the

Re: Exporting a public key from the secure enclave

Is there a specific reason you’re trying to work with the secure enclave directly, and not just the keychain? In my experience the Keychain APIs are mind-curdlingly horrible to work with, and the newer the feature you’re trying to use, the worse they get. Have you tried doing this stuff

Re: Exporting a public key from the secure enclave

> On May 15, 2017, at 2:20 PM, Quincey Morris > wrote: > > On May 15, 2017, at 14:08 , Doug Hill > wrote: >> >> Also, the Security developer forum has held up my forum post for moderation >> for almost 4

Re: Exporting a public key from the secure enclave

On May 15, 2017, at 14:08 , Doug Hill wrote: > > Also, the Security developer forum has held up my forum post for moderation > for almost 4 days. You really should ask Quinn (the Eskimo). The moderation was probably due to the external GitHub link. Try removing the

Re: Times in other cities

Apple has a good Technical Q about this: https://developer.apple.com/library/content/qa/qa1480/_index.html Sal > You might want to err on the side of caution and ensure that the Calendar object is explicitly set > to Gregorian rather than using the current system setting. > Jonathan > On 15

Exporting a public key from the secure enclave

I'm attempting to implement what is described in this developer forum post: https://forums.developer.apple.com/message/84684#84684 That is, export an elliptic curve public key from the secure enclave. Unfortunately, this doesn't work for

Re: Times in other cities

Got it - I understand now. And I kindly thank you for the clarification. On Mon, May 15, 2017 at 9:31 AM Andrew Thompson wrote: > BST is British Summer Time, but also Bering Standard Time (UTC-11). Do you > want to risk getting the wrong one? > > The UK observes daylight

Re: Times in other cities

BST is British Summer Time, but also Bering Standard Time (UTC-11). Do you want to risk getting the wrong one? The UK observes daylight savings time, which being in Boston you no doubt understand means half the year the name of the time zone changes. In Boston Eastern time switches from EST to

Re: Times in other cities

Europe/London = BST though, correct? On Mon, May 15, 2017 at 9:06 AM Andrew Thompson wrote: > > > > On May 15, 2017, at 8:50 AM, Eric E. Dolecki wrote: > > > > Thanks for your reply. Does this look safe to use? > > > > // London > > let locale =

Re: Times in other cities

> On May 15, 2017, at 8:50 AM, Eric E. Dolecki wrote: > > Thanks for your reply. Does this look safe to use? > > // London > let locale = TimeZone.init(abbreviation: "BST") > Use "Europe/London": 1. BST has at least 3 different meanings 2. You'll automatically get

Re: Times in other cities

You might want to err on the side of caution and ensure that the Calendar object is explicitly set to Gregorian rather than using the current system setting. Jonathan > On 15 May 2017, at 13:50, Eric E. Dolecki wrote: > > Thanks for your reply. Does this look safe to use?

Re: Times in other cities

Thanks for your reply. Does this look safe to use? // London let locale = TimeZone.init(abbreviation: "BST") let cal = Calendar.current let date = Date() let comp = cal.dateComponents(in:locale!, from: date) // Local (right now for me it's Boston) let hour = Calendar.current.component(.hour,