Searched hist:"130 b14681439a48d62fc44e0b860687b9df9b770" (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/security/audit/ |
H A D | audit_arg.c | diff 130b14681439a48d62fc44e0b860687b9df9b770 Mon Nov 06 01:15:44 CET 2006 Christian S.J. Peron <csjp@FreeBSD.org> Change the type of ar_arg_sockaddr from struct sockaddr to struct sockaddr_storage. This structure is defined in RFC 2553 and is a more semantically correct structure for holding IP and IP6 sockaddr information. struct sockaddr is not big enough to hold all the required information for IP6, resulting in truncated addresses et al when auditing IP6 sockaddr information.
We also need to assume that the sa->sa_len has been validated before the call to audit_arg_sockaddr() is made, otherwise it could result in a buffer overflow. This is being done to accommodate auditing of network related arguments (like connect, bind et al) that will be added soon.
Discussed with: rwatson Obtained from: TrustedBSD Project MFC after: 2 weeks diff 130b14681439a48d62fc44e0b860687b9df9b770 Mon Nov 06 01:15:44 CET 2006 Christian S.J. Peron <csjp@FreeBSD.org> Change the type of ar_arg_sockaddr from struct sockaddr to struct sockaddr_storage. This structure is defined in RFC 2553 and is a more semantically correct structure for holding IP and IP6 sockaddr information. struct sockaddr is not big enough to hold all the required information for IP6, resulting in truncated addresses et al when auditing IP6 sockaddr information.
We also need to assume that the sa->sa_len has been validated before the call to audit_arg_sockaddr() is made, otherwise it could result in a buffer overflow. This is being done to accommodate auditing of network related arguments (like connect, bind et al) that will be added soon.
Discussed with: rwatson Obtained from: TrustedBSD Project MFC after: 2 weeks
|
H A D | audit_private.h | diff 130b14681439a48d62fc44e0b860687b9df9b770 Mon Nov 06 01:15:44 CET 2006 Christian S.J. Peron <csjp@FreeBSD.org> Change the type of ar_arg_sockaddr from struct sockaddr to struct sockaddr_storage. This structure is defined in RFC 2553 and is a more semantically correct structure for holding IP and IP6 sockaddr information. struct sockaddr is not big enough to hold all the required information for IP6, resulting in truncated addresses et al when auditing IP6 sockaddr information.
We also need to assume that the sa->sa_len has been validated before the call to audit_arg_sockaddr() is made, otherwise it could result in a buffer overflow. This is being done to accommodate auditing of network related arguments (like connect, bind et al) that will be added soon.
Discussed with: rwatson Obtained from: TrustedBSD Project MFC after: 2 weeks diff 130b14681439a48d62fc44e0b860687b9df9b770 Mon Nov 06 01:15:44 CET 2006 Christian S.J. Peron <csjp@FreeBSD.org> Change the type of ar_arg_sockaddr from struct sockaddr to struct sockaddr_storage. This structure is defined in RFC 2553 and is a more semantically correct structure for holding IP and IP6 sockaddr information. struct sockaddr is not big enough to hold all the required information for IP6, resulting in truncated addresses et al when auditing IP6 sockaddr information.
We also need to assume that the sa->sa_len has been validated before the call to audit_arg_sockaddr() is made, otherwise it could result in a buffer overflow. This is being done to accommodate auditing of network related arguments (like connect, bind et al) that will be added soon.
Discussed with: rwatson Obtained from: TrustedBSD Project MFC after: 2 weeks
|