From: Christoph Hellwig <hch@lst.de>
To: akpm@osdl.org
Cc: netdev@oss.sgi.com
Subject: [PATCH] remove secure_ipv6_id
Date: Tue, 7 Sep 2004 17:17:53 +0200 [thread overview]
Message-ID: <20040907151753.GA9735@lst.de> (raw)
looks like the ipv6 code doesn't need this one anymore
--- 1.54/drivers/char/random.c 2004-09-03 11:08:21 +02:00
+++ edited/drivers/char/random.c 2004-09-07 15:51:23 +02:00
@@ -2279,19 +2279,7 @@
return seq;
}
EXPORT_SYMBOL(secure_tcpv6_sequence_number);
-
-__u32 secure_ipv6_id(__u32 *daddr)
-{
- struct keydata *keyptr;
-
- keyptr = check_and_rekey(get_seconds());
-
- return halfMD4Transform(daddr, keyptr->secret);
-}
-
-EXPORT_SYMBOL(secure_ipv6_id);
#endif
-
__u32 secure_tcp_sequence_number(__u32 saddr, __u32 daddr,
__u16 sport, __u16 dport)
--- 1.3/include/linux/random.h 2003-09-21 23:50:34 +02:00
+++ edited/include/linux/random.h 2004-09-07 14:07:58 +02:00
@@ -67,8 +67,6 @@
extern __u32 secure_tcpv6_sequence_number(__u32 *saddr, __u32 *daddr,
__u16 sport, __u16 dport);
-extern __u32 secure_ipv6_id(__u32 *daddr);
-
#ifndef MODULE
extern struct file_operations random_fops, urandom_fops;
#endif
reply other threads:[~2004-09-07 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040907151753.GA9735@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).