net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
# SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
|
|
|
|
|
#
|
|
|
|
|
# Author: Chuck Lever <chuck.lever@oracle.com>
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2023, Oracle and/or its affiliates.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
name: handshake
|
|
|
|
|
|
|
|
|
|
protocol: genetlink
|
|
|
|
|
|
|
|
|
|
doc: Netlink protocol to request a transport layer security handshake.
|
|
|
|
|
|
|
|
|
|
definitions:
|
|
|
|
|
-
|
|
|
|
|
type: enum
|
|
|
|
|
name: handler-class
|
|
|
|
|
value-start: 0
|
2023-04-17 14:32:33 +00:00
|
|
|
entries: [ none, tlshd, max ]
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
type: enum
|
|
|
|
|
name: msg-type
|
|
|
|
|
value-start: 0
|
|
|
|
|
entries: [ unspec, clienthello, serverhello ]
|
|
|
|
|
-
|
|
|
|
|
type: enum
|
|
|
|
|
name: auth
|
|
|
|
|
value-start: 0
|
|
|
|
|
entries: [ unspec, unauth, psk, x509 ]
|
|
|
|
|
|
|
|
|
|
attribute-sets:
|
|
|
|
|
-
|
|
|
|
|
name: x509
|
|
|
|
|
attributes:
|
|
|
|
|
-
|
|
|
|
|
name: cert
|
2023-09-21 13:08:07 +00:00
|
|
|
type: s32
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
name: privkey
|
2023-09-21 13:08:07 +00:00
|
|
|
type: s32
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
name: accept
|
|
|
|
|
attributes:
|
|
|
|
|
-
|
|
|
|
|
name: sockfd
|
2023-09-21 13:07:40 +00:00
|
|
|
type: s32
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
name: handler-class
|
|
|
|
|
type: u32
|
|
|
|
|
enum: handler-class
|
|
|
|
|
-
|
|
|
|
|
name: message-type
|
|
|
|
|
type: u32
|
|
|
|
|
enum: msg-type
|
|
|
|
|
-
|
|
|
|
|
name: timeout
|
|
|
|
|
type: u32
|
|
|
|
|
-
|
|
|
|
|
name: auth-mode
|
|
|
|
|
type: u32
|
|
|
|
|
enum: auth
|
|
|
|
|
-
|
|
|
|
|
name: peer-identity
|
|
|
|
|
type: u32
|
|
|
|
|
multi-attr: true
|
|
|
|
|
-
|
|
|
|
|
name: certificate
|
|
|
|
|
type: nest
|
|
|
|
|
nested-attributes: x509
|
|
|
|
|
multi-attr: true
|
2023-05-11 15:49:50 +00:00
|
|
|
-
|
|
|
|
|
name: peername
|
|
|
|
|
type: string
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
name: done
|
|
|
|
|
attributes:
|
|
|
|
|
-
|
|
|
|
|
name: status
|
|
|
|
|
type: u32
|
|
|
|
|
-
|
|
|
|
|
name: sockfd
|
2023-09-21 13:07:40 +00:00
|
|
|
type: s32
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
name: remote-auth
|
|
|
|
|
type: u32
|
|
|
|
|
multi-attr: true
|
|
|
|
|
|
|
|
|
|
operations:
|
|
|
|
|
list:
|
|
|
|
|
-
|
|
|
|
|
name: ready
|
|
|
|
|
doc: Notify handlers that a new handshake request is waiting
|
|
|
|
|
notify: accept
|
|
|
|
|
-
|
|
|
|
|
name: accept
|
|
|
|
|
doc: Handler retrieves next queued handshake request
|
|
|
|
|
attribute-set: accept
|
|
|
|
|
flags: [ admin-perm ]
|
|
|
|
|
do:
|
|
|
|
|
request:
|
|
|
|
|
attributes:
|
|
|
|
|
- handler-class
|
|
|
|
|
reply:
|
|
|
|
|
attributes:
|
|
|
|
|
- sockfd
|
|
|
|
|
- message-type
|
|
|
|
|
- timeout
|
|
|
|
|
- auth-mode
|
|
|
|
|
- peer-identity
|
|
|
|
|
- certificate
|
2023-05-11 15:49:50 +00:00
|
|
|
- peername
|
net/handshake: Create a NETLINK service for handling handshake requests
When a kernel consumer needs a transport layer security session, it
first needs a handshake to negotiate and establish a session. This
negotiation can be done in user space via one of the several
existing library implementations, or it can be done in the kernel.
No in-kernel handshake implementations yet exist. In their absence,
we add a netlink service that can:
a. Notify a user space daemon that a handshake is needed.
b. Once notified, the daemon calls the kernel back via this
netlink service to get the handshake parameters, including an
open socket on which to establish the session.
c. Once the handshake is complete, the daemon reports the
session status and other information via a second netlink
operation. This operation marks that it is safe for the
kernel to use the open socket and the security session
established there.
The notification service uses a multicast group. Each handshake
mechanism (eg, tlshd) adopts its own group number so that the
handshake services are completely independent of one another. The
kernel can then tell via netlink_has_listeners() whether a handshake
service is active and prepared to handle a handshake request.
A new netlink operation, ACCEPT, acts like accept(2) in that it
instantiates a file descriptor in the user space daemon's fd table.
If this operation is successful, the reply carries the fd number,
which can be treated as an open and ready file descriptor.
While user space is performing the handshake, the kernel keeps its
muddy paws off the open socket. A second new netlink operation,
DONE, indicates that the user space daemon is finished with the
socket and it is safe for the kernel to use again. The operation
also indicates whether a session was established successfully.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2023-04-17 14:32:26 +00:00
|
|
|
-
|
|
|
|
|
name: done
|
|
|
|
|
doc: Handler reports handshake completion
|
|
|
|
|
attribute-set: done
|
|
|
|
|
do:
|
|
|
|
|
request:
|
|
|
|
|
attributes:
|
|
|
|
|
- status
|
|
|
|
|
- sockfd
|
|
|
|
|
- remote-auth
|
|
|
|
|
|
|
|
|
|
mcast-groups:
|
|
|
|
|
list:
|
|
|
|
|
-
|
|
|
|
|
name: none
|
2023-04-17 14:32:33 +00:00
|
|
|
-
|
|
|
|
|
name: tlshd
|