text:
Printed from https://ideas.repec.org/e/pbl128.html
Don Blayney
First Name: Don
Last Name: Blayney
RePEc Short-ID: pbl128
[This author has chosen not to make the email address public]
Agricultural Economics and Agricultural Business
Las Cruces, New Mexico (United States)
http://www.aeab.nmsu.edu/
RePEc:edi:aenmsus (more details at EDIRC)
Jump to: Working papers Articles
C., Apar G. & Ghimire, Rajan & Blayney, Don & Acharya, Ram N., 2018. "Feasibility of Using Cover Crops to Enhance Soil Organic Matter and Crop Yield in New Mexico," 2018 Annual Meeting, February 2-6, 2018, Jacksonville, Florida 266735, Southern Agricultural Economics Association.
Manzamasso, Hodjo & Acharya, Ram N. & Blayney, Don P., 2016. "Corn and Rice Yield and Acreage Response to Prices, Policy and Climate Factors in Togo," 2016 Annual Meeting, February 6-9, 2016, San Antonio, Texas 230082, Southern Agricultural Economics Association.
Hahn, William F & Stewart, Hayden & Blayney, Donald P & Davis, Christopher G., 2015. "Modeling Price Transmission between Farm and Retail Prices: A Soft Switches Approach," 2015 AAEA & WAEA Joint Annual Meeting, July 26-28, San Francisco, California 204951, Agricultural and Applied Economics Association.
William Hahn & Hayden Stewart & Donald P. Blayney & Christopher G. Davis, 2016. "Modeling price transmission between farm and retail prices: a soft switches approach," Agricultural Economics, International Association of Agricultural Economists, vol. 47(2), pages 193-203, March.
Jones, Keithly G. & Blayney, Donald P., 2012. "Implications of the South Korea-U.S. Free Trade Agreement on South Korean Dairy Product Imports," 2012 Annual Meeting, August 12-14, 2012, Seattle, Washington 124823, Agricultural and Applied Economics Association.
Davis, Christopher G. & Dong, Diansheng & Blayney, Donald P. & Owens, Ashley, 2010. "An Analysis of U.S. Household Dairy Demand," Technical Bulletins 184308, United States Department of Agriculture, Economic Research Service.
Sauer, Johannes & Nehring, Richard F. & Gillespie, Jeffrey M. & Morrison Paul, Catherine J. & Blayney, Donald P. & Hallahan, Charles B. & Latruffe, Laure, 2010. "Determining the Competitive Edge: Diversified Dairy Production Systems in the United States and the European Union," 2010 Annual Meeting, July 25-27, 2010, Denver, Colorado 61149, Agricultural and Applied Economics Association.
Stewart, Hayden & Blayney, Donald P., 2010. "Retail Dairy Prices Fluctuate with the Farm Value of Milk," 2010 Annual Meeting, July 25-27, 2010, Denver, Colorado 60947, Agricultural and Applied Economics Association.
Stewart, Hayden & Blayney, Donald P., 2009. "Retail Dairy Prices Fluctuate With Farm Value of Milk," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, pages 1-1, December.
Stewart, Hayden & Blayney, Donald P., 2011. "Retail Dairy Prices Fluctuate with the Farm Value of Milk," Agricultural and Resource Economics Review, Northeastern Agricultural and Resource Economics Association, vol. 40(2), pages 1-17, August.
Stewart, Hayden & Don, P. Blayney, 2011. "Retail Dairy Prices Fluctuate with the Farm Value of Milk," Agricultural and Resource Economics Review, Cambridge University Press, vol. 40(2), pages 201-217, September.
Davis, Chris & Blayney, Don & Yen, Steven & Cooper, Joseph C., 2009. "An analysis of at-home demand for ice cream in the United States," MPRA Paper 24782, University Library of Munich, Germany.
Davis, Christopher G. & Blayney, Donald P. & Cooper, Joseph C. & Yen, Steven T., 2009. "An Analysis of Demand Elasticities for Fluid Milk Products in the U.S," 2009 Conference, August 16-22, 2009, Beijing, China 51791, International Association of Agricultural Economists.
Ollinger, Michael & Nguyen, Sang V. & Blayney, Donald P. & Chambers, William & Nelson, Kenneth B., 2006. "Food Industry Mergers and Acquisitions Lead to Higher Labor Productivity," Economic Research Report 7246, United States Department of Agriculture, Economic Research Service.
Blayney, Donald P. & Gehlhar, Mark J. & Bolling, H. Christine & Jones, Keithly G. & Langley, Suchada V. & Normile, Mary Anne & Somwaru, Agapi, 2006. "U.S. Dairy at a Global Crossroads," Economic Research Report 7209, United States Department of Agriculture, Economic Research Service.
Ollinger, Michael & Nguyen, Sang V. & Blayney, Donald P. & Chambers, William & Nelson, Kenneth B., 2005. "Structural Change in the Meat, Poultry, Dairy and Grain Processing Industries," Economic Research Report 7217, United States Department of Agriculture, Economic Research Service.
Ollinger, Michael & Nguyen, Sang V. & Blayney, Donald P. & Chambers, William & Nelson, Kenneth B., 2005. "Effect of Food Industry Mergers and Acquisitions on Employment and Wages," Economic Research Report 7250, United States Department of Agriculture, Economic Research Service.
Blayney, Donald P., 2004. "The Changing Landscape of U.S. Milk Production," Statistical Bulletin 262277, United States Department of Agriculture, Economic Research Service.
Jones, Keithly G. & Blayney, Donald P., 2004. "Evaluating Trade Developments in Dairy Products," 2004 Annual Meeting, February 14-18, 2004, Tulsa, Oklahoma 34696, Southern Agricultural Economics Association.
Langley, Suchada V. & Blayney, Donald P. & Stout, Jim & Somwaru, Agapi & Normile, Mary Anne & Miller, James J. & Stillman, Richard, 2003. "A Trade Liberalization In International Dairy Markets," 2003 Annual meeting, July 27-30, Montreal, Canada 21997, American Agricultural Economics Association (New Name 2008: Agricultural and Applied Economics Association).
Huang, Kuo S. & Blayney, Donald P., 2003. "How Dairy Price Changes Influence The Consumers' Welfare," 2003 Annual meeting, July 27-30, Montreal, Canada 22031, American Agricultural Economics Association (New Name 2008: Agricultural and Applied Economics Association).
Manchester, Alden C. & Blayney, Donald P., 2001. "Milk Pricing In The United States," Agricultural Information Bulletins 33612, United States Department of Agriculture, Economic Research Service.
Blisard, Noel & Blayney, Donald P. & Chandran, Ram & Allshouse, Jane E., 1999. "Analyses of Generic Dairy Advertising, 1984-97," Technical Bulletins 33554, United States Department of Agriculture, Economic Research Service.
Manchester, Alden C. & Blayney, Donald P., 1997. "Structure of Dairy Markets: Past, Present, Future," Agricultural Economic Reports 33929, United States Department of Agriculture, Economic Research Service.
Stillman, Richard & Blayney, Donald P. & Miller, James J. & Crawford, Terry L., 1996. "The U.S. Dairy Industry," Proceedings of the 2nd Agricultural and Food Policy Systems Information Workshop, 1996: Understanding Canada\United States Dairy Disputes 16951, Farm Foundation, Agricultural and Food Policy Systems Information Workshops.
Blayney, Donald & Miller, James & Stillman, Richard, 1995. "Dairy: Background for 1995 Farm Legislation," Agricultural Economic Reports 262021, United States Department of Agriculture, Economic Research Service.
Blayney, Don P., 1994. "Economic Models for Dairy Policy Analysis: Issues and Applications, A Workshop Proceedings," Staff Reports 278742, United States Department of Agriculture, Economic Research Service.
Kaiser, Harry M. & Blayney, Donald P., 1993. "A Survey Of Economic Models Of The Dairy Industry," Research Bulletins 123009, Cornell University, Department of Applied Economics and Management.
Blayney, Don P. & Fallert, Richard, 1990. "The World Dairy Market--Government Intervention and Multilateral Policy Reform," Staff Reports 278345, United States Department of Agriculture, Economic Research Service.
Blayney, Don P. & Fallert, Richard F., 1990. "Biotechnology and Agriculture: Emergence of Bovine Somatotropin (bST)," Staff Reports 278330, United States Department of Agriculture, Economic Research Service.
Fallert, Richard F. & Blayney, Don P. & Miller, James J., 1990. "Dairy: Background for 1990 Farm Legislation," Staff Reports 278854, United States Department of Agriculture, Economic Research Service.
Blayney, Don & Mittlehammer, Ron C., 1986. "On Aggregate Notions Of Shephard'S And Hotelling'S Lemmas," 1986 Annual Meeting, July 27-30, Reno, Nevada 278075, American Agricultural Economics Association (New Name 2008: Agricultural and Applied Economics Association).
Blayney, Don & Marousek, Gerald, 1980. "A Statistical Approach for Identifying Socioeconomic Structure in Rural Communities," 1980 Annual Meeting, July 27-30, Urbana-Champaign, Illinois 278899, American Agricultural Economics Association (New Name 2008: Agricultural and Applied Economics Association).
Blayney, Don P. & Crawford, Terry L. & Davis, Christopher G., 2016. "Dairy Export Markets: Changing the Structure of US Dairy Demand," International Food and Agribusiness Management Review, International Food and Agribusiness Management Association, vol. 19(B), pages 1-18, August.
Burdine, Kenneth H. & Kusunose, Yoko & Maynard, Leigh J. & Blayney, Donald P. & Mosheim, Roberto, 2014. "Livestock Gross Margin–Dairy: An Assessment of Its Effectiveness as a Risk Management Tool and Its Potential to Induce Supply Expansion," Journal of Agricultural and Applied Economics, Southern Agricultural Economics Association, vol. 46(2), pages 1-12, May.
Blayney, Donald & Mosheim, Roberto, 2014. "Livestock Gross Margin-Dairy—an Effective Risk Management Tool?," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, issue 02, pages 1-1, March.
Burdine, Kenneth H. & Kusunose, Yoko & Maynard, Leigh J. & Blayney, Don P. & Mosheim, Roberto, 2014. "Livestock Gross Margin–Dairy: An Assessment of Its Effectiveness as a Risk Management Tool and Its Potential to Induce Supply Expansion," Journal of Agricultural and Applied Economics, Cambridge University Press, vol. 46(2), pages 245-256, May.
Kiethly G. Jones & Don Blayney, 2014. "Assessing Changes in Dairy Product Import Demand: The Case of South Korea with Implementation of the KORUS FTA," Agribusiness, John Wiley & Sons, Ltd., vol. 30(1), pages 74-84, January.
D'Antoni, Jeremy M. & Mishra, Ashok K. & Blayney, Donald, 2013. "Assessing participation in the Milk Income Loss Contract program and its impact on milk production," Journal of Policy Modeling, Elsevier, vol. 35(2), pages 243-254.
D'Antoni, Jeremy M. & Mishra, Ashok K., 2011. "Assessing Participation in the Milk Income Loss Contract Program and its Impact on Milk Production," 2011 Annual Meeting, July 24-26, 2011, Pittsburgh, Pennsylvania 103775, Agricultural and Applied Economics Association.
Jean C. Buzby & L. Hannah Gould & Magdalena E. Kendall & Timothy F. Jones & Trisha Robinson & Don P. Blayney, 2013. "Characteristics of Consumers of Unpasteurized Milk in the United States," Journal of Consumer Affairs, Wiley Blackwell, vol. 47(1), pages 153-166, April.
Davis, Christopher G. & Dong, Diansheng & Blayney, Donald P. & Yen, Steven T. & Stillman, Richard, 2012. "U.S. Fluid Milk Demand: A Disaggregated Approach," International Food and Agribusiness Management Review, International Food and Agribusiness Management Association, vol. 15(1), pages 1-26, February.
Blayney, Donald P. & Stewart, Hayden, 2012. "Retail Dairy Prices Respond Differently to Farm Milk Price Shocks," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, issue 03, pages 1-4, September.
Davis, Christopher G. & Blayney, Donald P. & Dong, Diansheng & Yen, Steven T. & Johnson, Rachel J., 2011. "Will Changing Demographics Affect U.S. Cheese Demand?," Journal of Agricultural and Applied Economics, Southern Agricultural Economics Association, vol. 43(2), pages 1-15, May.
Davis, Christopher G. & Blayney, Donald & Dong, Diansheng & Yen, Steven T. & Johnson, Rachel J., 2011. "Will Changing Demographics Affect U.S. Cheese Demand?," Journal of Agricultural and Applied Economics, Cambridge University Press, vol. 43(2), pages 259-273, May.
Perez, Agnes C. & Blayney, Donald P. & Hoskin, Roger, 2011. "Indicators," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, pages 1-3.
Davis, Christopher G. & Blayney, Donald P. & Muhammad, Andrew & Yen, Steven T. & Cooper, Joseph C., 2010. "A Cross-Sectional Analysis of U.S. Yogurt Demand," Journal of Food Distribution Research, Food Distribution Research Society, vol. 41(2), pages 1-10, July.
Blayney, Donald P. & Dyck, John H. & Harvey, David J., 2006. "Economic Effects of Animal Diseases linked to Trade Dependency," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, pages 1-7, April.
Blayney, Donald P. & Gehlhar, Mark J., 2005. "U.S. Dairy at a New Crossroads in a Global Setting," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, pages 1-6, November.
Blayney, Donald P., 2004. "Milk Production shifts West," Amber Waves:The Economics of Food, Farming, Natural Resources, and Rural America, United States Department of Agriculture, Economic Research Service, pages 1-4, September.
Blayney, Don & Manchester, Alden, 2000. "Large Companies Active in Changing Dairy Industry," Food Review/ National Food Review, United States Department of Agriculture, Economic Research Service, vol. 23(2), pages 1-6.
Blayney, Don P., 1994. "Milk and Biotechnology: Maintaining Safe, Adequate Mille Supplies," Food Review/ National Food Review, United States Department of Agriculture, Economic Research Service, vol. 17(2), May.
Johnson, Mark S. & Mittelhammer, Ronald C. & Blayney, Donald P., 1994. "Stock Price Reaction to Regulation in the Meat Packing Industry," Journal of Agricultural Economics Research, United States Department of Agriculture, Economic Research Service, vol. 45(3), pages 1-10.
Mark S. Johnson & Ron C. Mittelhammer & Don P. Blayney, 1992. "Pesticide industry regulation: Economic consequences as revealed through stock price behavior," Agribusiness, John Wiley & Sons, Ltd., vol. 8(4), pages 347-364.
Blayney, Don P. & Fallent, Richard F. & Shagam, Shayle D., 1991. "Controversy Over Livestock Growth Hormones Continues," Food Review/ National Food Review, United States Department of Agriculture, Economic Research Service, vol. 14(4), October.
Fallert, Richard & Blayney, Don, 1990. "U.S. Dairy Programs," Food Review/ National Food Review, United States Department of Agriculture, Economic Research Service, vol. 13(1), March.
Don P. Blayney & Ron C. Mittelhammer, 1990. "Decomposition of Milk Supply Response into Technology and Price-Induced Effects," American Journal of Agricultural Economics, Agricultural and Applied Economics Association, vol. 72(4), pages 864-872.
Access and download statistics for all items
Co-authorship network on CollEc
NEP is an announcement service for new working papers, with a weekly report in each of many fields. This author has had 4 papers announced in NEP. These are the fields, ordered by number of announcements, along with their dates. If the author is listed in the directory of specialists for this field, a link is also provided.
NEP-AGR: Agricultural Economics (3) 2010-09-11 2016-04-30 2018-10-08
NEP-INT: International Trade (1) 2012-06-25
NEP-MKT: Marketing (1) 2010-09-11
To update listings or check citations waiting for approval, Don Blayney should log into the RePEc Author Service.


