1
00:00:02,341 --> 00:00:07,624
If you are still pasting static OpenAI API
keys into your CI runners or Kubernetes

2
00:00:07,664 --> 00:00:11,707
secrets, November twentieth brought a
pretty big reason to stop.

3
00:00:12,467 --> 00:00:16,309
Codex CLI zero point one seven one point
zero just shipped,

4
00:00:16,770 --> 00:00:21,312
and while we already talked about its TUI
workspace and GPT six point two defaults,

5
00:00:21,712 --> 00:00:24,654
there is a massive security feature buried
in the changelog.

6
00:00:25,374 --> 00:00:29,217
Before we get into the mechanics, thanks
to Jellypod AI for sponsoring this episode.

7
00:00:29,677 --> 00:00:33,319
They make it easy to turn technical
changelogs and research into audio you can

8
00:00:33,459 --> 00:00:34,860
actually listen to on your commute.

9
00:00:36,170 --> 00:00:39,812
Let us look at PR sixty one thousand two
hundred seven.

10
00:00:40,593 --> 00:00:47,576
Codex CLI zero point one seven one point
zero added SPIFFE JWT SVID support for

11
00:00:47,696 --> 00:00:49,357
workload identity authentication.

12
00:00:50,677 --> 00:00:55,360
If you have not worked with SPIFFE before,
it stands for Secure Production Identity

13
00:00:55,460 --> 00:00:56,680
Framework for Everyone.

14
00:00:57,501 --> 00:01:01,542
Basically, it gives your workloads, like a
Kubernetes pod or a build runner,

15
00:01:02,003 --> 00:01:05,784
a cryptographic identity attested by a
local agent like SPIRE.

16
00:01:06,465 --> 00:01:10,087
Instead of storing a long lived API key in
an environment variable,

17
00:01:10,567 --> 00:01:15,689
your workload fetches a short lived JWT
SVID and exchanges it with OpenAI for a

18
00:01:15,789 --> 00:01:16,990
short lived access token.

19
00:01:18,796 --> 00:01:19,877
Why does this matter?

20
00:01:20,897 --> 00:01:24,520
Static API keys are a nightmare in
automated coding pipelines.

21
00:01:25,020 --> 00:01:29,143
They sit in secret managers, they get
copied into local dot env files,

22
00:01:29,603 --> 00:01:34,226
and if one leaks, it stays valid until
someone notices and revokes it.

23
00:01:34,927 --> 00:01:38,709
With workload identity federation, there
is no static key to leak.

24
00:01:39,229 --> 00:01:42,331
The token is bound to the attested
workload and expires quickly.

25
00:01:43,452 --> 00:01:47,415
Even if an attacker grabs a token from
memory, its blast radius is tiny.

26
00:01:48,812 --> 00:01:50,773
So how do you actually set this up?

27
00:01:51,873 --> 00:01:58,416
First, you configure your SPIFFE or SPIRE
server and your OIDC Discovery Provider

28
00:01:58,856 --> 00:02:03,057
with a matching HTTPS JWT issuer URL.

29
00:02:03,998 --> 00:02:08,019
If OpenAI cannot reach your discovery
endpoint over the public internet,

30
00:02:08,579 --> 00:02:11,540
you can use uploaded JWKS mode instead.

31
00:02:13,021 --> 00:02:19,343
Second, you assign a stable SPIFFE ID to
your workload, something like spiffe colon

32
00:02:19,503 --> 00:02:24,985
slash slash example dot org slash ns slash
production slash sa

33
00:02:31,727 --> 00:02:38,210
slash openai wif, and a dedicated

34
00:02:38,350 --> 00:02:44,972
audience like https colon slash slash api
dot openai dot com slash v1.

35
00:02:46,574 --> 00:02:53,037
Third, you fetch the JWT SVID from the
local SPIFFE Workload API inside the exact

36
00:02:53,097 --> 00:02:54,317
same workload context.

37
00:02:55,238 --> 00:03:01,221
Using the spire agent CLI, that looks like
running spire agent api fetch jwt,

38
00:03:02,061 --> 00:03:06,523
passing the socket path to your agent dot
sock, and passing the audience flag.

39
00:03:07,784 --> 00:03:12,265
One important note here: the release
summary for PR sixty one thousand two hundred

40
00:03:12,265 --> 00:03:17,549
seven does not list the exact Codex CLI
config keys or flags introduced for this

41
00:03:17,629 --> 00:03:17,929
flow.

42
00:03:18,729 --> 00:03:23,332
Rather than guessing, check the PR diff or
the updated configuration docs once you

43
00:03:23,352 --> 00:03:25,813
upgrade to zero point one seven one point
zero.

44
00:03:27,673 --> 00:03:33,876
Now, there are three big caveats to watch
out for, and they will trip you up if you

