Showing posts with label Technical. Show all posts
Showing posts with label Technical. Show all posts

Friday, January 3, 2014

The security industry found its dream enemy in 2013 -- and new technical challenges too

IDG News Service - 2013 was the year we learned we must encrypt our data if we don't want the likes of the U.S. National Security Agency or the U.K. Government Communications Headquarters reading it as it crosses the Internet.

The security industry has the enemy it always dreamed of to help it make the case for encryption adoption, but users looking to secure their data and communications need to be wary of claims made in marketing messages. Securing data in motion is the priority, experts say, and some large Internet firms are already making progress in this area, but encrypting data at rest without losing its usefulness will prove a greater challenge.

"The NSA's surveillance has opened the eyes of many people around the world," Lamar Bailey, director of security research and development at security firm Tripwire said via email. "Security professionals have always known that this style of surveillance is possible with the right resources, but this episode has been a big wake-up call for everyone. Many countries and companies outside the U.S. are now taking a harder, more in-depth look at software and hardware that comes from the U.S., although the silver lining is that mainstream users are now more concerned with encrypting data and reviewing how their information is being shared."

The public debate sparked by the surveillance revelations in recent months has prompted some encouraging responses already: Google has encrypted the links between its data centers; Yahoo is working to do the same and has promised to enable SSL encryption by default for webmail and other services, and Twitter has enabled an SSL feature called forward secrecy, already implemented by Google and Facebook, which makes mass decryption of SSL traffic hard even if the website operator's master private key is compromised.

Some software vendors started developing alternatives to existing communication technologies, with the goal of providing end-to-end encryption and making upstream data interception harder. Secure communications provider Silent Circle launched an effort called the Dark Mail Alliance to develop a private a secure email protocol that encrypts metadata, not just message contents; Pirate Bay co-founder Peter Sunde is working with others on a secure crowd-funded mobile messaging application called Hemlis with distributed infrastructure hosted in privacy-friendly jurisdictions, and BitTorrent, the company behind the popular file-sharing protocol of the same name, is developing a peer-to-peer instant messaging application that encrypts messages directly between users and doesn't rely on central servers.

These and other examples send a clear message: securing the data transport channels to prevent unwanted upstream interception is a priority. The Internet Engineering Task Force, an organization that develops Internet standards, is already working toward this goal. Together with other Internet infrastructure groups, IETF expressed concern that the reported mass monitoring and surveillance by government agencies undermines the trust and confidence of Internet users globally.

The IDG News Service is a Network World affiliate.


View the original article here

Thursday, October 31, 2013

Technical Operations

Logo: TPP Send my CV via email

(Log in to keep track of your applications)

Salary£27,001-£29,500Additional salary infoSalary £28,000 ContractUnknownClosing dateContinuous recruitment LocationLeeds

Are you computer-obsessed? Are you fascinated by new technology and the latest gadgets? Is your house covered in computer parts and PC magazines? If so, we want to hear from you.

The TPP Technical Operations are looking for a new member of staff to join them. Highly skilled in a number of areas, this dynamic team plays a vital role in developing and maintaining our pioneering technologies. TPP are the best in world at what we do and we’re looking for the best to join us.

The successful candidate will need to learn new skills quickly and perform to a high standard in order to meet the wide variety of roles covered by the team but the job is rewarding and the experience invaluable.

The Vacancy
Our tasks don’t just involve our own offices and datacentres, but also include working closely with the largest names and most innovative companies in the industry. You will consult with other technical teams to diagnose national and global problems, often identifying and resolving problems before the end user has even noticed them.
Working within the infrastructure team means the successful candidate will receive training and gain experience in the following technical fields:

One of the largest SQL Server databases in the worldHighly available, high performance servers and storageNetwork, server and physical securityOperating at an international level

This is a challenging and rewarding job with salary and benefits to match. Opportunities to learn at TPP are continuous: as a member of the infrastructure team you will be given projects to manage, complicated faults to diagnose and new technologies to research.

In addition, each year, you’ll benefit from our five-day training course allowance (after one year’s service) which you can use to enhance your skill set.

Salary and Benefits
As a member of the infrastructure team, you will receive the following benefits along with the company-wide perks and benefits.

£28,000 starting salaryBUPA health and dental care (after six month’s service)30+ days holidayTraining allowance (after six month’s service)

No direct experience is necessary however candidates must demonstrate a passion for computing, have the right dedicated attitude, a great academic record and the ability to learn quickly.

To read what it's like to work at TPP and to see our full list of benefits, visit our website.

In addition candidates must have:

