From 979ed3058b4ac4e3abcf90e6bcba5966b4e4222d Mon Sep 17 00:00:00 2001
From: Ian Young <ian@iay.org.uk>
Date: Mon, 5 May 2014 12:27:13 +0000
Subject: [PATCH] Bugzilla 1039: no longer need to blacklist one entity because
 the one it clashed with no longer appears in eduGAIN metadata. It's still in
 the *verification* blacklist because it has a 1024-bit key.

---
 mdx/uk/blacklist.xml | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/mdx/uk/blacklist.xml b/mdx/uk/blacklist.xml
index 67f09f4b..a07f3c75 100644
--- a/mdx/uk/blacklist.xml
+++ b/mdx/uk/blacklist.xml
@@ -25,17 +25,6 @@
     -->
     <util:set id="importEntityBlacklist">
         
-        <!--
-            Problems in int_edugain metadata updated 2013-09-10.
-        -->
-        <!--
-            Duplicate IdP display names.
-            
-            If we left this to normal processing, both entities would be rejected.
-            By blacklisting one, we allow the other to be processed normally.
-        -->
-        <value>https://lu-idp.lu.lv</value>
-        
         <!--
             Temporary mitigation of Heartbleed vulnerability 2014-04-16 (Bugzilla 1098).