Thank You so much for your quick reply, although I wish it wasn’t so depressing! I don’t think I helped myself by failing to keep a copy of the security information form - I’ve just requested a new one and was intending to return it to Abbey by fax, in line with what they suggested to both of us. However, reading of your experience, I have the mind to phone them up again and demand that they set up my online access over the phone. What an (ongoing) struggle! :p

I waited and waited but it never got sorted out. In the end I had to ring them and they insisted I fax them my security details again. I did this. Two more times. They lost them every time.

In the end after 3 weeks of no access I demanded they set it over the phone. They still got my mother’s maiden name wrong so if that security question comes up I have to reload. I’d rather do that than have to deal with the simians from Abbey again.

I think you’re going to have to phone them. Good luck.

I came across this posting after googling “ANIB JSP Diagnostic Page” - I am receiving the exact same error as you describe above when I try to log onto my Abbey business account. It has been around two weeks since I returned the form detailing my security information, so maybe something is amiss. May I ask how long after returning your form it was before you were able to access your account online? Did you have to do anything to resolve the problem?

Many Thanks for your reply

that aside, I think only rPath has actually bothered to fix the pygrub exploit, at least I didnt find much further references. There’s a long way to go for pygrub anyway, it’ll be interesting to see if the other grub features like tftp support or trusted grub extensions will go in at some point.

About the exploits nature, let’s just say pygrub was very eager to execute domu:/boot/grub/menu.lst, so instructions could be crafted to run in dom0, without using overflows or such.

for shared hosting scenarios this is an obvious nightmare

1.1A at idle is ludicrous though.