This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ripe-list] https://www.ripe.net/ inappropriate javascript
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Sat May 4 20:07:40 CEST 2019
to be constructive, from a message sent privately to mirjam explaining > what i meant by auditing: > > o the ncc web infrastructure incorporates elements from non-ncc > sites > > o as we learned from the youtube incident, those sites can deliver > undesirable javascript > > o if we audit manually today, we can assert we're clean today > > o but one or more of the incorporated contents could change tomorrow > and include undesirable javascript > > o ncc softeng could write code to traverse the site regularly to audit > for new javascript if i developed web sites, i would like such a tool randy
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]