Use Fig without disabling Secure Keyboard Entry

withfig / fig

Public issue tracker for Fig.

https://fig.io

MIT License

2.06k stars 63 forks source link

Use Fig without disabling Secure Keyboard Entry #764

Open mschrage opened 2 years ago

mschrage commented 2 years ago

Tracking issue for users who work at companies with MDM policies that require secure keyboard entry to be enabled.

To learn more about Secure Keyboard Entry see "Fig and Secure Keyboard Input.

brendanfalk commented 2 years ago

Likely fix here is taking part of our keyboard interception logic from the OS level all to our pseudoterminal level. Will likely prioritise within the next month or two

grant0417 commented 2 years ago

Likely fix here is taking part of our keyboard interception logic from the OS level all to our pseudoterminal level. Will likely prioritise within the next month or two

Issues that come from having to do this in the psudoterminal level:

No way to intercept ⌘
Needs to communicate over IPC for every character
Pasting values in the terminal will act the same as pressing the key, with a clipboard of a single tab ⌘+v and tab will both be seen the same.

mschrage commented 2 years ago

A variety of companies mandate that their employees turn on secure keyboard entry.

Fig uses the functionality that secure keyboard entry blocks for hotkey management (e.g. tab/enter insert text, up and down arrows navigate, cmd+i toggles description).

If your company asks you to use secure keyboard entry but you want to use Fig, just email brendan AT fig.io.

Brendan will usually email the CEO / engineering manager directly and get approval for you. We have gone through security reviews at a bunch of the big tech companies and are used in heavily regulated companies too like fintechs, HIPAA compliant etc