Import wildcards harmful?
| Newsgroups | gmane.comp.lang.e.general |
|---|---|
| Message-ID | <[email protected]> |
Hi folks, I am wondering if import wildcards (and, more generally, any import mechanism that grants the servant module the ability to insert things into the client's namespace) is inherently unsafe. In Joe-E, assume that I wrote code to do -- import com.good.*; import com.evil.*; x = new Foo(); // comes from Good.com If there also existed a "com.evil.Foo", the Java compiler would flag this as an error. However, if Good.com dropped support for "com.good.Foo", and Evil.com caught wind of that and quickly rolled out their own "com.evil.Foo", there could be a window of time when instances of my code "in the wild" would be vulnerable to the resulting substitution attack. How does that map to the threat model of Joe-E? Is it a concern? Should Joe-E reject all import wildcards? Ihab -- Ihab A.B. Awad, Palo Alto, CA _______________________________________________ e-lang mailing list [email protected] http://www.eros-os.org/mailman/listinfo/e-lang