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  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, 08 Apr 2014 20:26:37 +0200
From:	Heiner Kallweit <heiner.kallweit@....de>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: ipv6: Should inet6_addr_del consider IFA_F_MANAGETEMPADDR?

I stumbled accross the fact that inet6_addr_add as well as inet6_addr_modify
consider IFA_F_TEMPORARY whilst inet6_addr_del does not.

My understanding of IFA_F_MANAGETEMPADDR is that it allows userspace applications
to deal with temporary addresses w/o having to create / track (and possibly delete)
each and every temporary address.

This works fine when creating / modifying a global address. However when a
global address is deleted the orphaned temporary addresses remain.
Shouldn't the userspace be able to set IFA_F_MANAGETEMPADDR also for RTM_DELADDR
to signalize that the kernel should delete all related temporary addresses as well?

It would be a rather small extension to manage_tempaddrs to add a "delete" parameter
and set valid_lft=prefered_lft=0 for each temporary address if set.

Sorry if this was discussed before and I miss something.

Rgds,
Heiner

--
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

Powered by blists - more mailing lists