A champion on the indie scene alongside his brother, Sunil, Samir Singh has always had a knack for discovering the next big opportunity and pursuing it by any means necessary. His accomplishments landed him — and his sibling — in WWE Network's groundbreaking Cruiserweight Classic and, although neither of the Singh Brothers won the tournament, they quickly proved to be as opportunistic and enterprising as any Superstar who laced up a pair of boots.
The two brothers found themselves competing on the Cruiserweight-exclusive 205 Live show as well as WWE NXT, at least until they saw their biggest chance yet to shine on the brightest stage available and joined up with Jinder Mahal during The Maharaja's run to the WWE Championship. Not only were the Singh Brothers instrumental in helping Mahal win the coveted title, they proved to be crucial in his defense of it. Now, Samir Singh is finally where he believes he's always deserved to be — at least, until he decides he's hungry for more.


text:
Stefano Ayroldi (født 25. april 1967 i Bari) er en italiensk fodbolddommer som dømmer i den italienske liga Serie A. Han blev aktiv som dommer i 1995, og dømmer som linjedommer. Han har dømt et VM i fodbold, i 2010 hvor han var assistentdommer for Roberto Rosetti fra Italien. Hans første internationale kamp var kampen mellem  og  den 1. marts 2006.

Fodbolddommere fra Italien
Dommere i VM i fodbold 2010

redpajama_set_name: RedPajamaWikipedia


Your are viewing a classic 1965 Chevrolet Corvette convertible with a 350 cu. in. ram jet fuel injected engine and a Tremec 5 speed manual T6 transmission. Exterior is Red Body off powder coat. The interior is white and in good condition. Dakota cruise teak telescopic 2 tops extra deck lid for hardtop. Stainless caliper and master cylinder 83302 miles. This car runs and drives well. Please feel free to call us.David 775-964-4216 or Sharon 775-964-4216.
1965 Chevrolet Chevelle Malibu Conv.


text:
See it: Rhino wrecks car at safari park
Rhino saved? Southern white rhino gives birth aided by artificial insemination
Using artificial insemination scientists are trying to save the Northern White Rhino.
New driving tip: Don't get between a mother rhino and her child.
Jackson's Skoda Fabia suffered serious damage when it was rammed by the adult rhino.
(SWNS)
That's apparently what happened to a father and son whose car was rammed and damaged by an adult rhino at a drive-through safari park in the U.K.
Jamie Wood told SWNS that he and his five-year-old son, Jackson, were watching two Rhinos butting each other at the Midlands Safari Park when a baby got separated from them and on the other side of the compact car when the mother made a 200-foot charge and ran her horn into the front fender.
The rhinos roam freely about the park.
"It happened so quickly and I didn't know what to do, I was just in shock," wood said.
"I kept telling Jackson it would avoid us and then I heard myself swear when I realized it was going to hit us. If i'd have been a bit further forward that massive horn would have gone right through me."
Wardens patrol the facility in Land Rover SUVs.
According to a park spokesperson, a warden trying to get the adult rhinos to break it up by spinning its tires had scared the baby away, but would not cover the $2,000 repair bill.
The facility's terms of entry says that it "accepts no responsibility for damage to persons or property by animals. Under no circumstance will West Midland Safari Leisure Park accept responsibility for damage caused to any vehicle entering or exiting the electric gates."
The Skoda Fabia weighs around 2,400 pounds.
(Skoda)
Neither of the Woods were injured in the injured in the incident, but Jamie had some explaining to do, because he'd borrowed the car from his own mother.
It's not the first time something like this has happened at the facility. In 2015 a woman from Northfield suffered a similar incident that included the rhino hitting her vehicle then chasing it as she attempted to get away.
Jackson's Skoda Fabia subcompact hatchback weighs less than a fully-grown rhino and things could've been much worse.
Video shot a park in Germany several years ago shows a rhino using its horn to roll a vehicle that's about the same size as a Fabia.
Article source: https://www.foxnews.com/auto/rhino-wrecks-car-at-safari-park
Omicron variant symptoms 'usual but mild,' South African doctor says
Will Smith's 'Bad Boys' 1994 Porsche 911 Turbo is being auctioned for the first time

redpajama_set_name: RedPajamaCommonCrawl


Do you want to know your life lessons?
How exciting to know that you may be lucky in love, money or have a special gift!
A Palm reading can help you discover more about your future, your health, life and its lessons. A thorough reading of the hands can show individual potential, qualities of character and our behavior because the palms can reflect the thoughts and motivations of the mind.
The Study of the hand, Chiromancy is one of the oldest of the ancient forms of divination, which has long been known as palmistry. This study helps us to learn about ourselves and our goals in life. In modern times, a new methodical approach to hand reading has evolved (Chirology) which uses not only the study of the hand shape and fingers, but also of the lines, markings, skin texture, palm ridges and fingerprints.
The major lines are often what people look at most when questioning about their palms, but some of these lines can and do change.
What is evident on your hands now, does not mean that there is a fated outcome from what we see, therefore as our thoughts and desires change, new lines can be formed and old ones can fade.
The lines which are most likely to change are the minor lines and tend to do so as our goals or motivations change. The major lines are least likely to change quickly over time and the palm ridges and fingerprints do not change at all.
Are you ready to know more about yourself?
You may be lucky in love, money, travel or have a special gift!
There is more to analyzing hands than just reading the lines. It's a combination of comparing aspects of the whole hand, and so it can take some time to do. The basic shape of the hand is especially an important part of reading the palms because it is what helps us to determine the first and most essential character of the person.
Did you know your fingerprints can reveal your possible life purpose or choice of career?
Discovering this extra information can give you direction in life or more confidence of your abilities.
Destiny Palmistry is focused on providing you with a high-quality service and customer satisfaction, providing palm and tarot readings by e-mail as well as general information about analyzing the hands.
ARE THE READINGS SIMPLY COMPUTER GENERATED?
The e-mail readings are all personally analyzed and typed by Sari Puhakka, age 47, a palm reader of more than 25 years. Born in Finland, currently residing in Brisbane, Australia with her family and four children. She is also a published author of Claim Your Power You can ask her anything!
Do you have questions about making suitable career choices?
This website is to assist in giving a general understanding of palmistry and for ordering readings by e-mail. All questions and images of palms should be e-mailed directly to the palm reader and payments arranged through pay pal or Skrill.
We trust that you will be satisfied with your purchase.
Learn to read hands, see Destiny Palmistry.
Next TO TOUCH OR NOT TO TOUCH, THAT IS THE QUESTION.
Reblogged this on Life and Destiny Palmistry.


