32
41%
master: 41%

Ran 16 Feb 2019 04:40AM UTC

Jobs 1

Files 10

Run time 1s

Badge

Embed ▾

pending completion

Build # 32

Build Type

push

travis-ci

Committed by

kixelated

Commit Message

Use constant time comparison for auth verification

It's a subtle change. Get it?

Timing attacks rely on measuring the amount of time it takes for an
operation to complete. The idea is that programs will break out early on
error, and sometimes it can be abused.

In this case, an attacker could measure the time it takes to verify an
256 auth tags, each one starting with a different byte. `bytes.Equal`
will immediately return false if the first byte is wrong, otherwise
check the next byte and so on. This means that just one of the auth tags
will take longer than the rest, because the first byte will match.
You can repeat the process until you figure out the correct auth tag.

Run Details

302 of 741 relevant lines covered (40.76%)

10.94 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	32.1 (GO111MODULE=on)	16 Feb 2019 04:40AM UTC	0	40.76	Travis Job 32.1

Source Files on build 32

Detailed source file information is not available for this build.

pions / srtp / 32
41%
master: 41%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32

pions / srtp / 32 41% master: 41%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32

pions / srtp / 32
41%
master: 41%

README BADGES
x