POODLE-Angriff auf SSL 3.0 im Webbrowser verhindern

Übersicht:

Die Sicherheitslücke “POODLE” kann ausgenutzt werden, wenn sowohl Client als auch Server das Protokoll SSL Version 3.0 unterstützen. Also kann der Abgriff verunmöglicht werden, indem man die Unterstützung am Client (in diesem Fall also am Webbrowser) deaktiviert.

In Firefox:

Adresse aufrufen: about:config

Schlüssel suchen: security.tls.version.min

Wert ändern von 0 auf 1

In Internet Explorer:

Internetoptionen -> Erweitert -> Checkbox “SSL 3.0 verwenden” deaktivieren

Google Chrome:

Die Startverknüfung von Chrome ändern zu

chrome.exe --ssl-version-min=tls1

Eine detaillierte Anleitung mit Screenshots findet sich hier:

Andere Browser:

Apple Safari: Mir ist keine Möglichkeit bekannt. 😀

 

LibreOffice: Disable Typographic Quotes in Preformatted Text

Just so that I will never forget it again, because this now has been the second time that I had to look it up:

For a software manual, I made a paragraph style “Program Code” that was derived from “Preformatted Text”. The first thing I tried typing in was

10 PRINT "HELLO WORLD"
20 GOTO 10

LibreOffice 4 (like OpenOffice) has “Smart Quotes” enabled by default, and as I was typing them in it began replacing the double-quotes with complex typographic quotation marks according to my document’s Locale. For programming language text this is inappropriate.

The option “Extras → Auto Correct Options → Smart Quotes” can only be turned off on an all-or-nothing basis, but for natural language texts I would like to keep the behavior activated.

The solution:

Modify your paragraph style for code, for example type <F11> for the styles list, choose the paragraph styles tab, right-click on the style “Preformatted Text” and choose “Modify”.

In the “Font” tab, below the “Style” selection box, you see a dropdown menu “Language”. Set this to “None” and click “Ok”.

From then on, “Auto Correct” will no longer apply “Smart Quotes” to that style.

Not Being Tracked by Functions In WordPress Core

Install the plugin “Disable Google Fonts” to disable the loading of “OpenSans” from Google when using WP admin. The font brings no advantages over the standard appearance of WP admin.

Note: “Disable Google Fonts” is abandoned, and WordPress core apparently stopped loading fonts from Google.

Install the plugin “Disable Emojis” to disable the loading of an external SVG. 😀

Auf den Spuren römischer Infrastruktur

Ein Besuch auf einem römischen Bauernhof

Die Tage habe ich die “Villa Rustica”, also den römischen Gutshof im Wiesenbacher Forst “Herrenwald” besucht. Es handelte sich um einen landwirtschaftlichen Betrieb römischer Zeit mit Ackerbau und Viehzucht aus der Zeit von 130 bis nicht später als 260 n. Chr.

Read More »

Using VIm’s “:v” to Delete All Lines NOT Containing a Pattern

Addendum to my previous post

Using VIm’s “Negative Lookahead” to Delete All Lines NOT Containing a Pattern

I received a message from a reader who goes by the name of “bw1” who points out that my task “to delete all lines in the current file not containing the string foo” can easily be accomplished by issuing this command

:v/foo/d

🙂 I should read the VIm documentation once in a while!

Text-Console Barchart of Storage Utilization

Written as a Bourne Shell-Script that invokes a Perl one-liner:

LC_ALL=C df -kPT | perl -ane '!/(^Filesystem|tmpfs)/ && do {
   printf("%-33s: %s\n", $F[0], "*" x int((`tput cols`-35) * $F[3] / $F[2]))
}'

 

Using VIm’s “Negative Lookahead” to Delete All Lines NOT Containing a Pattern

UPDATE:

Please note that “bw1” has notified me of a much simpler solution than what is described here; please see

Using VIm’s “:v” Command to Delete All Lines NOT Containing a Pattern

Some statements have been struck through in the article below because they are false.

I want to delete all lines in the current file not containing the string foo:

:g/^.*?\@!foo/d

Explanation: Using the global command g (“act on range or entire file”) like :g/pattern/d applies the command d (“delete line”) to any line in the current file that matches pattern.

Since VIm generally does not support inverting RegExps (for example like sed does with the modifier !), I employ the “negative lookahead operator” @! (that has to be escaped \@!) of VIm-RegExp-syntax.

Since, in VIm RegExp syntax, look-ahead must follow something (why? I don’t know) I precede it with ^.*, but this is not enough, since it renders the obscure error E62: Nested \@ (why? I don’t know).

But it works if I make the preceeding term optional using the ? modifier. It’s a horribly inefficient RegExp, but it’s shortest to write (which is what VI-commands are all about).

And now you know that, too. 😀

P.S.: If you know a shorter version let me know –  FYI, I already know

:%!sed /foo/\!d

and it does not count – VIm onboard stuff only! 😉

Update: YouTube “Userstyle”

I have updated my YouTube Userstyle to the latest names they have given to their BS.

You can visit the style’s entry at userstyles.org for review and installation:

See also: Original announcement (20 Nov 2013).