4 ms·

I think there should be a non-AI build so companies can allow this specific flavor and not ban iTerm2 completely. There is always going to be somebody using it

by 404mm 2y ago

I think there should be a non-AI build so companies can allow this specific flavor and not ban iTerm2 completely. There is always going to be somebody using it when they shouldn’t.

542458 2y ago
You don’t need a separate build. This has the exact same risk profile as somebody just navigating to the openAI website, and can be blocked in the exact same way, with network policy. I could see the argument that the iterm needs a more clear way to explicitly disable these features (rather than not configuring them) but I don’t think a separate build solves anything.
mullingitover 2y ago
You can make calls to OpenAI's API with curl, too. Should we ask for linux distros without curl, to prevent employees from accessing AI that way? If companies are that worried about rogue employee access to forbidden AI APIs, the network layer seems like a more appropriate place for those blocks.