Paolo Falcarin | 21 Apr 01:08 2014

Post-doc positions in software protection at UEL, London, UK

The Software Systems Engineering research group in the School of Architecture Computing and Engineering
at the University of East London, is looking for two candidates to carry out research activities in the
field of software protection. These research positions are funded by the FP7 European research project
ASPIRE (Advanced Software Protection: Integration, Research and Exploitation) and are supervised by
Dr Paolo Falcarin, who is ASPIRE's principal investigator in UEL.

ASPIRE will establish trustworthy software execution on untrusted mobile platforms (such as tablets and
smartphones) that lack custom secure hardware elements, but that have a persistent or occasional
network connection to a trusted remote system.

The Software Systems Engineering Research Group at UEL aims at investigating two strategic areas of
software engineering and security: 
(1) Software protection diversity and renewability;
(2) Security modelling and evaluation. 

In the first area, the research will explore software protection techniques such as anti-tampering,
remote attestation, software diversity and renewability on mobile apps built with Android NDK.
The scientific challenge is realizing dynamic renewability of a mobile application, by designing and
implementing  client-server support for secure code updates; such diversified run-time code updates
will serve different purposes: contrasting static analysis, reducing the attacker's time-frame and
implementing network-based protections (such as remote attestation).

In the second area, a decision support system will be developed within the project to assist developers in
adopting the configuration that best fits their specific protection requirements. The decision
support system will rely on a knowledge base and attack models. 
The challenge is building a knowledge base of software protection related attacks and evaluating the
effectiveness of protection by developing tools for attack analysis based on system modelling
techniques, such as Petri nets and Bayesian networks.

More information about the ASPIRE project is available at
(Continue reading)

Jason Iannone | 16 Apr 17:30 2014

Request - PKI/CA History Lesson

The more I read, the more bewildered I am by the state of the PKI.
The trust model's unwieldy system[1] of protocols, dependencies, and
outright assumptions begs to be exploited.  Add to that the browser
behavior for a self-signed certificate (RED ALERT! THE SKY IS
FALLING!) compared to a "trusted" site and we're in bizarro world.
I'd rather we close the gap and appreciate a secure transaction with
an unauthenticated party than proclaim all is lost when a self-signed
key is presented.  I see no reason to trust VeriSign or Comodo any
more than Reddit.  Assuming trust in a top heavy system of Certificate
Authorities, Subordinate Certificate Authorities[2], Registration
Authorities, and Validation Authorities[3] in a post bulk data
collection partnership world is a non-starter.  The keys are

With that, I ask for a history lesson to more fully understand the
PKI's genesis and how we got here.  Maybe a tottering complex
recursive heirarchical system of trust is a really great idea and I
just need to be led to the light.

Eric Mill | 12 Apr 19:40 2014

If not StartSSL, the next best CA for individuals?

(Setting aside how awful the CA system is generally...)

For those who still have a need to participate in it, and for those
angry at StartCom's refusal to waive[1][2] revocation fees for their
free class 1 certs, what's the best CA for the job?

Even if not free, I'm looking to recommend[3] something priced
attractively for individuals and non-commercial uses. The friendlier
the interface, and the more reliable and principled the customer
service, the better.

-- Eric



-- |  <at> konklone
Jeffrey Walton | 11 Apr 23:50 2014

NSA Said to Exploit Heartbleed Bug for Intelligence for Years

The U.S. National Security Agency knew for at least two years about a
flaw in the way that many websites send sensitive information, now
dubbed the Heartbleed bug, and regularly used it to gather critical
intelligence, two people familiar with the matter said.

The NSA’s decision to keep the bug secret in pursuit of national
security interests threatens to renew the rancorous debate over the
role of the government’s top computer experts.

Heartbleed appears to be one of the biggest glitches in the Internet’s
history, a flaw in the basic security of as many as two-thirds of the
world’s websites. Its discovery and the creation of a fix by
researchers five days ago prompted consumers to change their
passwords, the Canadian government to suspend electronic tax filing
and computer companies including Cisco Systems Inc. to Juniper
Networks Inc. to provide patches for their systems.
cryptography mailing list
cryptography <at>
Jeffrey Walton | 11 Apr 07:35 2014

Wild at Heart: Were Intelligence Agencies Using Heartbleed in November 2013?

Yesterday afternoon, Ars Technica published a story reporting two
possible logs of Heartbleed attacks occurring in the wild, months
before Monday's public disclosure of the vulnerability. It would be
very bad news if these stories were true, indicating that blackhats
and/or intelligence agencies may have had a long period when they knew
about the attack and could use it at their leisure.

In response to the story, EFF called for further evidence of
Heartbleed attacks in the wild prior to Monday. The first thing we
learned was that the SeaCat report was a possible false positive; the
pattern in their logs looks like it could be caused by ErrataSec's
masscan software, and indeed one of the source IPs was ErrataSec.

The second log seems much more troubling. We have spoken to Ars
Technica's second source, Terrence Koeman, who reports finding some
inbound packets, immediately following the setup and termination of a
normal handshake, containing another Client Hello message followed by
the TCP payload bytes 18 03 02 00 03 01 40 00 in ingress packet logs
from November 2013. These bytes are a TLS Heartbeat with contradictory
length fields, and are the same as those in the widely circulated
proof-of-concept exploit.
Scott G. Kelly | 10 Apr 19:09 2014

question about heartbleed on Linux

