aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Sharpe <sharpe@ns.aus.com>2002-12-25 20:58:06 +0000
committerRichard Sharpe <sharpe@ns.aus.com>2002-12-25 20:58:06 +0000
commitbdf14fc80e961ff5324dc9ee8964769633364136 (patch)
tree52f8edc9b9605a269407862b08cb18ceb23b42fe
parent4f02b606b3d5708fb1a5cc9c152ef6ab488df28b (diff)
Minor spelling etc updates.
svn path=/trunk/; revision=6816
-rw-r--r--packet-spnego.c11
1 files changed, 5 insertions, 6 deletions
diff --git a/packet-spnego.c b/packet-spnego.c
index 15db9e6a0b..d67192d582 100644
--- a/packet-spnego.c
+++ b/packet-spnego.c
@@ -4,7 +4,7 @@
* Copyright 2002, Tim Potter <tpot@samba.org>
* Copyright 2002, Richard Sharpe <rsharpe@ns.aus.com>
*
- * $Id: packet-spnego.c,v 1.39 2002/11/28 06:48:42 guy Exp $
+ * $Id: packet-spnego.c,v 1.40 2002/12/25 20:58:06 sharpe Exp $
*
* Ethereal - Network traffic analyzer
* By Gerald Combs <gerald@ethereal.com>
@@ -115,14 +115,13 @@ dissect_parse_error(tvbuff_t *tvb, int offset, packet_info *pinfo,
/*
* This is the SPNEGO KRB5 dissector. It is not true KRB5, but some ASN.1
- * wrapped blob with an OID, Boolean, and a Ticket, that is also ASN.1 wrapped
- * by the looks of it.
+ * wrapped blob with an OID, USHORT token ID, and a Ticket, that is also
+ * ASN.1 wrapped by the looks of it. It conforms to RFC1964.
*/
#define KRB_TOKEN_AP_REQ 0x0001
#define KRB_TOKEN_AP_REP 0x0002
#define KRB_TOKEN_AP_ERR 0x0003
-#define KRB_TOKEN_AP_ERR 0x0003
#define KRB_TOKEN_GETMIC 0x0101
#define KRB_TOKEN_WRAP 0x0102
#define KRB_TOKEN_DELETE_SEC_CONTEXT 0x0201
@@ -191,10 +190,10 @@ dissect_spnego_krb5(tvbuff_t *tvb, packet_info *pinfo, proto_tree *tree)
* The KRB5 blob conforms to RFC1964:
* [APPLICATION 0] {
* OID,
- * USHORT (0x0001 == AP-REQ, 0x0002 == AP-REP, 0x0003 == ERROR,
+ * USHORT (0x0001 == AP-REQ, 0x0002 == AP-REP, 0x0003 == ERROR),
* OCTET STRING }
*
- * However, for some protocols, the KRB5 blob stars at the SHORT
+ * However, for some protocols, the KRB5 blob starts at the SHORT
* and has no DER encoded header etc.
*
* It appears that for some other protocols the KRB5 blob is just