45
00:03:33,896 --> 00:03:34,876
do not check them first.

46
00:03:36,056 --> 00:03:42,599
Number one: OpenAI only supports SPIFFE
JWT SVIDs as workload identity federation

47
00:03:42,719 --> 00:03:43,459
subject tokens.

48
00:03:44,199 --> 00:03:46,960
SPIFFE X five zero nine SVIDs are NOT
supported.

49
00:03:50,001 --> 00:03:56,123
Number two: the standard SPIFFE JWT SVID
spec makes the JWT header kid field

50
00:03:56,324 --> 00:03:58,104
optional, meaning key ID.

51
00:03:59,085 --> 00:04:04,146
OpenAI requires that kid header so it can
pick the right signing key from your JWKS,

52
00:04:05,047 --> 00:04:09,808
and it also requires iss and iat claims
alongside sub, aud,

53
00:04:09,808 --> 00:04:10,328
and exp.

54
00:04:11,889 --> 00:04:16,851
Number three: Workload API authorization
depends on the identity of the calling

55
00:04:16,891 --> 00:04:21,532
process, so you have to run your token
fetch and inspection in the actual workload

56
00:04:21,572 --> 00:04:22,093
context.

57
00:04:24,811 --> 00:04:29,733
Beyond workload identity, zero point one
seven one point zero packed in several

58
00:04:29,793 --> 00:04:32,755
Linux sandbox hardening updates that are
worth knowing about.

59
00:04:33,495 --> 00:04:38,818
First, PR sixty one thousand two hundred
six enforces Linux seccomp restrictions for

60
00:04:39,038 --> 00:04:40,178
x32 syscalls.

61
00:04:40,819 --> 00:04:45,701
Second, PR sixty one thousand two hundred
fifty six blocks request key in Linux

62
00:04:45,841 --> 00:04:47,162
network sandbox filters.

63
00:04:48,363 --> 00:04:53,385
And third, PR sixty one thousand three
hundred seventy two adds opt in transparent

64
00:04:53,465 --> 00:04:55,546
TCP routing for Linux sandboxes.

65
00:04:56,327 --> 00:05:00,749
If you run Codex agents in locked down
Linux containers, these are quiet but

66
00:05:00,889 --> 00:05:02,750
meaningful tightening of the security
boundary.

67
00:05:03,745 --> 00:05:07,948
Two other quality of life wins landed in
zero point one seven one point zero.

68
00:05:09,009 --> 00:05:13,532
For AWS users, PR sixty one thousand four
hundred twenty six enables incremental

69
00:05:13,592 --> 00:05:18,492
tools by default for Amazon Bedrock,
building on the opt in support from zero point

70
00:05:18,492 --> 00:05:19,836
one six seven point one.

71
00:05:20,416 --> 00:05:24,179
And for enterprise teams, PR sixty one
thousand two hundred twenty nine fixes

72
00:05:24,319 --> 00:05:29,002
enterprise MCP sign in for identity
providers that issue ID tokens without refresh

73
00:05:29,062 --> 00:05:29,422
tokens.

74
00:05:30,243 --> 00:05:33,185
That was a painful edge case for locked
down corporate SSO setups.

75
00:05:34,280 --> 00:05:38,101
Finally, let us look at what happened on
the main branch right after zero point one

76
00:05:38,101 --> 00:05:41,383
seven one point zero, between November
twentieth and twenty second.

77
00:05:42,463 --> 00:05:48,505
The team tagged zero point one seven three
point zero alpha one through alpha four,

78
00:05:48,505 --> 00:05:51,387
though those pre releases do not have
published release notes yet.

79
00:05:52,187 --> 00:05:54,908
On main, however, we can see three clean
fixes.

80
00:05:55,428 --> 00:05:59,970
Default TUI sessions now preserve your
host terminal cursor shape unless Codex

81
00:05:59,990 --> 00:06:01,630
applies an explicit override.

82
00:06:02,291 --> 00:06:06,952
The TypeScript SDK now tracks explicit web
search modes, specifically cached and

83
00:06:07,092 --> 00:06:10,394
indexed, in PR sixty two thousand eight
hundred eighty four.

84
00:06:11,074 --> 00:06:15,755
And on macOS, PR sixty two thousand six
hundred forty eight fixes standalone release

85
00:06:15,815 --> 00:06:20,337
pruning when GNU coreutils stat sits ahead
of macOS stat on your PATH.

86
00:06:21,298 --> 00:06:22,058
That is it for today.

87
00:06:22,478 --> 00:06:26,479
Update to zero point one seven one point
zero, check your SPIFFE claims,

88
00:06:26,840 --> 00:06:27,840
and we will catch you next time.