Does heartbleed allow one to read (discarded, freed) physical memory containing data from the OS and/or
other processes in linux?

A friend and I were discussing this. If the memory management is "lazy" (doesn't clear on page
allocation/free), and if processes don't clear their own memory, I wondered if heartbleed would expose
anything. My friend thinks "modern" operating systems clear memory to prevent inter-process data
leakage. Of course, I agree that this is security goodness, but I wonder if, in the name of performance,
this is "optional".

I'm poking around in linux memory management code in between other tasks, but I'll bet somebody here knows
the answer. Anyone?
travis+ml | 10 Apr 02:17 2014

crypto mdoel based on cardiorespiratory coupling

This is nonsense, right?  Unbounded in the sense of relying on secrecy of the unbounded number of algorithms?

Remediating... like a BOSS.

cryptography mailing list
Pranesh Prakash | 8 Apr 04:13 2014


Dear all,
In the March IETF 89 meeting in London, there were renewed discussions 
around end-to-end encryption in XMPP.

Here is the recording of the session:

There was basic agreement that OTR is a horrible fit for XMPP since it 
doesn't provide full stanza encryption.  The very reasons for the 
benefits of OTR (its ability to be protocol-agnostic) are the reasons 
for its shortfalls too.

However, there is no clear alternative.  The closest is 
draft-miller-xmpp-e2e.  The one clear verdict was that more contributors 
are required.

The discussions are happening at:

If anyone has the time to make contributions, please do jump in (and 
spread the word).

~ Pranesh

Pranesh Prakash
Policy Director, Centre for Internet and Society
T: +91 80 40926283 | W:
(Continue reading)

Edwin Chu | 7 Apr 23:53 2014

The Heartbleed Bug is a serious vulnerability in OpenSSL


A latest story for OpenSSL

The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).

The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop communications, steal data directly from the services and users and to impersonate services and users.

cryptography mailing list
Eric Mill | 4 Apr 20:08 2014

Github Pages now supports SSL

I know most of the people on here have transcended the earthbound, maudlin Certificate Authority system, but as services-adopting-SSL-news goes, I'm particular excited about Github Pages, which started quietly supporting SSL for * domains a few weeks back.

I'm excited because Github Pages is powerful, verrrrry flexible, and totally free. AFAIK, it's the only major blog/web host that gives you free SSL, backed by a high quality CDN (since everything is static files).

To promote the occasion and nudge Github to take it further, I wrote up my own experience, and a little how-to for forcing redirects via Jekyll:

Along with Cloudflare's 2014 plan to offer SSL termination for free, and their stated plan to double SSL on the Internet by end of year, the barrier to HTTPS everywhere is dropping rapidly.

cryptography mailing list
ianG | 4 Apr 15:09 2014


Has anyone looked at Tails?

 Crucial encryption tool enabled NSA reporting on shoestring budget

Big players in Snowden revelations publicly praise Tails, in hope of
gaining much-needed funding for the tool

While followers of the NSA leaks stories and everyday privacy
enthusiasts may be well acquainted with encryption tools like PGP, the
best-practice privacy tool — the operating system enabling much of the
Snowden leaks reporting — is known to few but experts.

On Wednesday, however, three key NSA revelation journalists (Laura
Poitras, Glenn Greenwald and Bart Gellman) spoke publicly about the
importance of Tails — a tool that forces privacy best-practices by
default. As Trevor Timm reported, it’s essentially the sine qua non of
reporting on sensitive stories. However, as Timm notes, the “vital” tool
“is incredibly underfunded. Tails’ 2013 expense report shows that they
only had an operating budget of around 42,000 euros, which is less than
$60,000.” In an effort to garner donations, the journalists spoke out
for the first time at the Freedom of the Press Foundation site about
Tails’ importance:

    Laura Poitras: “I’ve been reluctant to go into details about the
different steps I took to communicate securely with Snowden to avoid
those methods being targeted. Now that Tails gives a green light, I can
say it has been an essential tool for reporting the NSA story. It is an
all-in-one secure digital communication system (GPG email, OTR chat, Tor
web browser, encrypted storage) that is small enough to swallow. I’m
very thankful to the Tail developers for building this tool.”

    Glenn Greenwald: “Tails have been vital to my ability to work
securely on the NSA story. The more I’ve come to learn about
communications security, the more central Tails has become to my approach.”

    Barton Gellman: “Privacy and encryption work, but it’s too easy to
make a mistake that exposes you. Tails puts the essential tools in one
place, with a design that makes it hard to screw them up. I could not
have talked to Edward Snowden without this kind of protection. I wish
I’d had it years ago.”

Timm ran down the key aspects of how Tails renders best-practice privacy
communications a default for its users:

    It forces all of your web traffic through the Tor anonymity network,
so you don’t have to configure any of the settings on any program.
    It allows you to use GPG encryption when you are emailing and/or OTR
encryption while instant messaging, right out of the box.
    It allows journalists to work on sensitive documents, edit audio and
video, and store all their files encrypted.
    Critically, Tails never actually touches your hard drive and
securely wipes everything you’ve done every time you shut it down
(unless you specifically save it on an encrypted drive). This serves two
important purposes: first, it helps journalists who are operating in
environments or on networks that may already be compromised by
governments or criminals.

Natasha Lennard

Natasha Lennard is an assistant news editor at Salon, covering
non-electoral politics, general news and rabble-rousing. Follow her on
Twitter  <at> natashalennard, email nlennard@...