Minimum A and two Bs at A level2:1 or above in a computer related degreeAbility to concentrate and pay close attention to detailA natural problem solverAbility to think broadly and consider impacts across systems and within the organisationCalm under pressure

Any

No closing date, but apply as soon as possible.

To apply please email full CV and covering letter or post to:

TPP (Leeds) Ltd,
Mill House,
Troy Road,
Horsforth,
Leeds
LS18 5TN

Note that due to the high volume of applications, candidates failing to pass the initial selection will not be notified. Successful candidates will usually be contacted within two weeks.


View the original article here

Thursday, April 18, 2013

[Technical Comment] Comment on “Apatite 4He/3He and (U-Th)/He Evidence for an Ancient Grand Canyon”

Science 12 April 2013:
Vol. 340 no. 6129 p. 143
DOI: 10.1126/science.1233982 Karl E. Karlstrom1,*, John Lee2, Shari Kelley3, Ryan Crow1, Richard A. Young4, Ivo Lucchitta5, L. Sue Beard5, Rebecca Dorsey6, Jason W. Ricketts1, William R. Dickinson7, Laura Crossey1

1University of New Mexico, Albuquerque, NM 87131, USA.
2U.S. Geological Survey, Denver, CO 80225, USA.
3New Mexico Bureau of Geology and Mineral Resources, Socorro, NM 87801, USA.
4State University of New York, Geneseo, NY 14454, USA.
5U.S. Geological Survey, Flagstaff, AZ 86001, USA.
6University of Oregon, Eugene, OR 97403, USA.
7University of Arizona, Tucson, AZ 85721, USA. ?*Corresponding author. E-mail: kek1{at}unm.eduFlowers and Farley (Reports, 21 December 2012, p. 1616; published online 29 November 2012) propose that the Grand Canyon is 70 million years old. Starkly contrasting models for the age of the Grand Canyon—70 versus 6 million years—can be reconciled by a shallow paleocanyon that was carved in the eastern Grand Canyon 25 to 15 million years ago (Ma), negating the proposed 70 Ma and 55 Ma paleocanyons. Cooling models and geologic data are most consistent with a 5 to 6 Ma age for western Grand Canyon and Marble Canyon.

The “old” Grand Canyon hypothesis, reinvigorated by modeling of recent 4He/3He data in Flowers and Farley (1), posits that an early phase of canyon carving was accomplished by a northeast-flowing river 80 to 70 million years ago (Ma) followed by establishment of a west-flowing river by 55 Ma, such that the western Grand Canyon was “excavated to within a few hundred meters of modern depths by ~70 million years ago” (1, 2). The dramatically different “young” Grand Canyon hypothesis states that a majority of the canyon was carved by the west-flowing Colorado River in the past 5 to 6 million years (3, 4). Geologic data supporting the “young” canyon model include (i) 5.3-million-year age of earliest Colorado Plateau–derived sediments in the Salton Trough (5); (ii) 4.4-million-year age of oldest known Colorado River gravels (6); (iii) lack of pre-6 Ma Colorado River sediment immediately downstream of the mouth of Grand Canyon (7); (iv) geometry of north-flowing 70 to 18 Ma paleocanyons in western Grand Canyon (8); (v) southward-transported 60 to 50 Ma Hindu fanglomerate that was deposited across the modern course of the western Grand Canyon (9); (vi) semisteady incision rates over the past 4 million years sufficient to carve most of the Grand Canyon in 6 million years (10); and (vii) lack of Colorado Plateau detritus in early Tertiary deposits of the Los Angeles basin (11).

We believe that the thermochronologic data and modeling of Flowers and Farley also are consistent with a “young” Grand Canyon when reinterpreted to correct for tenuous assumptions. Their thermal models were generated from 4He/3He diffusion profiles and apatite 4He/3He and (U-Th)/He (Ahe) data for the eastern and western Grand Canyon (Fig. 1A), but we question their geological interpretations of these models for several reasons. Incomplete understanding of He diffusion in apatite poses considerable difficulties in assigning constrained cooling paths, requiring critical examination of modeling assumptions. One assumption used (1) was that apatite grains from each four-sample “ensemble” in the eastern and western Grand Canyon shared common cooling histories and can be modeled together. However, this is suspect because of structural complexities in both regions (12). Instead, existing AHe and apatite fission-track (AFT) data (12–15) show variability in thermochronologic ages and therefore nullify the extrapolation of results from a few samples to the entire Grand Canyon. Another questionable assumption (1) (see below) is that western Grand Canyon samples were heated enough to completely anneal apatite at 80 to 120 Ma.

