@Dan: You were on my ignore list, which meant I never saw your exploit (I
interact with launchpad via email). I only saw it when Jason mentioned it in a
post of his. If I had seen it earlier, I would have attempted to fix it. See
for instance my posts asking Jason for news on an updated exploit.
And for someone not trying to pick a fight, you certainly succeeded.
"it's easier to do something properly
from the beginning than to patch a broken implementation one exploit at
a time."
Now if only we had a working time travel machine. Given that in the now we
have a broken implementation, our options are:
1) Try to fix it, one exploit at a time.
2) Re-write it from scratch. Since the only one volunteering to do any
re-writing was me, I don't see how that would have improved matters at all.
@Dan: You were on my ignore list, which meant I never saw your exploit (I
interact with launchpad via email). I only saw it when Jason mentioned it in a
post of his. If I had seen it earlier, I would have attempted to fix it. See
for instance my posts asking Jason for news on an updated exploit.
And for someone not trying to pick a fight, you certainly succeeded.
"it's easier to do something properly
from the beginning than to patch a broken implementation one exploit at
a time."
Now if only we had a working time travel machine. Given that in the now we
have a broken implementation, our options are:
1) Try to fix it, one exploit at a time.
2) Re-write it from scratch. Since the only one volunteering to do any
re-writing was me, I don't see how that would have improved matters at all.