assets/uml is gitignored (not docs/assets/uml)

This commit is contained in:
nicobo 2020-04-18 22:30:52 +02:00
parent 8815aab562
commit 20bb4e7e08
No known key found for this signature in database
GPG key ID: 2581E71C5FA5285F
4 changed files with 121 additions and 1 deletions

1
.gitignore vendored
View file

@ -1,2 +1,3 @@
.sass-cache
.jekyll-metadata
assets/uml/**

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 14 KiB

View file

@ -0,0 +1,54 @@
@startuml
@startuml
title
Bluetooth association models & security history
end title
(BR/EDR Legacy Pairing) as bredr_legacy_pairing
note right of bredr_legacy_pairing
Since the beginning
Lowest security (based on SAFER+ algorithms)
There is only **one pairing workflow**.
end note
(Secure Simple Pairing) as secure_simple_pairing
note right of secure_simple_pairing
Since 2.1 + EDR
Enhances security with stronger (FIPS) algorithms,
passive eavesdropping and MITM protections,
and **4 possible pairing workflows**.
Some security is still at the level of <i>BR/EDR legacy</i>.
end note
(BR/EDR Secure Connections) as bredr_legacy_secure_connections
note right of bredr_legacy_secure_connections
Since 4.1
Fills the remaining security gaps.
end note
(LE Legacy Pairing) as le_legacy_pairing
note left of le_legacy_pairing
Since 4.0
Similar to BR/EDR's <i>Secure Simple Pairing</i>
but with only **3 pairing workflows**
(misses <i>Numeric Comparison</i>)
and trades some security for usability.
end note
(LE Secure Connections) as le_secure_connections
note left of le_secure_connections
Since 4.2
Similar to <i>BR/EDR Secure Connections</i>,
also with **4 pairing workflow**.
end note
bredr_legacy_pairing -up-> secure_simple_pairing
secure_simple_pairing -up-> bredr_legacy_secure_connections : Security upgrade through\n<i>Secure Connections</i>
le_legacy_pairing -up-> le_secure_connections : Security upgrade through\n<i>Secure Connections</i>
@enduml
@enduml

View file

@ -1,4 +1,4 @@
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.6">Jekyll</generator><link href="https://www.nicolabs.net/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.nicolabs.net/" rel="alternate" type="text/html" /><updated>2020-04-16T23:47:37+02:00</updated><id>https://www.nicolabs.net/feed.xml</id><title type="html">nicolabs</title><subtitle>Work in progress...</subtitle><author><name>nicobo</name></author><entry><title type="html">Bypassing GitHubs Jekyll limitations</title><link href="https://www.nicolabs.net/2020/Bypassing-GitHub-Jekyll-limitations" rel="alternate" type="text/html" title="Bypassing GitHub's Jekyll limitations" /><published>2020-04-13T00:00:00+02:00</published><updated>2020-04-13T00:00:00+02:00</updated><id>https://www.nicolabs.net/2020/Bypassing-GitHub-Jekyll-limitations</id><content type="html" xml:base="https://www.nicolabs.net/2020/Bypassing-GitHub-Jekyll-limitations">&lt;p&gt;As I feared when I &lt;a href=&quot;/2016/Migrating-from-Drupal-to-Jekyll&quot;&gt;migrated to GitHubs hosting&lt;/a&gt;, it has become too complicated to overcome GitHubs limitations on Jekyll plugins and features.&lt;/p&gt;
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.6">Jekyll</generator><link href="https://www.nicolabs.net/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.nicolabs.net/" rel="alternate" type="text/html" /><updated>2020-04-18T22:28:54+02:00</updated><id>https://www.nicolabs.net/feed.xml</id><title type="html">nicolabs</title><subtitle>Work in progress...</subtitle><author><name>nicobo</name></author><entry><title type="html">Bypassing GitHubs Jekyll limitations</title><link href="https://www.nicolabs.net/2020/Bypassing-GitHub-Jekyll-limitations" rel="alternate" type="text/html" title="Bypassing GitHub's Jekyll limitations" /><published>2020-04-13T00:00:00+02:00</published><updated>2020-04-13T00:00:00+02:00</updated><id>https://www.nicolabs.net/2020/Bypassing-GitHub-Jekyll-limitations</id><content type="html" xml:base="https://www.nicolabs.net/2020/Bypassing-GitHub-Jekyll-limitations">&lt;p&gt;As I feared when I &lt;a href=&quot;/2016/Migrating-from-Drupal-to-Jekyll&quot;&gt;migrated to GitHubs hosting&lt;/a&gt;, it has become too complicated to overcome GitHubs limitations on Jekyll plugins and features.&lt;/p&gt;
&lt;p&gt;I just needed to create a &lt;a href=&quot;https://jekyllrb.com/docs/collections/&quot;&gt;&lt;em&gt;collection&lt;/em&gt;&lt;/a&gt; to put my &lt;a href=&quot;/2016/Migrating-from-Drupal-to-Jekyll&quot;&gt;“live drafts”&lt;/a&gt; into it, but the deprecated &lt;em&gt;jekyll-paginate&lt;/em&gt; plugin provided with GitHub pages didnt support collections.&lt;/p&gt;