netdev - [IPSEC] confused about IPSEC_MANUAL_REQID

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Sep 2008 13:00:25 +0200
From:	"Zsolt SZALAI" <zs.szalai@...il.com>
To:	netdev@...r.kernel.org
Subject: [IPSEC] confused about IPSEC_MANUAL_REQID_MAX

Hi!

ipsec.h defines IPSEC_MANUAL_REQID_MAX as 0x3fff (16383) and only
af_key.c, the PF_KEY implementation uses that. When configuring a
policy with a higher reqid, the kernel drops the manually given reqid
and generates a new one.
Contrarily, XFRM allows one to create policies with higher reqid-s and
this is some inconsistency i guess.
I could not find any note on generating reqids in the pf_key rfc. From
where is that come from? Is it really necessary?

As XFRM allows, is it safe to increase this value or even bypass the
checking of the reqid beeing higher than that?

Thanks,
Zsolt Szalai
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html