A proposed road project list for Transylvania County was approved last week by the Board of Commissioners.
The projects (see below) will now go to the N.C. Department of Transportation (DOT) for further consideration and possible funding.
The list was created and approved by the county's Transportation Advisory Committee (TAC), Land of Sky RPO and DOT's Division 14. TAC receives data on safety, potential costs, congestion and other factors to help make its decision.


text:
College Football Frenzy: Utah's not going away in fight for final four
Todd SaelhofMore from Todd Saelhof
Updated: November 3, 2019 12:34 PM MST
NFC notebook: When a coordinator should overrule a head coach
Everyone's wondering: Will Sherman mirror Davante Adams?
Nov 2, 2019; Seattle, WA, USA; Utah Utes wide receiver Samson Nacua (45) high-fives fans after a win against the Washington Huskies at Husky Stadium. Mandatory Credit: Jennifer Buchanan-USA TODAY Sports ORG XMIT: USATSI-404368Jennifer Buchanan / USA TODAY Sports
The Pac-12 may still be able to grab a spot in the College Football Playoff after all.
Certainly, if the Utah Utes keep up their stellar play, it'll be tough to beat them back from one of NCAA football's coveted final-four spots.
A week after putting on a defensive clinic allowing just 89 yards, the Utes found timely offence in a 33-28 come-from-behind triumph over the host Washington Huskies on Saturday at Husky Stadium in Seattle.
No. 9 Utah overcame an 11-point first-half deficit by scoring three touchdowns in the second half, including a game-turning interception runback of 39 yards for a major by junior defensive back Jaylon Johnson with 3:06 remaining in the third quarter.
"It says a lot," Utes running back Zack Moss told reporters. "The last three games or whatever it's been by putting up 40 points and our defence looking impeccable. When we can do this and come on the road and win a game like this and doing it the way we did, that's what championship teams do.
"And that's what we've been missing the last couple of years."
Offensively, quarterback Tyler Huntley has enjoyed a sharp season, adding to his totals Saturday with a 19-of-24, 284-yard passing performance. He found Zach Moss for a nine-yard TD in the second quarter and then found room himself for a one-yard TD run in the fourth quarter.
Huntley and the Utes then capped off their second-half rally with a Moss two-yard run to paydirt with 5:22 left in the contest.
Aaron Fuller's TD grab of three yards from QB Jacob Eason brought the UDub to within five points late, but it was too little, too late for the host Huskies, whose game turned in the third quarter with two timely turnovers.
It's also too late for them in the Pac-12, as their season has been sealed for quite some time now.
With the loss, the Huskies dropped to 5-4 and would likely welcome a re-do of a season that's gotten away on them.
They lost last week to the Oregon Ducks, also on home turf.
But the Utes — now 8-1 — are picking up wins both at home and away.
Even with one loss on their resumé, they are making a case for the CFP.
Outcomes such as the one Saturday afternoon in one of the toughest stadiums to get a road victory are helping to make that happen.
"It's up there for me," Utah head coach Kyle Whittingham said when asked where this win on the shores of Lake Washington rates. "I'd have to go back and look at them, but it's up there. It's very, very satisfying, especially under the circumstances."
SECOND & LONG
No. 7 Oregon (8-1) kept its end up in representing the Pac-12 along with Utah. In fact, Oregon made a statement right before the College Football Playoff selection committee debuts its rankings this season by thumping host USC (5-4), which went into the day leading the Pac-12 South, in 56-24 fashion … With a 54-28 victory, No. 24 Memphis (8-1) took care of the unbeaten record of No. 15 SMU (8-1) in a Group of Five battle. With it, Memphis gets an inside track on a New Year's Day bowl berth … Also in that bid for the Group of Five bowl Jan. 1, No. 21 Boise State (7-1) upended host San Jose State (4-5) 52-42 in a night tilt … No. 17 Cincinnati (7-1) topped East Carolina (3-6) 46-43 … Games earlier in the day saw: No. 16 Notre Dame (6-2) eke out a 21-20 decision over visiting Virginia Tech (5-3); and No. 23 Wake Forest pummel visiting NC State (4-4) 44-10.
THIRD & GOAL
Fittingly, the reigning national champion became the first team to reach nine wins on the campaign, as No. 4 Clemson (9-0) enjoyed an easy 59-7 takedown of FCS-side Wofford (5-3) in Death Valley. RB Travis Etienne had 212 rushing yards on just nine carries as part of a whopping 419 along the ground by Clemson … No. 8 Georgia proved it's still a big dog in the final-four fight, as it powered past No. 6 Florida in a battle of SEC biggies. The 24-17 win at the World's Largest Outdoor Cocktail Party in Jacksonville saw Georgia QB Jake Fromm hit an uncovered Lawrence Cager for a 52-yard touchdown and the winning points in the fourth quarter. Fromm was 20-of-30 for 279 yards and two TDs through the air … No. 14 Michigan (7-2) kept its long-shot final-four hopes alive with a roll over host Maryland (3-6) 38-7 to improve to 8-1 all-time against the Big Ten rival. Giles Jackson put up a 97-yard return for a major on the opening kick to pace Michigan.
FOURTH & INCHES
Chuba Hubbard keeps on chugging with another 223 rushing yards and two TDs on 20 carries. Wow. The Alberta running back helped host Oklahoma State (6-3) to a 34-27 triumph over Big 12 rival TCU (4-4) … No. 12 Baylor (8-0) keeps winning to surprisingly stay atop the Big 12, but it wasn't easy Thursday, when it had to block a late field-goal attempt by visiting West Virginia (3-5) in a 17-14 edge. Baylor is 5-0 in conference action … Earlier Thursday, previously unbeaten No. 20 Appalachian State (7-1) got behind early and fell short in a rally, losing to visiting Georgia Southern (5-3) 24-21 … Play of the day — Nebraska DT Darrion Daniels somehow steps in the way of a shovel pass and shuffles his 6-foot-4, 320-lb. frame all the way inside the five-yard line to help the visitors score. But the interception by the big man couldn't help Nebraska (4-5) in a 27-24 loss to Purdue (3-6). To boot, kudos to Purdue for its cool headgear — black with Boilermaker railroad tracks painted down the spine of the helmet.
NHL Scoreboard
Pittsburgh 2 Final-OT
Anaheim 2 Final-OT
Carolina 1
Tampa Bay 7 Final
Minnesota 114 Final
Chicago 89 Final
Philadelphia 100
Washington 111 Final
Toronto 140
Miami 115 Final
Oklahoma City 108
Cleveland 109 Final
Atlanta 121 Final
Portland 71 6:37
Texas 12:05 PT1:05 MT2:05 CT3:05 ET15:05 ET20:05 GMT4:05 1:05 MST3:05 EST2:05 CST3:35 VEN0:05 UAE (+1)2:05 CT
Tennessee 12:05 PT1:05 MT2:05 CT3:05 ET20:05 GMT4:05 1:05 MST2:05 CST3:05 EST2:05 CT0:05 UAE (+1)15:05 ET18:05
Green Bay 3:40 PT4:40 MT5:40 CT6:40 ET23:40 GMT7:40 4:40 MST5:40 CST6:40 EST5:40 CT3:40 UAE (+1)18:40 ET21:40
Thursday, Jun. 11
BC 9:00 ET
Friday, Jun. 12
Toronto 7:00 ET
Montreal 10:00 ET
Saturday, Jun. 13
Winnipeg 7:00 ET
UFC 246 Notes: Don't expect McGregor-Cerrone to go to the ground
Roughnecks limp into new year hoping for fresh start
UFC 246: Opportunity knocks for McGregor
U.S. court won't force military to hear Omar Khadr war-crimes appeal


