Commit graph

2668 commits

Author SHA1 Message Date
Brinck Slattery
fe14eeaee8
Add files via upload 2018-06-14 17:39:11 -04:00
Thomas Zarebczan
6ddbae61c3
update cover 2018-06-14 17:39:10 -04:00
Brinck Slattery
24dfc3fa44 Create 173-lbry-fund-launches.md (#596)
* Create 172-lbry-fund-launches.md
2018-06-14 14:32:27 -07:00
Jeremy Kauffman
8bf516d1c6 print year on blog posts 2018-06-14 10:08:25 -04:00
Thomas Zarebczan
a52f2f5372
Update startup-troubleshooting.md 2018-06-13 21:51:54 -04:00
Udit Patel
23936a1cae Mixed content weakens HTTPS fix18 (#628)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:12:32 -07:00
Udit Patel
46586c6b70 Mixed content weakens HTTPS fix17 (#627)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:12:06 -07:00
Udit Patel
c2bfd52a01 Mixed content weakens HTTPS fix16 (#626)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:11:50 -07:00
Udit Patel
257df92a84 Mixed content weakens HTTPS fix15 (#625)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:11:31 -07:00
Udit Patel
12bfc2a089 Mixed content weakens HTTPS fix14 (#624)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:10:45 -07:00
Udit Patel
4fd8681682 Mixed content weakens HTTPS fix13 (#623)
* Mixed content weakens HTTPS fix13

Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.

* Update 23-bravenewcoin.md
2018-06-10 14:10:05 -07:00
Udit Patel
1e6142f7e1 Mixed content weakens HTTPS fix11 (#622)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:09:28 -07:00
Udit Patel
39b1dab4e1 Mixed content weakens HTTPS fix10 (#621)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:08:58 -07:00
Udit Patel
0cf3fd636c Mixed content weakens HTTPS fix10 (#620)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 14:08:39 -07:00
Udit Patel
84340c1e4c Mixed content weakens HTTPS fix9 (#619)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:47:29 -07:00
Udit Patel
965f386fb6 Mixed content weakens HTTPS fix 1 (#611)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:46:45 -07:00
Udit Patel
cd80b540f6 Mixed content weakens HTTPS fix 2 (#612)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:46:20 -07:00
Udit Patel
d81921c8a2 Mixed content weakens HTTPS fix3 (#613)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:46:08 -07:00
Udit Patel
02b5585b30 Mixed content weakens HTTPS fix4 (#614)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:45:57 -07:00
Udit Patel
696acbb2a9 Mixed content weakens HTTPS fix5 (#615)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:45:46 -07:00
Udit Patel
6db8252fb7 Mixed content weakens HTTPS fix6 (#616)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:45:34 -07:00
Udit Patel
b9f57de1bd Mixed content weakens HTTPS fix7 (#617)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:45:07 -07:00
Udit Patel
76e16e24b8 Mixed content weakens HTTPS fix8 (#618)
Mixed content weakens HTTPS
Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties. Using these resources, an attacker can often take complete control over the page, not just the compromised resource.

Although many browsers report mixed content warnings to the user, by the time this happens, it is too late: the insecure requests have already been performed and the security of the page is compromised. This scenario is, unfortunately, quite common on the web, which is why browsers can't just block all mixed requests without restricting the functionality of many sites.
2018-06-10 12:44:19 -07:00
Udit Patel
3007a1a08b Update 161-nickatnyte.md (#608)
Update to https link
2018-06-10 10:08:38 -07:00
Kristian Polso
9a551c0c6f Closes #597 2018-06-10 10:59:51 -04:00
YULIUS KURNIAWAN KRISTIANTO
a102898daf Update 172-lbry-development-community-update-May-2018.md (#604)
add stack exchange widget
2018-06-09 13:16:29 -07:00
Julie Sigwart
1a84df77d7
Merge pull request #588 from ykris45/patch-5
add telegram icon and link to footer
2018-06-09 11:07:34 -07:00
YULIUS KURNIAWAN KRISTIANTO
17f6e588c0 change http to https (#605) for Reddit + Tumblr 2018-06-09 07:47:22 -07:00
Thomas Zarebczan
20587d5a2c
add Ruby progress 2018-06-08 19:14:48 -04:00
Thomas Zarebczan
dedc0e8235
remove message 2018-06-08 17:38:54 -04:00
Thomas Zarebczan
32d36a56a9
wallet message 2018-06-08 17:15:22 -04:00
Brinck Slattery
d1b351d48c
Update 3d-contest.php 2018-06-08 10:44:42 -04:00
Brinck Slattery
7ff1942e0a
Update 3d-contest.php 2018-06-08 10:43:30 -04:00
Brinck Slattery
8f5f8824fa
Add files via upload 2018-06-08 10:43:00 -04:00
Clement
6ca23ed6dc Update exchanges.md (#599)
update text
2018-06-08 07:14:26 -07:00
Jeremy Kauffman
5d0d4786b4
fix styling by adding line 2018-06-08 10:02:53 -04:00
Sean Yesmunt
b2fdce44fe
Merge pull request #603 from lbryio/fix-typo
fix typo
2018-06-08 00:17:50 -04:00
Sean Yesmunt
bd34a94f9c fix typo 2018-06-08 00:17:12 -04:00
Thomas Zarebczan
de696b58da
Grammar and spelling 2018-06-07 20:15:40 -04:00
Thomas Zarebczan
018ff71905
fix anchor 2018-06-07 16:24:43 -04:00
Thomas Zarebczan
75b51070d9
fix speech link 2018-06-07 16:09:22 -04:00
Julie Sigwart
71bcc88283
Rename 172-lbry-development-community-update-May-2018 to 172-lbry-development-community-update-May-2018.md 2018-06-07 12:58:28 -07:00
Julie Sigwart
9d39435103
Typos 2018-06-07 12:56:04 -07:00
Julie Sigwart
6bce061d72
Merge pull request #601 from lbryio/jsigwart-patch-1
Create 172-lbry-development-community-update-May-2018
2018-06-07 12:47:45 -07:00
Julie Sigwart
89b054c9bf
Rename 172--lbry-development-community-update-May-2018 to 172-lbry-development-community-update-May-2018 2018-06-07 12:46:23 -07:00
Julie Sigwart
852f269954
Create 172--lbry-development-community-update-May-2018 2018-06-07 12:43:23 -07:00
Thomas Zarebczan
5578752721
cover 2018-06-07 04:10:28 -07:00
Julie Sigwart
f73b820e5d
backgrounds for dev update 2018-06-06 21:55:25 -07:00
Julie Sigwart
65aa358d66
Merge pull request #600 from lbryio/revert-590-feature/update_fontawesome
Revert "Update fontawesome to latest version of 4" - reddit links break on header and footer, so reverting
2018-06-06 15:27:28 -07:00
Julie Sigwart
4f3657a12d
Revert "Update fontawesome to latest version of 4" 2018-06-06 15:26:31 -07:00