Skip to content

Commit b200f05

Browse files
committed
cleanup: remove Travis CI references
1 parent b06579a commit b200f05

File tree

3 files changed

+3
-39
lines changed

3 files changed

+3
-39
lines changed

.coveralls.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
service_name: travis-ci
1+
service_name: github
22

3-
src_dir: lib
3+
src_dir: src
44

55
coverage_clover: tests/build/logs/clover.xml
66

.travis.yml

Lines changed: 0 additions & 36 deletions
This file was deleted.

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ A replay attack is basically try to reuse an intercepted valid SAML Message in o
171171
SAML Messages have a limited timelife (NotBefore, NotOnOrAfter) that
172172
make harder this kind of attacks, but they are still possible.
173173

174-
In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs alredy validated and processed. Those values only need
174+
In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs already validated and processed. Those values only need
175175
to be stored the amount of time of the SAML Message life time, so
176176
we don't need to store all processed message/assertion Ids, but the most recent ones.
177177

0 commit comments

Comments
 (0)