text:
Sarah Jones/ August 2, 2017
Jeff "I'm not a racist" Sessions is now going after affirmative action.
"It was very painful, I didn't know how to respond," Sessions once said in response to accusations that he is racist. Sessions also once joked that he thought the KKK was ok until he learned they smoked pot, and reportedly called a black attorney "boy." Now, as our attorney general, he has decided to take on discrimination—against whites.
According to The New York Times, a leaked document suggests that Sessions's Justice Department intends to begin suing universities over their affirmative action policies:
The document does not explicitly identify whom the Justice Department considers at risk of discrimination because of affirmative action admissions policies. But the phrasing it uses, "intentional race-based discrimination," cuts to the heart of programs designed to bring more minority students to university campuses.
If the Trump administration possesses any guiding philosophy, it is white grievance. In fact, college admissions—especially at elite colleges—tilt heavily in favor of whites. This is due largely to the racial wealth gap. According to the Economic Policy Institute, the median household wealth for white families is $134,230; it is only $11,030 for black families. College degrees do not eliminate that racial wealth gap, either. Meanwhile, The Harvard Crimson reports that the median family income for Harvard undergraduates is $168,800. (It's $204,200 at Brown.)
And wealthy students have long benefited from their own form of affirmative action. In a 2016 piece for Town and Country magazine, journalist Daniel Golden explained:
One [study] put the advantage of being an alumni child at 160 points on the SAT, which had a possible range of 400 to 1600. Another examined admissions decisions at 30 highly selective colleges and universities and concluded that the odds of a legacy being accepted at the alma mater of one of his or her parents are more than seven times better than an ordinary applicant's.
But facts, as we know, matter little to Trump or to the rest of his administration. Call it government by Daily Caller comment section: The right-wing base believes it's true, so by God the Trump administration is going to tell them it is true. In doing so, they behave like typical Republicans. The administration's war on minorities is simply the culmination of a decades-long political project. Lee Atwater would be proud.
Sarah Jones @onesarahjones
Sarah Jones is a staff writer at New York magazine.
Politics, Jeff Sessions, Donald Trump, Race, Affirmative Action


text:
Q: Delphi equivalent of .net's DateTime.ToString("s") (DateTime Sortable) Is there an equivalent in Delphi?  I've looked over the documentation and can't find anything that would give me the output I want.

A: kdunlapmo, the DateTime.ToString("s") function return an Sortable date/time pattern; conforms to ISO 8601. this pattern is declarated as "yyyy-MM-ddTHH:mm:ss". regardless of the culture, the date must always be returned in the same format. you can use the FormatDateTime function in delphi to format an TDateTime value into a string.
you can use something like this
FormatDateTime('yyyy-mm-dd"T"hh:mm:ss', Now);

but you must be careful because the - character is Substituted by the DateSeparator value and the : character is Substituted by the TimeSeparator value, both variables are depending on the Windows locale configuration. so to avoid problems getting distinct results when the culture changes you must use explicity the - and the : characters in your format string.
FormatDateTime('yyyy"-"mm"-"dd"T"hh":"mm":"ss', Now)

see this sample code
program ProjectTestFormat;

{$APPTYPE CONSOLE}

uses
  SysUtils;

begin
  try
    DateSeparator:='/';
    TimeSeparator:='.';
    //this string is affected by the windows locale configuration
    Writeln(FormatDateTime('yyyy-mm-dd"T"hh:mm:ss', Now));
    //this string is not affected
    Writeln(FormatDateTime('yyyy"-"mm"-"dd"T"hh":"mm":"ss', Now));
    Readln;
  except
    on E:Exception do
      Writeln(E.Classname, ': ', E.Message);
  end;
end.

Additionally you can write a function to convert an TDatetime value to the sortable format, see this sample
function GetSortableDatetimeFormat(Value:TDateTime):string;
begin
  Result:=FormatDateTime('yyyy"-"mm"-"dd"T"hh":"mm":"ss', Value);
end;

A: Little bugfix - right is:

Result:=FormatDateTime('yyyy"-"mm"-"dd"T"hh":"nn":"ss', Value);

(minutes is "nn", not "mm")

redpajama_set_name: RedPajamaStackExchange


6/02/2016 · Really easy to do Cat Family Live Christmas Cartoons for Kids Christmas Specia by Cat Family and Friends Cat Family and Friends 218 watching... How to Draw Super Duper Probe from BoBoiBoy step by step, learn drawing by this tutorial for kids and adults.
Draw Chibi Animals Cute Animal Drawings Sketches How To Draw Cat Cats. How To Draw A Kitten Super Easy Youtube Simple Cute Cat Drawing simple cute cat drawing How To Draw A Kitten Super Easy Youtube Simple Cute Cat Drawing simple cute cat drawing how to cook moose mince meat The wildcat is a small cat of various color and a native to most of Africa. This cat is the ancestor of the domestic cat. If you want to draw Wildcat, follow our tutorial step by step for the perfect picture.
• Drawing pictures of items to see similarities and differences (e.g., draw a cat and a dog). Bird Cage Dog Doghouse Expanding on analogies also helps increase a child's knowledge base.
How to Draw a Kitten (Super Easy) - An easy, step by step drawing lesson for kids. This tutorial shows the sketching and drawing steps from start to finish. Another free Animals for beginners step by step drawing video tutorial.


Data security doesn't need to be a challenge!
Whether your data is stored within your database files or transmitted to your trading partners, using the right tools can mean the difference between meeting compliance and security best practices or suffering a data breach.
Townsend Security is well known for providing security solutions for a wide variety of platforms (IBM i (AS400, iSeries), IBM mainframe, VMware, Windows, Linux). Recently, our founder and CEO produced an excellent webinar on "Securing Your IBM i Using the Right Tools". Many of our IBM i customers are under multiple compliance requirements including PCI, HIPAA, SOX, GLBA, and others which require securing data-at-rest and data-in-motion, real-time security event logging, file integrity monitoring, and two-factor authentication. The webinar covers encryption and key management as well as a number of our other auxiliary products specifically for the IBM i (AS400, iSeries) platform.
Q: Can I use FieldProc to protect multiple fields in a file?
A: The short answer is yes, encrypting multiple fields is a fully supported capability. FieldProc does allow, from both DB2 and from our solution, protecting multiple columns or fields in a DB2 file. You can define multiple fields and then enable FieldProc with one command on all those fields within our solution. People often ask if indexes can also be encrypted and yes, that is fully supported as well. There are a few limitations in legacy RPG applications, while with a native SQL application there are no limitations.
Q: Can't I just transfer my file from IBM i to Windows and then PGP encrypt it there?
A: This is a great compliance question and comes up often with QSA Auditors. Yes, of course you can move a file from one machine to another using operations navigator. The problem is that it exposes data in the clear during the movement, either across the network if it is an unsecured connection or when the data lands on the other side of the transfer. Any of these exposures will likely result in an audit failure.
Make sure to securely move it in encrypted form and don't let it get loose anywhere in between!
Q: How does key management work with older back-up copies of data that was secured with earlier keys?
A: Any Enterprise key management solution should maintain encryption keys under policy for as long as they are needed. As you generate new keys, the older keys are retained and made available for decryption purposes, until you retire those keys. Our solution will maintain multiple versions, and doesn't have a limit on how many keys or generations you can have of master or key encryption keys. If you have a loss or need to delete data that is out of your control, you can then delete the key.
Q: Your two-factor authentication product is supported in which countries?
A: Since our 2FA solution is through TeleSign, a global company, it has a broad presence in more than 200 countries around the world and in 87 languages. By leveraging an individual's mobile phone, a reliable means of authentication has become readily available for the IBM i platform. For example, instead of tokens, businesses can simply send an SMS or voice message that contains a one-time authentication code to the individual user's phone. This means cyber criminals cannot log into the IBM i without physical control of the actual phone.
In this age of "Bring Your Own", we see the acronyms BYOD (device), BYOE (encryption), and BYOK (key) showing up all over the blog-o-sphere. BYOK is a cloud computing security model that allows cloud service customers to use the provided server-side encryption software and (bring) manage their own encryption keys.
The idea of encryption (cryptography) is almost as old as the concept of written language: if a message might fall into enemy hands, then it is important to ensure that they will not be able to read it. Most typically, encryption relies on some sort of "key" to unlock and make sense of the message it contains, and that transfers the problem of security to a new level – now the message is secure, the focus shifts to protecting the key. In the case of access to cloud services, if we are encrypting data because we are worried about its security in an unknown cloud, then why would we trust the same cloud to hold the keys without using a key management solution?
BYOK can help an organization that wishes to take advantage of cloud services to address both regulatory compliance and data privacy concerns in a third-party multi-tenant environment. This approach allows a customer to use the encryption technology that best suits the customer's needs, including the cloud provider's underlying IT infrastructure. For example, Amazon's Simple Storage Service (S3) is about protecting data-at-rest using server-side encryption with customer-provided encryption keys (SSE-C) or "BYOK". With the encryption key you provide as part of your data request, Amazon S3 then manages the encryption (as it writes to disks) and decryption (when you access your data). You don't need to maintain any code to perform data encryption and decryption in S3. The only thing you do is manage the encryption keys you provide to the Amazon Simple Storage Service. When you upload an object, Amazon S3 uses the encryption key you provide to apply AES-256 encryption to your data and then removes the encryption key from memory. When you retrieve data, you must provide the same encryption key as part of your data request. Amazon S3 first verifies that the encryption key you provided matches, and then decrypts the data before returning it to you.
Important to Note: Amazon S3 does not store the encryption key you provide. Instead, they store a randomly salted HMAC value of the encryption key in order to validate future requests. The salted HMAC value cannot be used to derive the value of the encryption key or to decrypt the contents of the encrypted object. That means, if you lose the encryption key, you lose the object.
Any time a company decides it wants to host its applications in the cloud, or use a SaaS application where the company's data will be stored in the cloud, their IT security professionals have to ask a series of questions.
Can we encrypt the data? If so, who will have access to the keys?
How will we perform key rotation and manage the lifecycle of the encryption keys?
Is the cloud vendor using a proprietary encryption technology that prevents us from moving our data to another vendor?
If we use 10 SaaS applications, will we have to administrate 10 different key management solutions?
These questions are tough enough to answer when the data and encryption technologies are in a company's own data center where it has complete control over everything. In many cases, if encryption is provided, the cloud provider holds or has access to the keys, which creates another set of problems for the end user. For one thing, a third-party having access to data in the clear is a violation of regulations such as PCI-DSS, HIPAA, GLBA and others. Also, customers have yet to establish trust in cloud platforms or SaaS providers to protect their data. There have been many high profile data breaches that make end-users nervous. Customers also fear the U.S. government will subpoena access to their data without their knowledge or permission. For companies outside the U.S. that choose to use a U.S.-hosted cloud or app, there are data privacy and residency concerns. Instinctively it feels a lot more secure to manage your own key and use BYOK instead of leaving it to the cloud provider.
You need to know where your sensitive information is. Period.
You need to know who has access to it. Not who you think has access to it, but who really has access to it.
Wherever you put your sensitive information, you need to protect it. The most critical thing you need to do is to apply a strong defense in depth approach to data security, including the use of encryption and access controls.
You need to be able to document, through audit logs and reports, who has actually accessed your information. This is true (and important) for sensitive data, as well as for compliance-regulated data.
If you think that having your cloud service provider encrypt your data provides adequate security for your information, you probably need to rethink this.
It all boils down to this: When encrypted data is stored or processed in the cloud, the data and the keys must be kept separate and only the end-user should control the encryption keys.
Cloud storage options bring new economies and business efficiencies, but security can't be ignored, and it can't be simply outsourced to some other party. We believe that it is fundamental to good security to control all access to your data, including managing your own encryption keys. Managing encryption keys may sound daunting, but it doesn't need to be. Our technology makes data security and encryption key management simple and straightforward. Our key management solution addresses all of the issues described above and can protect your data everywhere you have it stored.
Real-time, Low-cost, Business Integration When and Where You Need It!
Do you need a complete and affordable solution for implementing XML web services on your IBM i? Need a solution that won't disrupt your existing applications and database so you can easily implement web services without complicated API programming or the deployment of external servers? Our Alliance XML solution includes all of the communications, XML parsing, data translation, and application integration components that you need. You can create XML documents from your existing database files and securely send them to remote web servers, and you can receive XML documents directly on your IBM i and process the data into your applications.
QSA auditors and other security professionals focus on the protection of sensitive data after it traverses the Internet and then lands in a database on a hard disk drive. You need a solution that provides security at every level of processing and protects data in transit using session encryption. When sending or receiving XML documents Alliance XML can use the Transport Layer Security (TLS) protocol for strong encryption of the transferred data. The Alliance XML TLS support is based on the IBM Digital Certificate Manager and related IBM APIs for TLS sessions. This gives you an implementation that is compatible with native IBM i security. As an additional layer of security the Alliance XML HTTP servers provide IP address controls so that only known clients can use the servers.
When receiving XML documents with sensitive data you can enable field level encryption to protect the data. For example, if you receive a document with a credit card number or social security number, you can use strong encryption of the data to protect it before it is written to your database table. User APIs provide a means of decrypting the data so that it can be used in your RPG and Cobol applications.
The web protocols HTTPS and FTPS provide for the ability to encrypt the data in transit, and Secure Shell SSH also provides strong encryption. But after the data reaches the end point of its journey it lands in a database somewhere, and it is often exposed to loss at that point. I believe that's why security auditors put emphasis on making sure that data is encrypted when it hits it's destination.
Many companies have implemented web services in combination with the XML data standard to take advantage of low cost, real time integration with their customers and vendors. When you combine the ubiquity of the web HTTPS protocol with the W3C XML standard you get a powerful incentive to use this platform for business integration.
Care should be given to what happens to data when it leaves the realm of encrypted transit and lands on server hard drives. The right thing to do is encrypt sensitive data at the very beginning. This means that the tools you are using have to support encryption as a natural part of the process of converting XML data. Standard XML processing tools such as Xerces and Xpath do not have built-in encryption. The same is true for XML toolkits and APIs provided by IBM, Microsoft, and others. This leaves it to developers to try to intercept data after it is transformed from XML and before it lands in a database table or on a hard drive. That's a real challenge.
In our Alliance XML/400 web services product on the IBM platform we built encryption right into the data transformation process. Alliance XML/400 customers can protect sensitive data by enabling the encryption option on a translation map. The solution does the rest. The data is encrypted before insertion into the database and there is no exposure as the data lands in the database on the hard drive. Our customers are taking advantage of this feature to meet PCI and other compliance regulations.
Encryption can help protect against another common threat, too. At the annual PCI SSC standards council meeting a few years ago, forensics expert Chris Novak of Verizon talked about how more than 75 percent of data loss events begin with a well known weakness that hasn't been patched, and half of these are based on SQL injection attacks, this is still true today. With SQL injection, the attack on your servers starts with bad data inserted into a database in the clear, leaving open a later exploit. There are ways to prevent SQL injection through programming techniques, but encryption will also help defeat them.
Will encrypting your data provide all of the security protection you need? No, but it should be a major part of your defense-in-depth strategy to protect sensitive data.
Beyond meeting compliance regulations, it is the right thing to do!
In the past, encryption has had a reputation for being difficult to do, complex, and time consuming, we hope to show you how that has changed. If you are new at protecting data in Microsoft SQL Server environments, generally compliance regulations are what drive an encryption project.
Since it wasn't thought of as something that improved the "Bottom line" by increasing revenue or decreasing expenses, encryption has historically been a project solely driven by the need to meet compliance regulations. There are a large variety of compliance regulations that most, if not all, businesses fall under. One common misconception about compliance regulations is that they don't equally apply to both private and public companies. To clarify, these regulations apply to all companies, of all sizes, whether they are privately-held or publicly-owned.
HIPAA Data Security & HITECH Act of 2009 which applies to Medical Providers and the healthcare industry.
GLBA/FFIEC apply to banks, credit unions, credit reporting agencies, and anyone in the financial industry.
FISMA is for Federal US Government Agencies.
The Federal Trade Commission (FTC) also gets involved with anyone who issues a privacy statement.
More than 45 states also have their own privacy rules, in addition to the ones listed above, that strongly recommend encryption of any personally identifiable information (PII).
So, beyond compliance with regulations, why should you care about encryption… and what is it anyways? First of all, your customers, clients, and suppliers all expect you to protect their sensitive data. Hackers and data thieves are targeting mid-sized companies because, as larger companies get better at securing sensitive information, the hackers see smaller companies as better targets. Financial fraud and data breaches become more common in those businesses that might not be as prepared without the resources to have an internal security team. Data loss can have a big impact on a company's reputation as well as their financial health.
AES encryption is a mathematical formula for protecting data. It is based on a proven, well-known algorithm and standards published by NIST. Since that formula is a open and vetted standard use, it is not the mathematical algorithm that is the big secret. It is what happens with the "Key" that locks and unlocks the data that all the fuss is about.
Key management is so important because the encryption keys are THE secret that must be protected. Without access to the key, a hacker that accesses encrypted data has no way to read it. Industry standards and best practices for encryption key management, as well as compliance regulations that require proper encryption key management, all state that storing encryption keys on the server with the protected data is a poor security practice. Encryption keys are unique and cryptographically secure, and once created, protecting the key is the core practice that will protect the sensitive data. It will not be defensible in the event of a data breach if the keys were stored in the same server as the data. This would be like leaving the key to your house in the door lock and being surprised that someone entered uninvited!
Our solutions help Microsoft SQL Server customers really protect their data. Alliance Key Manager, our encryption key management solution, is NIST FIPS 140-2 compliant. This means it meets Federal standards that private enterprises expect around key management. We provide encryption key management solutions for every version and edition of SQL Server starting with SQL Server 2005. In addition, you can choose between a hardware security module (HSM), Cloud HSM, VMware virtual appliance, or a cloud instance in AWS or Azure. Easy. Efficient. Cost-Effective.
Please join our founder and data security expert, Patrick Townsend, in this 30-minute webinar that will cover encryption and key management best practices with Microsoft SQL Server!
As always, your comments and feedback are appreciated!
As we discussed in the webinar and latest blog on Encryption & Key Management Everywhere You Need It, sensitive data needs to be protected wherever it resides!
Q: Is there any limit to the number of servers that I can hook up to your encryption key manager?
Patrick: There are no restrictions, and no license constraints on our encryption & key management solution. We don't meter or count the number of client-side platforms that connect to our Alliance Key Manager, so you can hook up as many client side applications, servers, and processors as you need to. This is one of the things I think is different about how we approach encryption and key management with our customers. We also know the applications you are running today may not be the applications you need to be running tomorrow and we really want you to deploy encryption to all your sensitive data and scale up when & where you need it.
Q: With the various platforms that I can deploy an encryption key manager in, how do I know which one is right for me?
Compliance regulations that you need to meet can be a factor in whether you deploy an Hardware Security Module (HSM) or a cloud HSM or a virtualized instance. If you are working with an auditor or going through a QSA audit, you'll want to have a conversation with them to understand their expectation from a compliance point of view around where you deploy your encryption key manager.
Risk tolerance will also come into play. You may have a security group within your organization with strong feelings about how to deploy encryption key management and how to mitigate risk. If you have large amounts of sensitive data to protect you might decide to deploy an HSM in your secure data center. If you're dealing with a very small amount of data and you do not process credit cards or personally identifiable information, your risk assessment may indicate a cloud deployment.
Budget is certainly always a factor to consider. It is important to consider the cost benefits of security however, we all understand that leaving our data in the clear is no longer an option. It is a matter of understanding your industry regulations and risk assessment, then deciding what encryption and key management to deploy.
While they are generally the most secure solution, Hardware Security Modules (HSMs) can be more expensive than a virtual environment, dedicated cloud instance, or virtual private cloud. Once you look at all the factors that affect your company, we will be there with the right solution that will work for your needs.
Q: Does Townsend Security provide guidance on how to get the best performance with my operating environment?
Patrick: Because every enterprise operational environment is different, we provide guidance around performance with our encryption key management solution. With every one of our solutions we offer complimentary 30-day product evaluations and encourage our customers to do proof of concepts with their applications. We are serious about making this process simple, and our customers can download the actual instance in evaluation mode, run it with their applications, test the actual solution, and truly evaluate performance in their specific environment. Performance metrics will be moderated by a number of factors within your specialized environment, your network, and your processing platform.
Q: I have data that needs to be encrypted in a cloud other than Amazon or Windows Azure, can your product help me with this?
Patrick: Yes, we can. First of all, following best practices, you want to keep your encryption keys separate from the data they are protecting. You may have data in a cloud platform, but choose to run your encryption key management solution in a different location or a virtual private cloud. Let's say you want to run the key manager in a dedicated cloud HSM or even in your data center. Most top-tier cloud vendors truly support multiple environments for running key management, and we find that our solutions work well for customers who are running in the cloud. We suggest you contact us and have a conversation about options and we can provide guidance about how to deploy a secure solution.
Q: How is Alliance Key Manager Priced?
Patrick: We have a wide set of options for our customers, and are dedicated to helping find affordable solutions. We have perpetual license or subscription options for classic HSMs, Cloud HSM, and virtualized environments. Our cloud offerings are true usage-based subscriptions, so if you're used to deploying in Amazon Web Services or Windows Azure, our encryption & key management solutions will fit that same strategy for pricing.
We really believe that the encryption should go everywhere you need it to go! Your key management should work across a wide set of application environments, and it must be affordable, so that we can all get where we need to be in terms of protecting sensitive data. Regardless of where your data is or what platform you are using, there's a solution that can work for you!
Wherever your sensitive data resides - client side applications, secure data centers, or in the cloud - Encrypt it!
"Sensitive data" is not just credit card numbers and expiration dates anymore. Because of recent data breaches, we know that loyalty information like names, e-mail, physical addresses, phone numbers; personal data like birthdate, social security number... so much information today... now constitutes what we call personally identifiable information (PII) and must be properly protected with encryption no matter it is stored.
When it comes to protecting data, look to well-defined industry standards for an encryption algorithm that is reviewed and vetted by cryptographers around the world. Advanced Encryption Standard or AES is the most commonly used encryption algorithm to protect sensitive data. Validated by the National Institute of Standards and Technology (NIST), this standard is referenced in a wide variety of compliance regulations either as a requirement or as a recommendation. However, the AES algorithm is not the secret that we have to defend. Think of encryption as the lock that you put on your front door, and the encryption key is your house key. You don't tape your house key right next to the lock when you leave in the morning, you take it with you and you protect it from loss or theft. Your unique encryption key is THE secret that you must protect, which can be accomplished using a secure, certified key management solution. Getting encryption key management right is in fact the biggest challenge customers and organizations run into when they start their encryption projects.
When you look at what it takes to properly protect sensitive data with encryption, you immediately find standards (NIST) & best practices for key management, and industry compliance regulations (PCI DSS, HIPAA/HITECH, FFIEC, and state privacy laws) that require proper key management. They all say the same thing: "Do Not Store the Encryption Key on the Same Server as the Encrypted Data".
Encryption key management is a well-defined process with standards and best practices around managing encryption keys and a formal definition of the encryption key lifecycle.
When an encryption key is first generated, or established, it may not be used for some time so it waits in a pre-activation status until it is being actively used. The key will expire after use or based on a set definition and then will go into escrow after post-activation. After that period, the key is generally destroyed.
One way to destroy data is to destroy the encryption key that's protecting it, because if the key is not recoverable neither is that data. Auditors will want to know if you have a process for managing the encryption key through the entire lifecycle, and this is one of the things that a key management solution does for you in a provable way. Beyond the encryption key lifecycle, the key management solution provides access controls for users and groups, in-depth audit trails and system logging with the ability to integrate across multiple platforms, and they must implement a mechanism for dual control and separation of duties to really meet compliance regulations as well as defensible security best practices.
It is also very important for an encryption key manager to provide the option of onboard encryption. The core function of the encryption key management solution is to generate, protect, and distribute encryption keys to authenticated users. If you have a web application or a more exposed cloud environment, retrieving an encryption key may seem risky to you in terms of having that key in your operating environment. With an onboard encryption solution you can send your data to the key manager, name a key, and get that data encrypted or decrypted strictly within the confines of that key management solution. Avoiding the risk of losing encryption keys in a more exposed environment is an important component in a compliance strategy.
Even 10 years ago, encryption key management solutions were very expensive specialized hardware devices and very difficult and time consuming projects. Thankfully, encryption and key management is no longer the development or cost headache it once was. Since IT infrastructures have become very complex environments using different technologies and platforms (60% of Microsoft SQL Server customers are also running Oracle someplace in the organization), a key management solution also needs to address these complexities and protect data wherever it may be. There are still hardware security modules (HSMs) and now there are new options for deployment of cloud-based HSMs, virtual appliances, and true cloud instances of encryption and key management.
Hardware Security Module (HSM) is a physical appliance or security device that is protected and tamper evident. Built for high resiliency and redundancy it has hot swappable rated disc drives, dual power supplies, dual network interfaces, and is deployed in your IT data center.
Cloud HSM is a physical appliance hosted in a secure cloud with real-time encryption key and access policy mirroring. Dedicated HSMs are hosted in geographically dispersed data centers under an ITIL-based control environment and are independently validated for compliance against PCI DSS and SOC frameworks. No access is available to the cloud vendor or any unauthorized user.
Virtual Appliances are the exact same key management solution - the same binary software that runs inside the hardware HSM - available as a VMware instance.
In the Cloud - If you're running on Microsoft Windows Azure or vCloud, the encryption key manager can run as a true cloud instance in a standard cloud or deploy in a virtual private cloud for added data protection for sensitive applications.
We think that when you buy an encryption key manager, you should be able to easily deploy the solution, get all your encryption projects done properly, and have very affordable and predictable costs.
We understand that we live in a world where budget matters to our customers, so we do not charge client-side fees.
We understand that IT resources are limited and have done a huge amount of work to make our solutions easy with out-of-the-box integrations, simplified deployments, and also provide along with our solution ready-made client-side applications, encryption libraries, source code samples, as well as SDKs for developers who need them to get their projects done very quickly.
Still Have Questions About Meeting Compliance Requirements?
Q: If I have my sensitive data stored off site with a hosting company or in the cloud am I responsible if they have a data breach?
A: The short answer is yes you are. When you have sensitive data and are moving it into a cloud solution you are still ultimately responsible for protecting that data. This can be confusing because cloud vendors make a lot of statements about encryption and compliance, however you are responsible for your overall data protection strategy.
It is your responsibility to make sure your data security meets compliance regulations. Any loss will also be your responsibility, so it is worth the time to make sure you have a strong strategy in place and are using industry standard encryption and proper key management to protect your data wherever it resides.
Q: A vendor told me that tokenizing data will make us PCI compliant is this true?
A: This is a more complex question to answer. Tokenization is a great technology and there has been a lot of work done in this field the past few years. Personally, I believe it can be done well and can help you meet compliance regulations. If you are planning to generate non-recoverable tokens (when the original data does not need to be recovered) using a separate token server, that can eliminate the need to store the original data in an encrypted format. Non-recoverable tokens can help minimize the impact of regulations such as HIPAA, PCI, HITECH , GLBA and individual state privacy laws by taking the server out of scope for compliance. However if you plan to recover the data and are consolidating sensitive information into the tokenization solution, you must make sure the tokenization solution itself is PCI compliant and using industry standard encryption such as AES when using recoverable tokens. The basic concept for tokenization is that you replace the data in your database with a token that has no value; however, sensitive data (for retrieval) has been transferred into the tokenization solution. Because all of this sensitive information has been consolidated into one place, it becomes even more of a high value target. Tokenization is very effective as long as you are using industry standard encryption within that solution and also using best practices for encryption key management. Make sure you are using a tokenization solution that integrates with a NIST validated and FIPS 140-2 compliant key management solution that will properly store your encryption keys on a designated hardware security module (HSM) and not in the same server as the pool of data.
Q: A vendor we are considering for key management advertises an integrated key management solution, would this be PCI compliant?
A: Only a QSA auditor can determine PCI compliance of vendor solutions, however being educated on industry best practices is very important.
Storing the key within the same server where the data is located is not a defensible practice, and security best practices recommend using an HSM to store encryption keys away from the data you are protecting. Best practices for encryption key management also recommend that you implement separation of duties and dual control. I highly recommend that you look for NIST validations and make sure the approach to encryption and key management has been done correctly.
To help you plan your data security strategy, we've created a great How-to-Guide on Encryption Best Practices and you can download your complimentary copy by clicking on the link below.
As always, we welcome your questions and comments!
Would Your Data Security Strategy Pass an Audit?
Are You Confident You Are Meeting Compliance Requirements?
Why do we have so many different compliance regulations that affect our companies and our need to protect data? The fact is that there are people out there trying to access that sensitive information and devastating data breaches happen on a regular basis. While breaches are very difficult for companies that suffer the loss of customers, brand damage, and stiff financial penalties, it is the consumers and individuals who are most impacted by the loss of personal information, credit card numbers, or bank account numbers. Because these breaches happen and have such a catastrophic effect on individual people, state and federal and private regulations have been necessary to help motivate companies to try to protect that sensitive information and keep it out of the hands of those who would use it to commit the financial crime and fraud.
HIPAA/HITECH Act covers the medical segment and any partner entity under thefederal law has to comply with data protection for protected health information (PHI) of patients and must meet requirements about protecting patient information and PHI. The most recent meaningful use guidance was very clear that organizations who fall under HIPAA/HITECH must protect patient health information and we must use proper key management as a part of any encryption strategy. They were quite blunt when they said 'don't store encryption keys on the device with protected data'... there is no gray area there!
GLBA/FFIEC applies to the financial industry (bank, credit union, trading organization, credit reporting agency). Gramm Leach Bliley Act sets standards for protecting information and consumer information. The FFIEC is responsible for publishing guidance, actually performing audits, and enforcing the standards set by GLBA around encryption and key management best practices.
Sarbanes-Oxley (SOX) applies to public traded companies (section 404 - information technology and data protection for stakeholders). SOX provides detail around data protection, guidance around cryptographic key management, and security requirements for data management. They issue very strong guidance for encrypting sensitive data of personally identifiable information (PII) that is being managed by a publicly traded company. SOX closely mirrors the National Institute of Standards and Technology (NIST) which publishes best practices guidance for encryption key management, key management lifecycles, and logging.
In the United States we have a number of state privacy laws, some of them mandate encryption, others strongly recommended it. These laws apply to both public and private organizations of all sizes and provide guidance for breach notification and penalties around data loss. There is a wide recognition that protecting data using industry-standard encryption and proper key management is a basic common safe harbor from having to do breach notification. Additionally there is a proposed federal privacy law that will eventually replace the individual state laws.
What elements do all of these regulations have in common?
One of the biggest points of audit and compliance failure is around the encryption key management strategy. While compliance regulations do not mandate FIPS 140-2 validation on a key management solution, auditors will red flag encryption or key management that's not industry-standard. They're looking for certifications like NIST validation of AES libraries or other encryption components and FIPS 140-2 validation of key management solutions. Once you encrypt your data with AES, encryption keys are the secret that you must protect. The nature of an encryption key is that it is unique to you. It cannot be easily detected or reverse engineered from the data itself. Look to NIST for recommendations about how to manage the creation and lifecycle of an encryption key (when it should be rotated or changed).
What do auditors look for in certifications and standards?
Regulations are getting more stringent and specific… not less!
Fines and penalties are getting steeper… not cheaper!
Define personally identifiable information (PII) broadly…not narrowly!
Also crucial when you begin to consider a data protection strategy and your data is moving across multiple operating systems, databases, and platforms is to look for a common approach to encryption and key management, it will be very helpful in reducing costs and maintenance over the long-term.
Please request the webinar download!


text:
Ишму́рзино () — село в Баймакском районе Республики Башкортостан (Россия). Административный центр Ишмурзинского сельсовета.

Географическое положение
Расстояние до:
 районного центра (Баймак): 22 км,
 ближайшей железнодорожной станции (Сибай): 63 км.

История
Название происходит от личного имени Ишмырҙа.

Население

 Национальный состав
Согласно переписи 2002 года, преобладающая национальность — башкиры (100 %).

Известные уроженцы
 Тутманов, Радис Нурисламович (род. 1953 года) — солист ансамбля народного танца им. Ф. Гаскарова, народный артист Республики Башкортостан (1994).

Примечания

Ссылки
 Совет муниципальных образований Республики Башкортостан .
 Ишмурзино (Юкаляр) на портале «Генеалогия и Архивы»

Населённые пункты Баймакского района


text:
You are here: Home / News / Front Page / PUPPY LOVE
FRIDAY, JUNE 10, 2016 /by DOUGLAS ROBSON
Wozniacki taught her dog, Bruno, to respond to commands in English, so anyone could tell him to "sit" or "stay." (Photo by Douglas Robson)
For globetrotting tour insiders, Chip, Pierre and Bruno manage to keep a low profile, not to mention a lot of feet on the ground.
They jet off to tournaments. They carry special passports. They hang out in the players' lounge, show up at press conferences and pass on a first-name basis. But you won't find them on any official credential, guest or entry list.
Chip, Pierre and Bruno walk on all fours. They are dogs.
Like coaches, nutritionists and conditioning experts, canines are increasingly part of the ever-expanding modern tennis entourage; a lavish—and some would argue, outlandish—ingredient in the smorgasbord of circuit life.
No shortage of top players travel with their tail-waggers, from Serena Williams, Novak Djokovic and Caroline Wozniacki (regularly) to Bethanie Mattek-Sands, Andy Murray and Svetlana Kuznetsova (occasionally).
To owners, the headaches of criss-crossing continents with a dog in tow are outweighed by the gift of unconditional affirmation despite life lived out of a suitcase. They are a touchstone of domestic stability and companionship on tennis' long and lonely road.
"It's so comforting," said Williams, who often refers to her 10-pound Yorkshire Terrier, Chip, as "my son."
"We don't see them as just an animal," echoes Djokovic, whose toy poodle, Pierre (being carried, at right), is closest to his wife, Jelena.
As Wozniacki says of her Pomeranian puffball, Bruno, who never leaves home without his European Union doggy passport: "It's totally worth it. He's always happy to see you."
Weathering far-flung time zones with a mutt or, more typically, a pint-sized purebred, is not as expensive as it might sound. The added fees for flights, hotels and food amount to a few thousand dollars a year, said several players. That's pocket change to multi-millionaires like Williams and Djokovic.
But the potential hassles are many, and are occasionally emotionally costly. Animals end up stranded at customs by paperwork snafus. They relieve themselves in busy airports or hotel lobbies. They must be fed, walked and exercised, all while negotiating the rigorous demands of elite tennis.
Djokovic names dog for Dogs Trust. EDITORIAL USE ONLY: World number one tennis player and dog lover Novak Djokovic with his girlfriend Jelena Ristic and their pet poodle, Pierre, play with Goldendoodle Bella, a Dogs Trust rescue dog, which Novak named this morning at his temporary residence in Wimbledon, south west London, to raise awareness of Dogs Trust and help find Bella a new home. PRESS ASSOCIATION Issue date: Friday June 21, 2013. Photo credit should read: John Phillips/PA Wire URN:16865807
"I love dogs," says Djokovic, whose transition to fatherhood last year did not deter him from adding a second toy poodle, Tesla, to his growing brood. "But logistically it's not easy, especially when you travel on the opposite side of the world."
Indeed, dog-care duties often fall on other members of a player's team. Significant others, parents and hitting partners all pitch in. But players also go to great lengths to make their pets content, and it is not unusual to see them out strolling with their dogs on streets and in cafés across the globe. Djokovic recently found himself sneaking 7-year-old Pierre into the cramped lavatory of a transatlantic flight so that the little poodle could do his business. He positioned Pierre over the seat. He sweet-talked. He stroked his fur. He flushed. Pierre did not oblige.
If the idea of Serbia's best-known citizen at 33,000 feet bent over the toilet coaxing his dog to go sounds absurd, Djokovic does not disagree. "What can I do?" he says, sounding chagrined as he explains commercial airlines' in-bag policy, even for flights that can last 14 hours. "It's the only place I can let him out."
A few years ago, Kuznetsova tried to bring Dolce, her 50-pound American Bulldog, to Wimbledon. The two-time Grand Slam champion hit a snag on arrival and the notoriously strict U.K. authorities placed Dolce in quarantine.
Kuznetsova was beside herself. She left the tournament to visit him every day at a small, dirty facility next to Heathrow Airport. The fees ended up costing her more than her hotel in London. "It was a mess," she says. "I was crying so much."
By definition, the best-traveled dogs are toy breeds. They rarely exceed 20 pounds, so they can ride inside airplane cabins. But there are exceptions.
American Bethanie Mattek-Sands has taken to the road with Ruger (at right), a 140-pound South African Mastiff-like breed called a Boerboel. Named for the Ruger Magnum firearm, he entered her life when she and her husband, Justin, started dating. Justin had acquired Ruger just before they met.
Ruger, understandably, has never flown. But he has accompanied the couple on road trips from their Arizona base to tournaments in California. One summer, Ruger visited several tour stops on the East Coast and in Canada.
Despite his intimidating size, Mattek-Sands says Ruger is a big baby. He doesn't thrive away from the familiar surroundings of home. He won't eat at first. He's startled by any small noise. He must sleep with his toys. "He kinda freaks out a little bit," she says.
Mattek-Sands says she and her husband often feel like "absentee parents" because they leave him in the care of others so often. And though he's high-maintenance, Ruger is a sweet, obedient, playful pooch that sleeps with them in bed. "He's like another person to cuddle with," Mattek-Sands says. When he leaves a mark, however, it doesn't go unnoticed. "They're huge," says Mattek-Sands of Ruger's droppings. "You won't miss them."
Not everyone views the decision to tote animals around the world as a worthwhile inconvenience. Dominika Cibulkova's parents were none too pleased when the Slovakian started to travel regularly with her two Yorkshire Terriers, Woody and Spajky.
Kuznetsova says her father, a renowned coach of several Olympic cycling medalists, went "nuts" when she began to bring Dolce to tournaments. "He said, 'You cannot do this! You're an athlete! You need to focus! You will disturb your sleep,' and blah blah blah."
Harold Reginald Williams – September 12, 2012 – EleVen By VENUS WILLIAMS Spring/Summer 2013 Presentation held at The GREY GOOSE Blue Door, 509 West 34th Street, New York, NY. Photo Credit: A.m. Hoyer/PatrickMcMullan.com/Sipa USA
While modern travel and lucrative prize money have made such extravagances possible, the idea of folding a pet into the most peripatetic of sports strikes others as doggone crazy.
"It's not for me," says animal lover Agnieszka Radwanska, with a dismissive roll of the eyes.
Jelena Jankovic, who has a Maltese named Stella at her home in San Diego, goes a bit further. She says it's unfair. "Being in a bag all day is not fun," the Serbian says. "I prefer my dog to be at home and live a normal life."
Still, others view it as a luxury for the elite. "I think that only would work if you're one of the top players flying privately," says dog-loving American Tim Smyczek. "That would be a goal of mine—to afford a dog on tour."
Most dogs coexist amiably on tour, but tensions can arise. Mattek-Sands says Ruger became embroiled in a "standoff" with Kuznetsova's Dolce when they crossed paths in a hotel lobby.
"They had this little alpha male thing going," says Mattek-Sands. "I'm just glad Justin was holding him because he's strong. If he really wants to take off, I have no chance."
Some dogs keep to themselves. Maria Sharapova's Pomeranian, also named Dolce, once appeared in a series of Canon ads with the L.A.-based superstar but is not one to mingle. "He's unsocial," Sharapova says, "kind of like his owner."
Social or not, players face daily inconveniences in exchange for their loyalty. Dogs disrupt sleep by barking at strange noises. They whine. They snore. They get sick. They act out. Kuznetsova's dog once chewed up her favorite sunglasses. But that's not his main offense. "He farts a lot," she says.
Food is another issue. Simple kibble does not always make the cut. Some players cart special concoctions with them. Diet-crazed Djokovic says he cooks rice, carrots and beef for Pierre and Tesla. Sharapova's tiny and spirited dog is on a raw diet. "It's a Russian thing," she says.
And though no toy is more ubiquitous to dogs than the tennis ball, not all ATP and WTA canines are necessarily fans. Some chase them; some disdain them. "If I throw him a tennis ball he just looks at me and says, 'OK you run and get it,'" Djokovic says of Pierre.
Serena Williams of the U.S. and her dog Chip pose in the cloakroom after winning the French Open Tennis tournament against Lucie Safarova of the Czech Republic, at the Roland Garros stadium in Paris, France, Saturday, June 6, 2015. Williams won 6-3, 6-7, 6-2. (Corinne Dubreuil, FFT, Pool via AP)
Wozniacki, on the other hand, trained Bruno not to chase tennis balls, or any yellow ball. "We said no because when I'm practicing I want him to be at the side of the court," she says.
On the flip side, dogs jump for joy, wag tails, lick faces and gaze up adoringly. Players who don't take them on the road describe giddy reunions when they reunite back at home. "My best moment is when I come from a trip and I open the door and my dog starts running in circles," Jankovic gushes.
"I think we all need distractions, something to look forward to when we come back home—the unconditional love you get from pets," says Nadia Petrova, whose French Bulldog, Lulu, stays at her base in South Florida. "They are the best therapists."
And while there are challenges, the bond between master and dog runs deep, even for some of the world's least stationary athletes. "We're all one family," says Djokovic.
Williams says she would travel more regularly with Chip (above) and her other dog, a Maltese named Lorelei, if she could. But even that would barely suffice, says the American great. "I could live with 100 of them if I had the time."
FRENCH OPEN 2016: FUN THE KEY FACTOR IN WINNING DOUBLE PARTNERSHIP PHOENIX'S BETHANIE MATTEK-SANDS ON VERGE OF FIRST OLYMPICS


text:
package docker

import (
	"fmt"
	"strings"
	"sync"
	"time"

	log "github.com/Sirupsen/logrus"
	"github.com/armon/go-radix"
	docker_client "github.com/fsouza/go-dockerclient"

	"github.com/weaveworks/scope/probe/controls"
	"github.com/weaveworks/scope/report"
)

// Consts exported for testing.
const (
	CreateEvent            = "create"
	DestroyEvent           = "destroy"
	RenameEvent            = "rename"
	StartEvent             = "start"
	DieEvent               = "die"
	PauseEvent             = "pause"
	UnpauseEvent           = "unpause"
	NetworkConnectEvent    = "network:connect"
	NetworkDisconnectEvent = "network:disconnect"
)

// Vars exported for testing.
var (
	NewDockerClientStub = newDockerClient
	NewContainerStub    = NewContainer
)

// Registry keeps track of running docker containers and their images
type Registry interface {
	Stop()
	LockedPIDLookup(f func(func(int) Container))
	WalkContainers(f func(Container))
	WalkImages(f func(docker_client.APIImages))
	WalkNetworks(f func(docker_client.Network))
	WatchContainerUpdates(ContainerUpdateWatcher)
	GetContainer(string) (Container, bool)
	GetContainerByPrefix(string) (Container, bool)
	GetContainerImage(string) (docker_client.APIImages, bool)
}

// ContainerUpdateWatcher is the type of functions that get called when containers are updated.
type ContainerUpdateWatcher func(report.Node)

type registry struct {
	sync.RWMutex
	quit                   chan chan struct{}
	interval               time.Duration
	collectStats           bool
	client                 Client
	pipes                  controls.PipeClient
	hostID                 string
	handlerRegistry        *controls.HandlerRegistry
	noCommandLineArguments bool
	noEnvironmentVariables bool

	watchers        []ContainerUpdateWatcher
	containers      *radix.Tree
	containersByPID map[int]Container
	images          map[string]docker_client.APIImages
	networks        []docker_client.Network
	pipeIDToexecID  map[string]string
}

// Client interface for mocking.
type Client interface {
	ListContainers(docker_client.ListContainersOptions) ([]docker_client.APIContainers, error)
	InspectContainer(string) (*docker_client.Container, error)
	ListImages(docker_client.ListImagesOptions) ([]docker_client.APIImages, error)
	ListNetworks() ([]docker_client.Network, error)
	AddEventListener(chan<- *docker_client.APIEvents) error
	RemoveEventListener(chan *docker_client.APIEvents) error

	StopContainer(string, uint) error
	StartContainer(string, *docker_client.HostConfig) error
	RestartContainer(string, uint) error
	PauseContainer(string) error
	UnpauseContainer(string) error
	RemoveContainer(docker_client.RemoveContainerOptions) error
	AttachToContainerNonBlocking(docker_client.AttachToContainerOptions) (docker_client.CloseWaiter, error)
	CreateExec(docker_client.CreateExecOptions) (*docker_client.Exec, error)
	StartExecNonBlocking(string, docker_client.StartExecOptions) (docker_client.CloseWaiter, error)
	Stats(docker_client.StatsOptions) error
	ResizeExecTTY(id string, height, width int) error
}

func newDockerClient(endpoint string) (Client, error) {
	if endpoint == "" {
		return docker_client.NewClientFromEnv()
	}
	return docker_client.NewClient(endpoint)
}

// RegistryOptions are used to initialize the Registry
type RegistryOptions struct {
	Interval               time.Duration
	Pipes                  controls.PipeClient
	CollectStats           bool
	HostID                 string
	HandlerRegistry        *controls.HandlerRegistry
	DockerEndpoint         string
	NoCommandLineArguments bool
	NoEnvironmentVariables bool
}

// NewRegistry returns a usable Registry. Don't forget to Stop it.
func NewRegistry(options RegistryOptions) (Registry, error) {
	client, err := NewDockerClientStub(options.DockerEndpoint)
	if err != nil {
		return nil, err
	}

	r := &registry{
		containers:      radix.New(),
		containersByPID: map[int]Container{},
		images:          map[string]docker_client.APIImages{},
		pipeIDToexecID:  map[string]string{},

		client:          client,
		pipes:           options.Pipes,
		interval:        options.Interval,
		collectStats:    options.CollectStats,
		hostID:          options.HostID,
		handlerRegistry: options.HandlerRegistry,
		quit:            make(chan chan struct{}),
		noCommandLineArguments: options.NoCommandLineArguments,
		noEnvironmentVariables: options.NoEnvironmentVariables,
	}

	r.registerControls()
	go r.loop()
	return r, nil
}

// Stop stops the Docker registry's event subscriber.
func (r *registry) Stop() {
	r.deregisterControls()
	ch := make(chan struct{})
	r.quit <- ch
	<-ch
}

// WatchContainerUpdates registers a callback to be called
// whenever a container is updated.
func (r *registry) WatchContainerUpdates(f ContainerUpdateWatcher) {
	r.Lock()
	defer r.Unlock()
	r.watchers = append(r.watchers, f)
}

func (r *registry) loop() {
	for {
		// NB listenForEvents blocks.
		// Returning false means we should exit.
		if !r.listenForEvents() {
			return
		}

		// Sleep here so we don't hammer the
		// logs if docker is down
		time.Sleep(r.interval)
	}
}

func (r *registry) listenForEvents() bool {
	// First we empty the store lists.
	// This ensure any containers that went away in between calls to
	// listenForEvents don't hang around.
	r.reset()

	// Next, start listening for events.  We do this before fetching
	// the list of containers so we don't miss containers created
	// after listing but before listening for events.
	events := make(chan *docker_client.APIEvents)
	if err := r.client.AddEventListener(events); err != nil {
		log.Errorf("docker registry: %s", err)
		return true
	}
	defer func() {
		if err := r.client.RemoveEventListener(events); err != nil {
			log.Errorf("docker registry: %s", err)
		}
	}()

	if err := r.updateContainers(); err != nil {
		log.Errorf("docker registry: %s", err)
		return true
	}

	if err := r.updateImages(); err != nil {
		log.Errorf("docker registry: %s", err)
		return true
	}

	if err := r.updateNetworks(); err != nil {
		log.Errorf("docker registry: %s", err)
		return true
	}

	otherUpdates := time.Tick(r.interval)
	for {
		select {
		case event, ok := <-events:
			if !ok {
				log.Errorf("docker registry: event listener unexpectedly disconnected")
				return true
			}
			r.handleEvent(event)

		case <-otherUpdates:
			if err := r.updateImages(); err != nil {
				log.Errorf("docker registry: %s", err)
				return true
			}
			if err := r.updateNetworks(); err != nil {
				log.Errorf("docker registry: %s", err)
				return true
			}

		case ch := <-r.quit:
			r.Lock()
			defer r.Unlock()

			if r.collectStats {
				r.containers.Walk(func(_ string, c interface{}) bool {
					c.(Container).StopGatheringStats()
					return false
				})
			}
			close(ch)
			return false
		}
	}
}

func (r *registry) reset() {
	r.Lock()
	defer r.Unlock()

	if r.collectStats {
		r.containers.Walk(func(_ string, c interface{}) bool {
			c.(Container).StopGatheringStats()
			return false
		})
	}

	r.containers = radix.New()
	r.containersByPID = map[int]Container{}
	r.images = map[string]docker_client.APIImages{}
	r.networks = r.networks[:0]
}

func (r *registry) updateContainers() error {
	apiContainers, err := r.client.ListContainers(docker_client.ListContainersOptions{All: true})
	if err != nil {
		return err
	}

	for _, apiContainer := range apiContainers {
		r.updateContainerState(apiContainer.ID, nil)
	}

	return nil
}

func (r *registry) updateImages() error {
	images, err := r.client.ListImages(docker_client.ListImagesOptions{})
	if err != nil {
		return err
	}

	r.Lock()
	defer r.Unlock()

	for _, image := range images {
		r.images[trimImageID(image.ID)] = image
	}

	return nil
}

func (r *registry) updateNetworks() error {
	networks, err := r.client.ListNetworks()
	if err != nil {
		return err
	}

	r.Lock()
	r.networks = networks
	r.Unlock()

	return nil
}

func (r *registry) handleEvent(event *docker_client.APIEvents) {
	// TODO: Send shortcut reports on networks being created/destroyed?
	switch event.Status {
	case CreateEvent, RenameEvent, StartEvent, DieEvent, DestroyEvent, PauseEvent, UnpauseEvent, NetworkConnectEvent, NetworkDisconnectEvent:
		r.updateContainerState(event.ID, stateAfterEvent(event.Status))
	}
}

func stateAfterEvent(event string) *string {
	switch event {
	case DestroyEvent:
		return &StateDeleted
	default:
		return nil
	}
}

func (r *registry) updateContainerState(containerID string, intendedState *string) {
	r.Lock()
	defer r.Unlock()

	dockerContainer, err := r.client.InspectContainer(containerID)
	if err != nil {
		// Don't spam the logs if the container was short lived
		if _, ok := err.(*docker_client.NoSuchContainer); !ok {
			log.Errorf("Error processing event for container %s: %v", containerID, err)
			return
		}

		// Container doesn't exist anymore, so lets stop and remove it
		c, ok := r.containers.Get(containerID)
		if !ok {
			return
		}
		container := c.(Container)

		r.containers.Delete(containerID)
		delete(r.containersByPID, container.PID())
		if r.collectStats {
			container.StopGatheringStats()
		}

		if intendedState != nil {
			node := report.MakeNodeWith(report.MakeContainerNodeID(containerID), map[string]string{
				ContainerID:    containerID,
				ContainerState: *intendedState,
			})
			// Trigger anyone watching for updates
			for _, f := range r.watchers {
				f(node)
			}
		}
		return
	}

	// Container exists, ensure we have it
	o, ok := r.containers.Get(containerID)
	var c Container
	if !ok {
		c = NewContainerStub(dockerContainer, r.hostID, r.noCommandLineArguments, r.noEnvironmentVariables)
		r.containers.Insert(containerID, c)
	} else {
		c = o.(Container)
		// potentially remove existing pid mapping.
		delete(r.containersByPID, c.PID())
		c.UpdateState(dockerContainer)
	}

	// Update PID index
	if c.PID() > 1 {
		r.containersByPID[c.PID()] = c
	}

	// Trigger anyone watching for updates
	if err != nil {
		node := c.GetNode()
		for _, f := range r.watchers {
			f(node)
		}
	}

	// And finally, ensure we gather stats for it
	if r.collectStats {
		if dockerContainer.State.Running {
			if err := c.StartGatheringStats(r.client); err != nil {
				log.Errorf("Error gathering stats for container %s: %s", containerID, err)
				return
			}
		} else {
			c.StopGatheringStats()
		}
	}
}

// LockedPIDLookup runs f under a read lock, and gives f a function for
// use doing pid->container lookups.
func (r *registry) LockedPIDLookup(f func(func(int) Container)) {
	r.RLock()
	defer r.RUnlock()

	lookup := func(pid int) Container {
		return r.containersByPID[pid]
	}

	f(lookup)
}

// WalkContainers runs f on every running containers the registry knows of.
func (r *registry) WalkContainers(f func(Container)) {
	r.RLock()
	defer r.RUnlock()

	r.containers.Walk(func(_ string, c interface{}) bool {
		f(c.(Container))
		return false
	})
}

func (r *registry) GetContainer(id string) (Container, bool) {
	r.RLock()
	defer r.RUnlock()
	c, ok := r.containers.Get(id)
	if ok {
		return c.(Container), true
	}
	return nil, false
}

func (r *registry) GetContainerByPrefix(prefix string) (Container, bool) {
	r.RLock()
	defer r.RUnlock()
	out := []interface{}{}
	r.containers.WalkPrefix(prefix, func(_ string, v interface{}) bool {
		out = append(out, v)
		return false
	})
	if len(out) == 1 {
		return out[0].(Container), true
	}
	return nil, false
}

func (r *registry) GetContainerImage(id string) (docker_client.APIImages, bool) {
	r.RLock()
	defer r.RUnlock()
	image, ok := r.images[id]
	return image, ok
}

// WalkImages runs f on every image of running containers the registry
// knows of.  f may be run on the same image more than once.
func (r *registry) WalkImages(f func(docker_client.APIImages)) {
	r.RLock()
	defer r.RUnlock()

	// Loop over containers so we only emit images for running containers.
	r.containers.Walk(func(_ string, c interface{}) bool {
		image, ok := r.images[c.(Container).Image()]
		if ok {
			f(image)
		}
		return false
	})
}

// WalkNetworks runs f on every network the registry knows of.
func (r *registry) WalkNetworks(f func(docker_client.Network)) {
	r.RLock()
	defer r.RUnlock()

	for _, network := range r.networks {
		f(network)
	}
}

// ImageNameWithoutVersion splits the image name apart, returning the name
// without the version, if possible
func ImageNameWithoutVersion(name string) string {
	parts := strings.SplitN(name, "/", 3)
	if len(parts) == 3 {
		name = fmt.Sprintf("%s/%s", parts[1], parts[2])
	}
	parts = strings.SplitN(name, ":", 2)
	return parts[0]
}

redpajama_set_name: RedPajamaGithub