Fig. 1 Fig. 1 Thermochronology data from the Grand Canyon region. (A) Map of the Grand Canyon region showing apatite helium samples discussed in the text (1, 13–15). (B) Carving of an Eastern paleocanyon from 25 to 15 Ma is indicated by different temperatures of rim- and river-level samples until ~25 Ma. (C) Western Grand Canyon thermal models are in conflict, but joint inversion of AFT and AHe data [purple curves, from (14)], suggest that the western Grand Canyon was carved in the the past 6 million years. (D) The top left diffusion profile (1) may fit the “young canyon” model if modeled without the highest temperature step. (E) Full data set of AHe ages (top) resembles predicted “young” canyon distribution of (1).

Joint inversion of independent AHe and AFT data sets is especially powerful and provides well-constrained cooling histories for river samples in the eastern Grand Canyon (14); these show that basement rocks cooled slowly from 80° to 70°C between 65 and 25 Ma, then cooled rapidly from 25 to 15 Ma. The geometry of their published rim-level samples (shown in our Fig. 1A) is not optimal for resolving paleocanyons, but all available data (12–15) suggest that rim- and river-level samples, now separated vertically by 1 to 1.5 km, resided at 45° to 55° and 80°C, respectively, from 60 to 25 Ma. There is no evidence for a paleocanyon until after 25 Ma, when rim- and river-level cooling paths converge (Fig. 1B). Similar data show that the Marble Canyon section of the eastern Grand Canyon was buried by ~2 km of rock, and hence no canyons existed there until after 10 Ma (14). The combined data (Fig. 1B) refute the hypothesis for carving of the eastern Grand Canyon by 55 Ma (1, 2).

The western Grand Canyon cooled earlier than the eastern Grand Canyon because of its proximity to the ancient Sevier/Laramide highlands. This region was eroded by northeast-flowing Laramide paleocanyons (9) and is cut by numerous faults with a history of recurring movement (12). A model from one 4He/3He sample (CP06-69) (Fig. 1C) suggests that rocks cooled to <30°C (~200 m depth) and have resided at these cool temperatures since 70 Ma (1). However, this interpretation conflicts with the joint inversion of AFT and AHe data from nearby samples (14), which suggests that these rocks cooled from ~60° to 40°C between 60 and 25 Ma (01-GC86) (Fig. 1C), compatible with ~1-km burial depth (the present depth below the rim). These conflicting results (1, 14) have several plausible explanations: (i) Sample “ensembles” from (1) span several known faults and therefore may not have shared a common cooling history. (ii) Western Grand Canyon samples accumulated considerable radiation damage during residence in the AHe partial retention zone for >600 million years and may not have been heated enough during the Cretaceous time to fully anneal grains, such that western Grand Canyon models should be rerun starting ~600 Ma to account for any incomplete annealing and inherited helium. (iii) When the combined AFT and AHe data sets (1, 12–14) are merged, the results of (1) are more closely reproduced by the “young” canyon than the “old” canyon model (Fig. 1E). The conflicting models (Fig. 1C) could both be correct if (iv) sample CP06-69 (1) was situated beneath a north-flowing paleocanyon near Separation Canyon, whereas sample 01GC-86 (14) was from an interfluve; or (v) CP06-69 was cooled on the upthrown side of an unrecognized Laramide reverse fault relative to 01GC-86. Although our knowledge of the north-flowing Laramide paleocanyon system is incomplete, existing thermochronologic data argue against a 70-Ma western Grand Canyon that followed the same path with nearly the same depth as the modern canyon.

A simple dichotomy of “old” canyon versus “young” canyon hypotheses is overly simplistic because the Grand Canyon includes different sections with different geologic histories. Older paleocanyons likely were reused or re-excavated once the river found its modern path and began eroding rapidly. Despite these complexities, existing data do not support the model for a 80- to 70-Ma northeast-flowing California river, nor a 55-Ma southwest-flowing Arizona river, that collectively carved the Grand Canyon to within a few hundred meters of its modern depth by Early Tertiary time. Instead, an overwhelming body of published geologic and thermochronologic evidence shows that a majority of the Grand Canyon—the canyon that we see from the rim today—has been carved in the past 5 to 6 million years by the Colorado River. Drainage integration at 5 to 6 Ma was likely facilitated by older paleocanyon segments, whose geometry is now coming into focus.

Received for publication 12 December 2012. Accepted for publication 25 February 2013. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Acknowledgments: Funding for the University of New Mexico coauthors (K.E.K., R.C., L.C., and J.W.R.) was from NSF EAR-0711546 and EAR-1119629.


View the original article here