(Lawrence, KS) Haskell Men'sTrack begin it's 2013 Track season with an Indoor meet hosted by JCCC. The meet took place Friday January 11^th at 4:00pm in Overland Park.

Article By: Enoch Kaulaity

The Haskell Men's  indoor track and field season got off with a visit up the road earlier this month and competed in the Cavalier Relays on January 16, 2015, and a repeat return for the Cavalier Night Relays which took place this past Friday, January 30th on the campus of Johnson County Community College.

Cadence is hosting a Front End Design Summit on Thursday, December 6, 2012 9:30am – 5:00pm at Cadence San Jose headquarters, 2655 Seely Avenue, Building 10. Logic designers will hear from customers including Cisco, Chelsio, PMC, Spansion, and Via Technologies...(read more)

How to use Encounter® RTL Compiler support Interface Logic Models during synthesis.(read more)

کورونا کی وبا کی ہولناکیوں کے پیش نظر، جمعیۃ علماء ہند کی جیلوں میں قید قیدیوں، جن کی سزا 7 سال سےکم ہے اورجو ان کے زیرکفالت ہیں، کی مشروط ضمانت کے لئےمعزز سپریم کورٹ میں درخواست دائرکریں گے۔

No Starch Press: $49.95

If you are a security engineer, a researcher, a hacker or just someone who keeps your ear to the ground when it comes to computer security, chances are you have seen the name Michal Zalewski. He has been responsible for an abundance of tools, research, proof of concepts and helpful insight to many over the years. He recently released a book called "The Tangled Web - A Guide To Securing Modern Web Applications".

Normally, when I read books about securing web applications, I find many parallels where authors will give an initial lay of the land, dictating what technologies they will address, what programming languages they will encompass and a decent amount of detail on vulnerabilities that exist along with some remediation tactics. Such books are invaluable for people in this line of work, but there is a bigger picture that needs to be addressed and it includes quite a bit of secret knowledge rarely divulged in the security community. You hear it in passing conversation over beers with colleagues or discover it through random tests on your own. But rarely are the oddities documented anywhere in a thorough manner.

Before we go any further, let us take a step back in time. Well over a decade ago, the web was still in its infancy and an amusing vulnerability known as the phf exploit surfaced. It was nothing more than a simple input validation bug that resulted in arbitrary code execution. The average hacker enjoyed this (and many more bugs like it) during this golden age. At the time, developers of web applications had a hard enough time getting their code to work and rarely took security implications into account. Years later, cross site scripting was discovered and there was much debate about whether or not a cross site scripting vulnerability was that important. After all, it was an issue that restricted itself to the web ecosystem and did not give us a shell on the server. Rhetoric on mailing lists mocked such findings and we (Packet Storm) received many emails saying that by archiving these issues we were degrading the quality of the site. But as the web evolved, people starting banking online, their credit records were online and before you knew it, people were checking their social network updates on their phone every five minutes. All of a sudden, something as small as a cross site scripting vulnerability mattered greatly.

To make the situation worse, many programs were developed to support web-related technologies. In the corporate world, being first to market or putting out a new feature in a timely fashion trumphs security. Backwards compatibility that feeds poor design became a must for any of the larger browser vendors. The "browser wars" began and everyone had different ideas on how to solve different issues. To say web-related technologies brought many levels of complexity to the modern computing experience is a great understatement. Browser-side programming languages, such as JavaScript, became a playground for hackers. Understanding the Document Object Model (DOM) and the implications of poorly coded applications became one of those lunch discussions that could cause you to put your face into your mashed potatoes. Enter "The Tangled Web".

This book puts some very complicated nuances in plain (enough) english. It starts out with Zalewski giving a brief synopsis of the security industry and the web. Breakdowns of the basics are provided and it is written in a way that is inviting for anyone to read. It goes on to cover a wide array of topics inclusive to the operation of browsers, the protocols involved, the various types of documents handled and the languages supported. Armed with this knowledge, the reader is enabled to tackle the next section detailing browser security features. As the author puts it, it covers "everything from the well-known but often misunderstood same-origin policy to the obscure and proprietary zone settings of Internet Explorer". Browsers, it ends up, have a ridiculous amount of odd dynamics for even the simplest acts. The last section wraps things up with upcoming security features and various browser mechanisms to note.

I found it a credit to the diversity of the book that technical discussion could also trail off to give historical notes on poor industry behavior. When it noted DNS hijacking by various providers it reminded me of the very distinct and constantly apparent disconnect between business and knowledge of technology. When noting how non-HTTP servers were being leveraged to commit cross site scripting attacks, Zalewski also made it a point to note how the Internet Explorer releases only have a handful of prohibited ports but all other browsers have dozens that they block. The delicate balance of understanding alongside context is vital when using information from this book and applying it to design.

Every page offers some bit of interesting knowledge that dives deep. It takes the time to note the odd behaviors small mistakes can cause and also points out where flawed security implementations exist. This book touches on the old and the new and many things other security books have overlooked. Another nice addition is that it provides security engineering cheatsheets at the end of each chapter. To be thorough, it explains both the initiatives set out by RFCs while it also documents different paths various browser vendors have taken in tackling tricky security issues. Google's Chrome, Mozilla's Firefox, Microsoft's Internet Explorer, Apple's Safari and Opera are compared and contrasted greatly throughout this book.

In my opinion, the web has become a layer cake over the years. New shiny technologies and add-ons have been thrown into the user experience and with each of them comes a new set of security implications. One-off findings are constantly discovered and documented (and at Packet Storm we try to archive every one of them), but this is the first time I have seen a comprehensive guide that focuses on everything from cross-domain content inclusion to content-sniffing. It is the sort of book that should be required reading for every web developer.

 -Todd

Over 95 percent of climate scientists have concluded that CO2 is the primary cause of global warming. Solving the problem requires a dramatic reduction in CO2 emissions. Some people are altruistic, but almost all businesses are bottom line oriented and will not reduce their CO2 emissions unless they have an economic incentive to do so. There are two realistic incentives: taxing CO2 emissions or setting up a cap and trade program for CO2. Since increasing taxes is politically unfeasible, the most practical approach is with a cap and trade program.

The news about the Environmental Protection Agency’s plan to limit carbon pollution from existing power plants just got even better: the proposed Clean Power Plan (CPP) can save the power industry and its customers — us — as much as $2 to $4 billion in 2020 and $6 to 9 billion in 2030, while cleaning our air and modernizing the electricity sector.

The Western States Petroleum Association (WSPA) — whose members include Chevron, ExxonMobil, Shell, ConocoPhillips, BP, and others — was caught red-handed late last month when a leaked internal presentation revealed a coordinated campaign to stomp out climate and clean energy progress in California, Oregon and Washington by propping up over 15 front groups that purport to represent the views of concerned citizens and the broader business community.

Shinzo Abe’s re-election as prime minister risks undercutting Japan’s commitment to clean energy at a time when incentives are under review and the nation’s utilities say they can’t accommodate capacity already planned.

The U.S. Department of Commerce just announced that it will add high tariffs for solar modules imported from China. The Canadian government is also investigating the adoption of similar measures, following recent complaints filed by Ontario-based solar manufacturers. With the solar industry in hypergrowth, it’s not a surprise that these governments are interested in boosting new jobs, protecting their economies, and fostering the solar sector. The problem is that tariffs are a short-sighted approach that actually attack the future of North American solar on its home soil, and likely destroy more jobs than they create.