Comment 9 for bug 206129

What are the security implications of this issue (if we don't alias as described above)? Is it likely that this will be fixed in Hardy soon anyway?

In case one wonders why I'm asking these questions, I have been curious since I started using Hardy about what happens when I implement a work-around for a bug that is later fixed -- potentially in a way that is not compatible with my workaround. That's a question related to the bigger picture. I plan to stay with this same installation of Hardy as I move forward, but I am collecting (implementing) various bug fixes as I use it. (Sorry to get off topic a bit.)