mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-09 17:38:00 +00:00
98200d1bfe
DIT, for 'Data-Independent Timing', is a bit you can set in the
processor state on sufficiently new Arm CPUs, which promises that a
long list of instructions will deliberately avoid varying their timing
based on the input register values. Just what you want for keeping
your constant-time crypto primitives constant-time.
As far as I'm aware, no CPU has _yet_ implemented any data-dependent
optimisations, so DIT is a safety precaution against them doing so in
future. It would be embarrassing to be caught without it if a future
CPU does do that, so we now turn on DIT in the PuTTY process state.
I've put a call to the new enable_dit() function at the start of every
main() and WinMain() belonging to a program that might do
cryptography (even testcrypt, in case someone uses it for something!),
and in case I missed one there, also added a second call at the first
moment that any cryptography-using part of the code looks as if it
might become active: when an instance of the SSH protocol object is
configured, when the system PRNG is initialised, and when selecting
any cryptographic authentication protocol in an HTTP or SOCKS proxy
connection. With any luck those precautions between them should ensure
it's on whenever we need it.
Arm's own recommendation is that you should carefully choose the
granularity at which you enable and disable DIT: there's a potential
time cost to turning it on and off (I'm not sure what, but plausibly
something of the order of a pipeline flush), so it's a performance hit
to do it _inside_ each individual crypto function, but if CPUs start
supporting significant data-dependent optimisation in future, then it
will also become a noticeable performance hit to just leave it on
across the whole process. So you'd like to do it somewhere in the
middle: for example, you might turn on DIT once around the whole
process of verifying and decrypting an SSH packet, instead of once for
decryption and once for MAC.
With all respect to that recommendation as a strategy for maximum
performance, I'm not following it here. I turn on DIT at the start of
the PuTTY process, and then leave it on. Rationale:
1. PuTTY is not otherwise a performance-critical application: it's
not likely to max out your CPU for any purpose _other_ than
cryptography. The most CPU-intensive non-cryptographic thing I can
imagine a PuTTY process doing is the complicated computation of
font rendering in the terminal, and that will normally be cached
(you don't recompute each glyph from its outline and hints for
every time you display it).
2. I think a bigger risk lies in accidental side channels from having
DIT turned off when it should have been on. I can imagine lots of
causes for that. Missing a crypto operation in some unswept corner
of the code; confusing control flow (like my coroutine macros)
jumping with DIT clear into the middle of a region of code that
expected DIT to have been set at the beginning; having a reference
counter of DIT requests and getting it out of sync.
In a more sophisticated programming language, it might be possible to
avoid the risk in #2 by cleverness with the type system. For example,
in Rust, you could have a zero-sized type that acts as a proof token
for DIT being enabled (it would be constructed by a function that also
sets DIT, have a Drop implementation that clears DIT, and be !Send so
you couldn't use it in a thread other than the one where DIT was set),
and then you could require all the actual crypto functions to take a
DitToken as an extra parameter, at zero runtime cost. Then "oops I
forgot to set DIT around this piece of crypto" would become a compile
error. Even so, you'd have to take some care with coroutine-structured
code (what happens if a Rust async function yields while holding a DIT
token?) and with nesting (if you have two DIT tokens, you don't want
dropping the inner one to clear DIT while the outer one is still there
to wrongly convince callees that it's set). Maybe in Rust you could
get this all to work reliably. But not in C!
DIT is an optional feature of the Arm architecture, so we must first
test to see if it's supported. This is done the same way as we already
do for the various Arm crypto accelerators: on ELF-based systems,
check the appropriate bit in the 'hwcap' words in the ELF aux vector;
on Mac, look for an appropriate sysctl flag.
On Windows I don't know of a way to query the DIT feature, _or_ of a
way to write the necessary enabling instruction in an MSVC-compatible
way. I've _heard_ that it might not be necessary, because Windows
might just turn on DIT unconditionally and leave it on, in an even
more extreme version of my own strategy. I don't have a source for
that - I heard it by word of mouth - but I _hope_ it's true, because
that would suit me very well! Certainly I can't write code to enable
DIT without knowing (a) how to do it, (b) how to know if it's safe.
Nonetheless, I've put the enable_dit() call in all the right places in
the Windows main programs as well as the Unix and cross-platform code,
so that if I later find out that I _can_ put in an explicit enable of
DIT in some way, I'll only have to arrange to set HAVE_ARM_DIT and
compile the enable_dit() function appropriately.
64 lines
1.8 KiB
C
64 lines
1.8 KiB
C
#cmakedefine NO_IPV6
|
|
#cmakedefine NO_GSSAPI
|
|
#cmakedefine STATIC_GSSAPI
|
|
#cmakedefine NO_SCROLLBACK_COMPRESSION
|
|
|
|
#cmakedefine NO_MULTIMON
|
|
|
|
#cmakedefine01 HAVE_WINRESRC_H
|
|
#cmakedefine01 HAVE_WINRES_H
|
|
#cmakedefine01 HAVE_WIN_H
|
|
#cmakedefine01 HAVE_NO_STDINT_H
|
|
#cmakedefine01 HAVE_AFUNIX_H
|
|
#cmakedefine01 HAVE_GCP_RESULTSW
|
|
#cmakedefine01 HAVE_ADDDLLDIRECTORY
|
|
#cmakedefine01 HAVE_GETNAMEDPIPECLIENTPROCESSID
|
|
#cmakedefine01 HAVE_SETDEFAULTDLLDIRECTORIES
|
|
#cmakedefine01 HAVE_STRTOUMAX
|
|
#cmakedefine01 HAVE_DWMAPI_H
|
|
|
|
#cmakedefine NOT_X_WINDOWS
|
|
#cmakedefine OMIT_UTMP
|
|
|
|
#cmakedefine01 HAVE_ASM_HWCAP_H
|
|
#cmakedefine01 HAVE_SYS_AUXV_H
|
|
#cmakedefine01 HAVE_SYS_SYSCTL_H
|
|
#cmakedefine01 HAVE_SYS_TYPES_H
|
|
#cmakedefine01 HAVE_GLOB_H
|
|
#cmakedefine01 HAVE_UTMP_H
|
|
#cmakedefine01 HAVE_FUTIMES
|
|
#cmakedefine01 HAVE_GETADDRINFO
|
|
#cmakedefine01 HAVE_POSIX_OPENPT
|
|
#cmakedefine01 HAVE_PTSNAME
|
|
#cmakedefine01 HAVE_SETRESUID
|
|
#cmakedefine01 HAVE_SETRESGID
|
|
#cmakedefine01 HAVE_STRSIGNAL
|
|
#cmakedefine01 HAVE_UPDWTMPX
|
|
#cmakedefine01 HAVE_FSTATAT
|
|
#cmakedefine01 HAVE_DIRFD
|
|
#cmakedefine01 HAVE_SETPWENT
|
|
#cmakedefine01 HAVE_ENDPWENT
|
|
#cmakedefine01 HAVE_GETAUXVAL
|
|
#cmakedefine01 HAVE_ELF_AUX_INFO
|
|
#cmakedefine01 HAVE_SYSCTLBYNAME
|
|
#cmakedefine01 HAVE_CLOCK_MONOTONIC
|
|
#cmakedefine01 HAVE_CLOCK_GETTIME
|
|
#cmakedefine01 HAVE_SO_PEERCRED
|
|
#cmakedefine01 HAVE_NULLARY_SETPGRP
|
|
#cmakedefine01 HAVE_BINARY_SETPGRP
|
|
#cmakedefine01 HAVE_PANGO_FONT_FAMILY_IS_MONOSPACE
|
|
#cmakedefine01 HAVE_PANGO_FONT_MAP_LIST_FAMILIES
|
|
#cmakedefine01 HAVE_G_APPLICATION_DEFAULT_FLAGS
|
|
|
|
#cmakedefine01 HAVE_AES_NI
|
|
#cmakedefine01 HAVE_SHA_NI
|
|
#cmakedefine01 HAVE_SHAINTRIN_H
|
|
#cmakedefine01 HAVE_CLMUL
|
|
#cmakedefine01 HAVE_NEON_CRYPTO
|
|
#cmakedefine01 HAVE_NEON_PMULL
|
|
#cmakedefine01 HAVE_NEON_VADDQ_P128
|
|
#cmakedefine01 HAVE_NEON_SHA512
|
|
#cmakedefine01 HAVE_NEON_SHA512_INTRINSICS
|
|
#cmakedefine01 USE_ARM64_NEON_H
|
|
#cmakedefine01 HAVE_ARM_DIT
|