Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tav
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
25 ms
·
181.
▲
by
tav
17y ago
Nice work! It's very useful for app developers on platforms like App Engine which don't provide a server-side DNS API. Is http://dig.jsondns.org for demonstration only or can we use that as an official deployment to use in our apps? Thank
182.
▲
Ciao Python, Hola Go
(tav.espians.com)
46 points
by
tav
17y ago
|
34 comments
183.
▲
by
tav
17y ago
Good points. I was imagining a scenario in which users/other-app-providers would be able to define their own Javascript functions, Google Caja http://code.google.com/p/google-caja/ style... in which case, the app should simply only need t
184.
▲
by
tav
17y ago
Sure, that's why one should only add hosts/base urls which one trusts, e.g. http://github.com/api/json/ http://api.twitter.com/json/ But with what you suggest, then you would've to keep a lot more state -- i.e. knowing beforehand
185.
▲
by
tav
17y ago
Nice one Drew!
186.
▲
by
tav
17y ago
If I understand it right, you're suggesting limiting it to just an <identifier> ? I agree and if we would all standardise on just that it'd fine by me... But, having said that, array_of_functions[index] is also a common pattern that
187.
▲
by
tav
17y ago
Whitelist the trusted sources =)
188.
▲
by
tav
17y ago
also, cross-posted from the comments there: Hey Philip, You are right, the code is executed in the context of the CALLERs page. But that is the problem... Imagine the scenario, where a client-side web application allows arbitrary data sourc
189.
▲
Sanitising JSON callback identifiers for security — a must for web developers
(tav.espians.com)
18 points
by
tav
17y ago
|
15 comments
190.
▲
Top Life Tips: #10
(tav.espians.com)
1 points
by
tav
18y ago
|
0 comments
191.
▲
Update on Securing the Python Interpreter (Capabilities)
(tav.espians.com)
1 points
by
tav
18y ago
|
0 comments
192.
▲
by
tav
18y ago
@sah Nice! Sadly it wouldn't ever fly in the Python context, but I like it nevertheless!
193.
▲
by
tav
18y ago
@lacker I did mail python-dev, but wanted to get general public criticism too...
194.
▲
by
tav
18y ago
@jackdied that's brilliant advice!! thank you -- will bear in mind for the future.
195.
▲
Ruby-style Blocks in Python
(tav.espians.com)
46 points
by
tav
18y ago
|
42 comments
196.
▲
by
tav
18y ago
I'd be really interested to know if any of you guys manage to find further exploits. Thanks!!
197.
▲
by
tav
18y ago
http://duckduckgo.com/?q=pw