fwips:

like-lucy-in-the-sky:

why are the bad guys’ horses always menacing and demonic too like

is there some kind of horse breeder for evil villains

come to uncle jim’s evil horse stables: for all your villainous horseriding needs

image

(Reblogged from fwips)

Baf, #heartbleed ankoraŭ ne puriga ĉie…

(Source: Wikipedia)

chuff:

"International Conference Regarding the Use of Esperanto"

Esperanto is a synthetic language devised by Polish eye doctor Ludwik Lazar Zamenhof (1859–1917), who in 1887 published a pamphlet in Russian, Polish, French, and German describing Esperanto and proposing it as an easy-to-learn second language. An international Esperanto movement developed in the 1890s, culminating in the first world congress of Esperanto speakers in 1905. After World War I, the League of Nations considered adopting Esperanto as a working language and recommending that it be taught in schools, but proposals along these lines were vetoed by France. The League sponsored an international conference regarding the use of Esperanto, which took place in Geneva on April 18–20, 1922. This photograph shows the opening session of the conference. The League of Nations had two working languages: English and French. The photograph is from the archives of the League, which were transferred to the United Nations in 1946 and are housed at the UN office in Geneva. They were inscribed on the UNESCO Memory of the World register in 2010.

(Reblogged from chuff)

En la Vikikomunejo kaj en aliaj parencaj projektoj estas selektilo de lingvoj, kiu elstare montras la konstruitlingvon Kotava en la sekcio “tutmonda” apud Esperanto aŭ Interlingvao. Kio estas Kotava? Mi ĝin ne konas. Kutime mi uzas anglalingvan Vikipedion, tial mi serĉis tie. Sed tie estas nur la rimarko diranta, ke artikoloj pri Kotava kaj Romanova estis forigitaj, ĉar laŭdire ili ne estis menciindecaj (ang. non-notable). Tamen, esperantlingva Vikipedio havas artikolon pri ĝi. La plejparto de informaĵo por Kotava en la Interreto estas en lingvo franca. Kio strange! Ĉu iu parolas en Kotava tie ĉi?

Makefile: Makefile.m4
	m4 $^ > $@
kolshica:

SCOOTS IS OVERWEIGHTED.so we need more breezy dashes!

kolshica:

SCOOTS IS OVERWEIGHTED.
so we need more breezy dashes!

(Reblogged from kolshica)

I stated earlier that there is no point in changing passwords before tumblr changes their private keys. And they did just that before issuing the notice on top. However, the old certificate is NOT revoked yet at the time of my writing so if keys were leaked, attacker could still use them to impersonate tumblr without any kind of warning from your browser whatsoever. So verify manually that the site you are communicating with is not using the old certificate (click on the lock icon, look for certificate information and compare RSA moduli… jk, just compare fingerprints).

Tumblr wouldn’t have any need for changing certificates if they weren’t affected by heartbleed so henceforth I assume it was. It’s actually unlikely that server’s private key leaked, but it’s certainly possible and there is no way to verify whether it happened or not so revoking it is a must. What certainly leaked is buffers containing scraps of actual data transferred, esp. cookies and, yes, passwords. If you logged in during last week, you should assume your password is compromised. Regardless, it’s a good idea to change password now even if unlikely to be leaked. It’s a good hygiene.

Changing your passwords everywhere still serves no purpose. Though, if you used the same password somewhere else, fix it now and learn to use password manager.

It’s a bit disappointing that tumblr staff’s post on the matter contains mostly of FUD and doesn’t answer the most crucial question: was tumblr affected or not? Did tumblr use OpenSSL version 1.0.1–1.0.1f or 1.0.2-beta1? It didn’t spew its guts when I checked so either tumblr wasn’t affected at all or patched it before I checked. In later case server’s private keys should be tumblr’s first worry rather than our passwords. It makes absolutely NO sense to change passwords before tumblr’s private keys (and therefore also certificates) are regenerated from scratch.

At the time of my writing, tumblr presented a certificate signed in May 2013.

(Source: imgflip.com)