mirrors/tcpdump
0
0
Fork 0
mirror of https://github.com/the-tcpdump-group/tcpdump.git synced 2024-11-30 21:44:49 +08:00
Code Issues Packages Projects Releases Wiki Activity
c9e5ac541b
tcpdump/parsenfsfh.c

463 lines
12 KiB
C
Raw Normal View History

clearify copyright. based on communication with the author, Jeffrey Mogul <mogul@pa.dec.com>. From: Jakob Schlyter <jakob@openbsd.org>
2001-06-15 08:17:58 +08:00
/*
* Copyright (c) 1993, 1994 Jeffrey C. Mogul, Digital Equipment Corporation,
* Western Research Laboratory. All rights reserved.
* Copyright (c) 2001 Compaq Computer Corporation. All rights reserved.
*
* Permission to use, copy, and modify this software and its
* documentation is hereby granted only under the following terms and
* conditions. Both the above copyright notice and this permission
* notice must appear in all copies of the software, derivative works
* or modified versions, and any portions thereof, and both notices
* must appear in supporting documentation.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND COMPAQ COMPUTER CORPORATION
* DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
* ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
* EVENT SHALL COMPAQ COMPUTER CORPORATION BE LIABLE FOR ANY
* SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
* AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
* OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
* SOFTWARE.
*/
Initial revision
1999-10-08 07:47:09 +08:00
/*
* parsenfsfh.c - portable parser for NFS file handles
* uses all sorts of heuristics
*
* Jeffrey C. Mogul
* Digital Equipment Corporation
* Western Research Laboratory
*/
Switch to config.h instead of passing defines in DEFS.
1999-11-21 17:36:43 +08:00
#ifdef HAVE_CONFIG_H
Always include <config.h> rather than "config.h". This can prevent bizarre failures if, for example, you've done a configuration in the top-level source directory, leaving behind one config.h file, and then do an out-of-tree build in another directory, with different configuration options. This way, we always pick up the same config.h, in the build directory.
2018-01-22 04:27:08 +08:00
#include <config.h>
Initial revision
1999-10-08 07:47:09 +08:00
#endif
Use quoted include netdissect-stdinc.h instead of angle-bracketed one
2018-01-20 22:59:49 +08:00
#include "netdissect-stdinc.h"
Initial revision
1999-10-08 07:47:09 +08:00
#include <stdio.h>
#include <string.h>
Don't use <ctype.h> macros. Some of them are locale-dependent, and all of them run the risk of failing if you hand them a char with the 8th bit set. Move our replacements to a new netdissect-ctype.h file, and, for the ones that check for particular character types, add _ASCII to the name, to indicate that only ASCII characters pass the check. Do the same for the ones that map between cases, to indicate that they only map ASCII letters. For isspace(), explicitly check for the characters we care about, to make it clearer what we're doing.
2019-09-02 07:11:32 +08:00
#include "netdissect-ctype.h"
libnetdissect code must include 'netdissect.h', not 'interface.h' Moreover: Remove netdissect.h include in interface.h Move thiszone declaration in netdissect.h Update a comment
2015-09-11 19:22:56 +08:00
#include "netdissect.h"
NFS: Use the EXTRACT_U_1() macro in the file handles parser
2018-01-29 05:47:48 +08:00
#include "extract.h"
Initial revision
1999-10-08 07:47:09 +08:00
#include "nfsfh.h"
/*
* This routine attempts to parse a file handle (in network byte order),
* using heuristics to guess what kind of format it is in. See the
* file "fhandle_layouts" for a detailed description of the various
* patterns we know about.
*
* The file handle is parsed into our internal representation of a
* file-system id, and an internal representation of an inode-number.
*/
#define FHT_UNKNOWN 0
#define FHT_AUSPEX 1
#define FHT_DECOSF 2
#define FHT_IRIX4 3
#define FHT_IRIX5 4
#define FHT_SUNOS3 5
#define FHT_SUNOS4 6
#define FHT_ULTRIX 7
#define FHT_VMSUCX 8
#define FHT_SUNOS5 9
#define FHT_AIX32 10
#define FHT_HPUX9 11
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
#define FHT_BSD44 12
Initial revision
1999-10-08 07:47:09 +08:00
Add the ndo parameter to some functions This parameter will be needed at the next step.
2018-06-15 21:44:51 +08:00
static int is_UCX(netdissect_options *, const unsigned char *, u_int);
Initial revision
1999-10-08 07:47:09 +08:00
void
Add the ndo parameter to some functions This parameter will be needed at the next step.
2018-06-15 21:44:51 +08:00
Parse_fh(netdissect_options *ndo, const unsigned char *fh, u_int len,
my_fsid *fsidp, uint32_t *inop,
parsenfsfh: fix old-style function definitions
2014-03-26 21:16:05 +08:00
const char **osnamep, /* if non-NULL, return OS name here */
const char **fsnamep, /* if non-NULL, return server fs name here (for VMS) */
int ourself) /* true if file handle was generated on this host */
Initial revision
1999-10-08 07:47:09 +08:00
{
Remove all storage class specifier 'register' Let the compiler do the optimizations (or not) based on build options. Avoid 'value has been optimized out' messages in gdb using '-O0'.
2017-12-14 02:17:47 +08:00
const unsigned char *fhp = fh;
u_intN_t is dead, long live uintN_t. And, as we require at least autoconf 2.61, and as autoconf 2.61 and later have AC_TYPE_UINTn_T and AC_TYPE_INTn_T macros, we use them to define the uintN_t and intN_t macros if the system doesn't define them for us. This lets us get rid of bitypes.h as well.
2014-04-23 15:20:40 +08:00
uint32_t temp;
Initial revision
1999-10-08 07:47:09 +08:00
int fhtype = FHT_UNKNOWN;
Don't overflow the Opaque_Handle buffer. The file handle length can be arbitrarily large; don't assume its hex dump will fit in the buffer, just truncate it if it doesn't.
2016-09-26 05:17:00 +08:00
u_int i;
Initial revision
1999-10-08 07:47:09 +08:00
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/*
* Require at least 16 bytes of file handle; it's variable-length
* in NFSv3. "len" is in units of 32-bit words, not bytes.
*/
if (len < 16/4)
fhtype = FHT_UNKNOWN;
else {
if (ourself) {
/* File handle generated on this host, no need for guessing */
Initial revision
1999-10-08 07:47:09 +08:00
#if defined(IRIX40)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_IRIX4;
Initial revision
1999-10-08 07:47:09 +08:00
#endif
#if defined(IRIX50)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_IRIX5;
Initial revision
1999-10-08 07:47:09 +08:00
#endif
#if defined(IRIX51)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_IRIX5;
Initial revision
1999-10-08 07:47:09 +08:00
#endif
#if defined(SUNOS4)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_SUNOS4;
Initial revision
1999-10-08 07:47:09 +08:00
#endif
#if defined(SUNOS5)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_SUNOS5;
Initial revision
1999-10-08 07:47:09 +08:00
#endif
#if defined(ultrix)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_ULTRIX;
Initial revision
1999-10-08 07:47:09 +08:00
#endif
#if defined(__osf__)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_DECOSF;
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
#endif
#if defined(__NetBSD__) || defined(__FreeBSD__) || defined(__DragonFly__) \
|| defined(__OpenBSD__)
fhtype = FHT_BSD44;
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
#endif
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
}
Initial revision
1999-10-08 07:47:09 +08:00
/*
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
* This is basically a big decision tree
Initial revision
1999-10-08 07:47:09 +08:00
*/
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
else if ((GET_U_1(fhp) == 0) && (GET_U_1(fhp + 1) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* bytes[0,1] == (0,0); rules out Ultrix, IRIX5, SUNOS5 */
/* probably rules out HP-UX, AIX unless they allow major=0 */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 2) == 0) && (GET_U_1(fhp + 3) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* bytes[2,3] == (0,0); must be Auspex */
/* XXX or could be Ultrix+MASSBUS "hp" disk? */
fhtype = FHT_AUSPEX;
Initial revision
1999-10-08 07:47:09 +08:00
}
else {
/*
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
* bytes[2,3] != (0,0); rules out Auspex, could be
* DECOSF, SUNOS4, or IRIX4
Initial revision
1999-10-08 07:47:09 +08:00
*/
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 4) != 0) && (GET_U_1(fhp + 5) == 0) &&
(GET_U_1(fhp + 8) == 12) && (GET_U_1(fhp + 9) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* seems to be DECOSF, with minor == 0 */
fhtype = FHT_DECOSF;
}
else {
/* could be SUNOS4 or IRIX4 */
/* XXX the test of fhp[5] == 8 could be wrong */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 4) == 0) && (GET_U_1(fhp + 5) == 8) && (GET_U_1(fhp + 6) == 0) &&
(GET_U_1(fhp + 7) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* looks like a length, not a file system typecode */
fhtype = FHT_IRIX4;
}
else {
/* by elimination */
fhtype = FHT_SUNOS4;
}
}
Initial revision
1999-10-08 07:47:09 +08:00
}
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
}
Initial revision
1999-10-08 07:47:09 +08:00
else {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/*
* bytes[0,1] != (0,0); rules out Auspex, IRIX4, SUNOS4
* could be IRIX5, DECOSF, UCX, Ultrix, SUNOS5
* could be AIX, HP-UX
*/
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 2) == 0) && (GET_U_1(fhp + 3) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/*
* bytes[2,3] == (0,0); rules out OSF, probably not UCX
* (unless the exported device name is just one letter!),
* could be Ultrix, IRIX5, AIX, or SUNOS5
* might be HP-UX (depends on their values for minor devs)
*/
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 6) == 0) && (GET_U_1(fhp + 7) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_BSD44;
}
/*XXX we probably only need to test of these two bytes */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
else if ((len >= 24/4) && (GET_U_1(fhp + 21) == 0) && (GET_U_1(fhp + 23) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_ULTRIX;
}
else {
/* Could be SUNOS5/IRIX5, maybe AIX */
/* XXX no obvious difference between SUNOS5 and IRIX5 */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if (GET_U_1(fhp + 9) == 10)
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_SUNOS5;
/* XXX what about AIX? */
}
Initial revision
1999-10-08 07:47:09 +08:00
}
else {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/*
* bytes[2,3] != (0,0); rules out Ultrix, could be
* DECOSF, SUNOS5, IRIX5, AIX, HP-UX, or UCX
*/
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 8) == 12) && (GET_U_1(fhp + 9) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_DECOSF;
}
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
else if ((GET_U_1(fhp + 8) == 0) && (GET_U_1(fhp + 9) == 10)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* could be SUNOS5/IRIX5, AIX, HP-UX */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
if ((GET_U_1(fhp + 7) == 0) && (GET_U_1(fhp + 6) == 0) &&
(GET_U_1(fhp + 5) == 0) && (GET_U_1(fhp + 4) == 0)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* XXX is this always true of HP-UX? */
fhtype = FHT_HPUX9;
}
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
else if (GET_U_1(fhp + 7) == 2) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/* This would be MNT_NFS on AIX, which is impossible */
fhtype = FHT_SUNOS5; /* or maybe IRIX5 */
}
else {
/*
* XXX Could be SUNOS5/IRIX5 or AIX. I don't
* XXX see any way to disambiguate these, so
* XXX I'm going with the more likely guess.
* XXX Sorry, Big Blue.
*/
fhtype = FHT_SUNOS5; /* or maybe IRIX5 */
}
}
else {
Add the ndo parameter to some functions This parameter will be needed at the next step.
2018-06-15 21:44:51 +08:00
if (is_UCX(ndo, fhp, len)) {
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
fhtype = FHT_VMSUCX;
}
else {
fhtype = FHT_UNKNOWN;
}
}
Initial revision
1999-10-08 07:47:09 +08:00
}
}
}
/* XXX still needs to handle SUNOS3 */
switch (fhtype) {
case FHT_AUSPEX:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_U_1(fhp + 7);
fsidp->Fsid_dev.Major = GET_U_1(fhp + 6);
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->fsid_code = 0;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "Auspex";
break;
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
case FHT_BSD44:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_U_1(fhp);
fsidp->Fsid_dev.Major = GET_U_1(fhp + 1);
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
fsidp->fsid_code = 0;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_LE_U_4(fhp + 12);
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
if (osnamep)
*osnamep = "BSD 4.4";
break;
Initial revision
1999-10-08 07:47:09 +08:00
case FHT_DECOSF:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->fsid_code = GET_LE_U_4(fhp + 4);
Initial revision
1999-10-08 07:47:09 +08:00
/* XXX could ignore 3 high-order bytes */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
temp = GET_LE_U_4(fhp);
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->Fsid_dev.Minor = temp & 0xFFFFF;
fsidp->Fsid_dev.Major = (temp>>20) & 0xFFF;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_LE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "OSF";
break;
case FHT_IRIX4:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_U_1(fhp + 3);
fsidp->Fsid_dev.Major = GET_U_1(fhp + 2);
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->fsid_code = 0;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 8);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "IRIX4";
break;
case FHT_IRIX5:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_BE_U_2(fhp + 2);
fsidp->Fsid_dev.Major = GET_BE_U_2(fhp);
fsidp->fsid_code = GET_BE_U_4(fhp + 4);
Use EXTRACT_ macros, don't reassemble multi-byte quantities ourselves.
2018-07-09 07:50:16 +08:00
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "IRIX5";
break;
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
#ifdef notdef
Initial revision
1999-10-08 07:47:09 +08:00
case FHT_SUNOS3:
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
/*
* XXX - none of the heuristics above return this.
* Are there any SunOS 3.x systems around to care about?
*/
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "SUNOS3";
break;
From NetBSD: revision 1.7 date: 2006/03/25 11:43:53; author: rpaulo; state: Exp; lines: +23 -3 PR 13604: detect and print correct information for 4.4BSD/NetBSD NFS filehandles. The heuristic may or may not be wrong, but no one replied in the tcpdump-workers mailing list. Extraction of the fsid information contributed by Chuck Silvers. Discussed with Chuck Silvers. ---------------------------- revision 1.6 date: 2006/03/22 04:30:28; author: christos; state: Exp; lines: +4 -2 Coverity CID 563: Kill SUNOS3 case; it is dead code. ----------------------------
2006-06-14 06:21:38 +08:00
#endif
Initial revision
1999-10-08 07:47:09 +08:00
case FHT_SUNOS4:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_U_1(fhp + 3);
fsidp->Fsid_dev.Major = GET_U_1(fhp + 2);
fsidp->fsid_code = GET_BE_U_4(fhp + 4);
Initial revision
1999-10-08 07:47:09 +08:00
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "SUNOS4";
break;
case FHT_SUNOS5:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
temp = GET_BE_U_2(fhp);
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->Fsid_dev.Major = (temp>>2) & 0x3FFF;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
temp = GET_BE_U_3(fhp + 1);
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->Fsid_dev.Minor = temp & 0x3FFFF;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->fsid_code = GET_BE_U_4(fhp + 4);
Initial revision
1999-10-08 07:47:09 +08:00
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "SUNOS5";
break;
case FHT_ULTRIX:
fsidp->fsid_code = 0;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_U_1(fhp);
fsidp->Fsid_dev.Major = GET_U_1(fhp + 1);
Initial revision
1999-10-08 07:47:09 +08:00
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
temp = GET_LE_U_4(fhp + 4);
Initial revision
1999-10-08 07:47:09 +08:00
*inop = temp;
if (osnamep)
*osnamep = "Ultrix";
break;
case FHT_VMSUCX:
/* No numeric file system ID, so hash on the device-name */
if (sizeof(*fsidp) >= 14) {
if (sizeof(*fsidp) > 14)
memset((char *)fsidp, 0, sizeof(*fsidp));
/* just use the whole thing */
Fix a bunch of de-constifications.
2015-04-27 08:24:42 +08:00
memcpy((char *)fsidp, (const char *)fh, 14);
Initial revision
1999-10-08 07:47:09 +08:00
}
else {
u_intN_t is dead, long live uintN_t. And, as we require at least autoconf 2.61, and as autoconf 2.61 and later have AC_TYPE_UINTn_T and AC_TYPE_INTn_T macros, we use them to define the uintN_t and intN_t macros if the system doesn't define them for us. This lets us get rid of bitypes.h as well.
2014-04-23 15:20:40 +08:00
uint32_t tempa[4]; /* at least 16 bytes, maybe more */
Initial revision
1999-10-08 07:47:09 +08:00
memset((char *)tempa, 0, sizeof(tempa));
Fix a bunch of de-constifications.
2015-04-27 08:24:42 +08:00
memcpy((char *)tempa, (const char *)fh, 14); /* ensure alignment */
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->Fsid_dev.Minor = tempa[0] + (tempa[1]<<1);
fsidp->Fsid_dev.Major = tempa[2] + (tempa[3]<<1);
fsidp->fsid_code = 0;
}
/* VMS file ID is: (RVN, FidHi, FidLo) */
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = (((uint32_t) GET_U_1(fhp + 26)) << 24) |
(((uint32_t) GET_U_1(fhp + 27)) << 16) |
(GET_LE_U_2(fhp + 22) << 0);
Initial revision
1999-10-08 07:47:09 +08:00
/* Caller must save (and null-terminate?) this value */
if (fsnamep)
NFS: Use the EXTRACT_U_1() macro in the file handles parser
2018-01-29 05:47:48 +08:00
*fsnamep = (const char *)(fhp + 1);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "VMS";
break;
case FHT_AIX32:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Minor = GET_BE_U_2(fhp + 2);
fsidp->Fsid_dev.Major = GET_BE_U_2(fhp);
fsidp->fsid_code = GET_BE_U_4(fhp + 4);
Use EXTRACT_ macros, don't reassemble multi-byte quantities ourselves.
2018-07-09 07:50:16 +08:00
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "AIX32";
break;
case FHT_HPUX9:
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->Fsid_dev.Major = GET_U_1(fhp);
temp = GET_BE_U_3(fhp + 1);
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->Fsid_dev.Minor = temp;
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
fsidp->fsid_code = GET_BE_U_4(fhp + 4);
Initial revision
1999-10-08 07:47:09 +08:00
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
*inop = GET_BE_U_4(fhp + 12);
Initial revision
1999-10-08 07:47:09 +08:00
if (osnamep)
*osnamep = "HPUX9";
break;
case FHT_UNKNOWN:
#ifdef DEBUG
(my_fsid): add Opaque_Handle for storing the actual filehandle. From Francisco Matias Cuenca-Acuna <mcuenca@george.rutgers.edu>
2000-06-01 09:02:15 +08:00
/* XXX debugging */
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
for (i = 0; i < len*4; i++)
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
(void)fprintf(stderr, "%x.", GET_U_1(fhp + i));
(my_fsid): add Opaque_Handle for storing the actual filehandle. From Francisco Matias Cuenca-Acuna <mcuenca@george.rutgers.edu>
2000-06-01 09:02:15 +08:00
(void)fprintf(stderr, "\n");
Initial revision
1999-10-08 07:47:09 +08:00
#endif
(my_fsid): add Opaque_Handle for storing the actual filehandle. From Francisco Matias Cuenca-Acuna <mcuenca@george.rutgers.edu>
2000-06-01 09:02:15 +08:00
/* Save the actual handle, so it can be display with -u */
Don't overflow the Opaque_Handle buffer. The file handle length can be arbitrarily large; don't assume its hex dump will fit in the buffer, just truncate it if it doesn't.
2016-09-26 05:17:00 +08:00
for (i = 0; i < len*4 && i*2 < sizeof(fsidp->Opaque_Handle) - 1; i++)
Remove more old-compiler compensation. We require an environment with a C99-compatible snprintf(), so we don't need to work around older implementations. Make the configuration process fail if we don't have snprintf() and vsnprintf(). We require at least VS 2015, so we don't have to check for _MSC_VER >= 1400. Make the build fail if we don't have at least VS 2015. We apparently do, however, have to use __inline, as the VS 2015 documentation doesn't meaning plain old "inline". Update a comment.
2019-08-09 13:39:54 +08:00
(void)snprintf(&(fsidp->Opaque_Handle[i*2]), 3, "%.2X",
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
GET_U_1(fhp + i));
Make sure the Opaque_Handle string is null-terminated. ...even if the file handle length is 0.
2016-10-19 09:33:12 +08:00
fsidp->Opaque_Handle[i*2] = '\0';
(my_fsid): add Opaque_Handle for storing the actual filehandle. From Francisco Matias Cuenca-Acuna <mcuenca@george.rutgers.edu>
2000-06-01 09:02:15 +08:00
have support for FHT_NETBSDE[LB]. maybe useful for other implementations.
2001-06-18 16:39:36 +08:00
/* XXX for now, give "bogus" values to aid debugging */
Initial revision
1999-10-08 07:47:09 +08:00
fsidp->fsid_code = 0;
fsidp->Fsid_dev.Minor = 257;
fsidp->Fsid_dev.Major = 257;
*inop = 1;
/* display will show this string instead of (257,257) */
if (fsnamep)
*fsnamep = "Unknown";
if (osnamep)
*osnamep = "Unknown";
break;
}
}
/*
* Is this a VMS UCX file handle?
* Check for:
* (1) leading code byte [XXX not yet]
* (2) followed by string of printing chars & spaces
* (3) followed by string of nulls
*/
static int
Add the ndo parameter to some functions This parameter will be needed at the next step.
2018-06-15 21:44:51 +08:00
is_UCX(netdissect_options *ndo, const unsigned char *fhp, u_int len)
Initial revision
1999-10-08 07:47:09 +08:00
{
Remove all storage class specifier 'register' Let the compiler do the optimizations (or not) based on build options. Avoid 'value has been optimized out' messages in gdb using '-O0'.
2017-12-14 02:17:47 +08:00
u_int i;
Initial revision
1999-10-08 07:47:09 +08:00
int seen_null = 0;
Don't run past the end of an NFSv3 file handle. NFSv2 file handles are always 32 bytes long, possibly with zero padding at the end. NFSv3 file handles are variable-length, however, so we cannot assume that they have any minimum number of bytes of data; check that bytes are present before looking at them.
2016-09-25 11:39:52 +08:00
/*
* Require at least 28 bytes of file handle; it's variable-length
* in NFSv3. "len" is in units of 32-bit words, not bytes.
*/
if (len < 28/4)
return(0);
Initial revision
1999-10-08 07:47:09 +08:00
for (i = 1; i < 14; i++) {
Don't use <ctype.h> macros. Some of them are locale-dependent, and all of them run the risk of failing if you hand them a char with the 8th bit set. Move our replacements to a new netdissect-ctype.h file, and, for the ones that check for particular character types, add _ASCII to the name, to indicate that only ASCII characters pass the check. Do the same for the ones that map between cases, to indicate that they only map ASCII letters. For isspace(), explicitly check for the characters we care about, to make it clearer what we're doing.
2019-09-02 07:11:32 +08:00
if (ND_ASCII_ISPRINT(GET_U_1(fhp + i))) {
Initial revision
1999-10-08 07:47:09 +08:00
if (seen_null)
return(0);
else
continue;
}
Use the new GET_ macros instead of the EXTRACT_ ones The exceptions are currently: Some EXTRACT_ in print-juniper.c, not used on packet buffer pointer. An EXTRACT_BE_U_3 in addrtoname.c, not always used on packet buffer pointer.
2018-06-16 23:23:21 +08:00
else if (GET_U_1(fhp + i) == 0) {
Initial revision
1999-10-08 07:47:09 +08:00
seen_null = 1;
continue;
}
else
return(0);
}
return(1);
}
Reference in New Issue Copy Permalink