HIPL

handle SA expiration properly

Bug #592115 reported by Miika Komu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HIPL
Confirmed
Critical
Unassigned

Bug Description

Currently SAs do not expire at all and therefore those events are not catched at all.

René Hummen (rene-hummen)
Changed in hipl:
importance: Undecided → High
importance: High → Critical
status: New → Confirmed
Revision history for this message
René Hummen (rene-hummen) wrote :

What exactly are "those events"?

In order to implement this feature, the hipd requires a mechanism to look-up the activity of SAs that have previously been set up by the daemon.

Revision history for this message
Miika Komu (miika-iki) wrote :

When the SAs are set up, they should have an expiration date. Correspondingly, the IPsec notifies about the expiration of SAs in hip_netdev_event() so that hipd can run CLOSE.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.