Search results for all lists

10000 messages found
Sort by
List: tacomaart@list.cityoftacoma.org
From: Miles Styer
 
Looking for Mother's Day Fun? Visit PAG Sunday 11AM-4PM
Fri, May 6, 2022 10:13 PM
Walk through the Proctor District and pay us a visit. We will be open for the holiday from 11AM to 4PM. [image: Facebook] <https://proctorart.us15.list-manage.com/track/click?u=16195314e1f03e031f5886b34&id=08e24ef28c&e=a15404276d> Facebook <https://proctorart.us15.list-manage.com/track/click?
List: websecurity@lists.webappsec.org
From: DefenseCode
 
[WEB SECURITY] DefenseCode ThunderScan SAST Advisory: WordPress Top-10 Plugin SQL Injection Security Vulnerability
Mon, Dec 18, 2017 8:55 PM
Homepage: https://wordpress.org/plugins/Top-10/ https://webberzone.com/plugins/Top-10/ 3. Vulnerability Description ============================ During the security analysis, ThunderScan discovered SQL injection vulnerability in Top-10 WordPress plugin.
List: websecurity@lists.webappsec.org
From: MustLive
 
Re: [WEB SECURITY] How are you tackling CSRF?
Wed, Apr 27, 2011 1:06 AM
More here: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet Jim Manico On Apr 23, 2011, at 3:59 PM, "MustLive" wrote: 2. Protecting only POST requests with tokens, but not GET. It looks like some web developers are lazy (or it's hard for them) to add tokens to GET requests.
List: time-nuts@lists.febo.com
From: ken johnson
 
Re: [time-nuts] saving Lady Heather set-up?
Sat, Jan 18, 2014 7:03 AM
. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
List: wasc-wafec@lists.webappsec.org
From: Ryan Barnett
 
Re: [WASC-WAFEC] IronBee -- a new Apache-licensed web application firewall
Wed, Feb 23, 2011 1:05 PM
The definition on the WASC Glossary page (http://projects.webappsec.org/w/page/13246967/The-Web-Security-Glossary) could use some updating - "Web Application Firewall: An intermediary device, sitting between a web-client and a web server, analyzing OSI Layer-7 messages for violations in the programmed security policy.
List: birdalert@ontbirds.ca
From: George Prieksaitis
 
Re: [Ontbirds] Western Tanager, Port Hope - May 7
Mon, May 7, 2018 8:40 PM
Send bird reports to birdalert@ontbirds.ca For information about ONTBIRDS including how to unsubscribe visit http://www.ofo.ca/site/page/view/information.ontbirdssetup Posting guidelines can be found at http://www.ofo.ca/site/page/view/information.ontbirdsguide Visit the OFO Facebook page https://www.facebook.com/OntarioFieldOrnithologists _________________
List: ctbirds@lists.ctbirding.org
From: Aidan Kiley
 
Re: [CT Birds] John Ogren has shared an eBird checklist with you from Plum Bank Marsh/ Back River Old Saybrook, CT on Aug 17, 2020 - 12:00 PM
Mon, Aug 17, 2020 5:35 PM
visit > http://lists.ctbirding.org/mailman/listinfo/ctbirds_lists.ctbirding.org >
List: websecurity@lists.webappsec.org
From: 孙松柏
 
[WEB SECURITY] which is the best web application vulnerability scanner
Tue, May 3, 2011 2:22 AM
which is the best web application vulnerability scanner .among the free software like Arachni JBrofuzz Webshag Websecurify Zero Day Scan Nikto Wapiti W3AF Skipfish Grendel-Scan Grabber Arachni wikto may be sth more and support server client mode. FIT1-213 Department of Computer Science Tsinghua University, Beijing, 100084 http://about.me/anakin/bio
List: birdalert@ontbirds.ca
From: Stu Mackenzie
 
[Ontbirds] Long Point Update - American Avocet, Loggerhead Shrike
Tue, Sep 6, 2011 9:57 PM
targetpg=lpbosight&lang=EN> &lang=EN .Some highlights from this fall so far include American Avocet and Loggerhead Shrike! Please send any noteworthy bird sightings in the Long Point area to lpbo@birdscanada.org or share them with LPBO through E-bird www.ebird.ca username: Long Point.
List: websecurity@lists.webappsec.org
From: super evr
 
Re: [WEB SECURITY] WAF testing
Sun, Oct 9, 2011 12:57 AM
I would say that a real world way to test a WAF is to test a web application first. Then, put the Web Application Firewall in front of it, then test again. This time, If you can't find any of the vulnerabilities that you found before then the WAF is probably doing an ok job.