andunix.net

info:java:firefox_java-plugin

andunix (andunix@undisclosed.example.com) — 2021-12-10T23:05:15+00:00

Install the Java-Plugin for Firefox

To install the Java plugin for Firefox, you have to create a symlink from Firefox's plugin directory /usr/lib/firefox-addons/plugins/ to the file libnpjp2.so in the JRE's “lib” dir.

sudo ln -s \
  ${JAVA_HOME}/jre/lib/amd64/libnpjp2.so \
  /usr/lib/firefox-addons/plugins/libnpjp2.so

Please note, that I tested this with Ubuntu 14.04, the “plugin” directory may be somewhere else on your system.

java, plugin, linux, ubunutu, sysadmin

info:cryptography:plaintext

andunix (andunix@undisclosed.example.com) — 2021-12-10T23:04:30+00:00

Plaintext

The plaintext is unencrypted and unsigned text. It's the payload which then get's signed and/or encrypted.

Wikipedia defines plaintext as:

In cryptography, plaintext is information a sender wishes to transmit to a receiver. Cleartext is often used as a synonym. Before the computer era, plaintext most commonly meant message text in the language of the communicating parties. Plaintext has reference to the operation of cryptographic algorithms, usually encryption algorithms, and is the input upon which they operate. Cleartext, by contrast, refers to data that is transmitted or stored unencrypted (that is, 'in the clear').

info:link:sidebar

andunix (andunix@undisclosed.example.com) — 2021-12-10T22:04:56+00:00

andunix Infos

info:link:index

andunix (andunix@undisclosed.example.com) — 2021-12-10T22:04:34+00:00

Link Lists

link, list

info:link:dokuwiki_plugins

andunix (andunix@undisclosed.example.com) — 2021-12-10T22:04:27+00:00

DokuWiki Plugins

This is a list of DokuWiki plugins I'm using.

An error occurred while fetching this feed: http://link.andunix.info/rss.php/andunix/dokuwiki%2Badd-on?sort=title_asc

dokuwiki, add-on, list, link

playground:playground

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:08:29+00:00

PlayGround

Formatting Syntax

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:08:14+00:00

Formatting Syntax

DokuWiki supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing “Edit this page”. If you want to try something, just use the playground page. The simpler markup is easily accessible via quickbuttons, too.

Basic Text Formatting

DokuWiki supports bold, italic, underlined and monospaced texts. Of course you can combine all these.

DokuWiki supports **bold**, //italic//, __underlined__ and ''monospaced'' texts.
Of course you can **__//''combine''//__** all these.

You can use _subscript and ^superscript, too.

You can use <sub>subscript</sub> and <sup>superscript</sup>, too.

You can mark something as ~~deleted~~ as well.

You can mark something as <del>deleted</del> as well.

Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line.

This is some text with some linebreaks
Note that the two backslashes are only recognized at the end of a line
or followed by
a whitespace \\this happens without it.

This is some text with some linebreaks\\ Note that the
two backslashes are only recognized at the end of a line\\
or followed by\\ a whitespace \\this happens without it.

You should use forced newlines only if really needed.

Links

DokuWiki supports multiple ways of creating links.

External

External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: This Link points to google. Email addresses like this one: andi@splitbrain.org are recognized, too.

DokuWiki supports multiple ways of creating links. External links are recognized
automagically: http://www.google.com or simply www.google.com - You can set
link text as well: [[http://www.google.com|This Link points to google]]. Email
addresses like this one: <andi@splitbrain.org> are recognized, too.

Internal

Internal links are created by using square brackets. You can either just give a pagename or use an additional link text.

Internal links are created by using square brackets. You can either just give
a [[pagename]] or use an additional [[pagename|link text]].

Wiki pagenames are converted to lowercase automatically, special characters are not allowed.

You can use namespaces by using a colon in the pagename.

You can use [[some:namespaces]] by using a colon in the pagename.

For details about namespaces see namespaces.

Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to this Section.

This links to [[syntax#internal|this Section]].

Notes:

Links to existing pages are shown in a different style from nonexisting ones.
DokuWiki does not use CamelCase to automatically create links by default, but this behavior can be enabled in the config file. Hint: If DokuWiki is a link, then it's enabled.
When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.

Interwiki

DokuWiki supports Interwiki links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: Wiki.

DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].

Windows Shares

Windows shares like this are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate Intranet.

Windows Shares like [[\\server\share|this]] are recognized, too.

Notes:

For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the “local zone”).
For Mozilla and Firefox it can be enabled through different workaround mentioned in the Mozilla Knowledge Base. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in conf/lang/en/lang.php (more details at localization):
conf/lang/en/lang.php
```
<?php
/**
 * Customization of the english language file
 * Copy only the strings that needs to be modified
 */
$lang['js']['nosmblinks'] = '';
```

Image Links

You can also use an image to link to another internal or external page by combining the syntax for links and images (see below) like this:

[[http://php.net|{{wiki:dokuwiki-128.png}}]]

Please note: The image formatting is the only formatting syntax accepted in link names.

The whole image and link syntax is supported (including image resizing, internal and external images and URLs and interwiki links).

Footnotes

You can add footnotes ¹⁾ by using double parentheses.

You can add footnotes ((This is a footnote)) by using double parentheses.

Sectioning

You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically – this can be disabled by including the string ~~NOTOC~~ in the document.

Headline Level 3

Headline Level 4

Headline Level 5

==== Headline Level 3 ====
=== Headline Level 4 ===
== Headline Level 5 ==

By using four or more dashes, you can make a horizontal line:

Media Files

You can include external and internal images, videos and audio files with curly brackets. Optionally you can specify the size of them.

Real size:

Resize to given width:

Resize to given width and height²⁾:

Resized external image:

Real size:                        {{wiki:dokuwiki-128.png}}
Resize to given width:            {{wiki:dokuwiki-128.png?50}}
Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
Resized external image:           {{https://secure.php.net/images/php.gif?200x50}}

By using left or right whitespaces you can choose the alignment.

{{ wiki:dokuwiki-128.png}}
{{wiki:dokuwiki-128.png }}
{{ wiki:dokuwiki-128.png }}

Of course, you can add a title (displayed as a tooltip by most browsers), too.

{{ wiki:dokuwiki-128.png |This is the caption}}

For linking an image to another page see Image Links above.

Supported Media Formats

DokuWiki can embed the following media formats directly.

Image	`gif`, `jpg`, `png`
Video	`webm`, `ogv`, `mp4`
Audio	`ogg`, `mp3`, `wav`
Flash	`swf`

If you specify a filename that is not a supported media format, then it will be displayed as a link instead.

By adding ?linkonly you provide a link to the media without displaying it inline

{{wiki:dokuwiki-128.png?linkonly}}

dokuwiki-128.png This is just a link to the image.

Fallback Formats

Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.

For example consider this embedded mp4 video:

{{video.mp4|A funny video}}

When you upload a video.webm and video.ogv next to the referenced video.mp4, DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.

Additionally DokuWiki supports a “poster” image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a video.jpg file would work.

Lists

Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a * for unordered lists or a - for ordered ones.

This is a list
The second item
- You may have different levels
Another item

The same list but ordered
Another item
1. Just use indention for deeper levels
That's it

  * This is a list
  * The second item
    * You may have different levels
  * Another item

  - The same list but ordered
  - Another item
    - Just use indention for deeper levels
  - That's it

Also take a look at the FAQ on list items.

Text Conversions

DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.

The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.

Text to Image Conversions

DokuWiki converts commonly used emoticons to their graphical equivalents. Those Smileys and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:

8-)
8-O
:-(
:-)
=)
:-/
:-\
:-?
:-D
:-P
:-O
:-X
:-|
;-)
^_^
:?:
:!:
LOL
FIXME
DELETEME

Text to HTML Conversions

Typography: DokuWiki can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.

→ ← ↔ ⇒ ⇐ ⇔ » « – — 640×480 © ™ ® “He thought 'It's a man's world'…”

-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
"He thought 'It's a man's world'..."

The same can be done to produce any kind of HTML, it just needs to be added to the pattern file.

There are three exceptions which do not come from that pattern file: multiplication entity (640×480), 'single' and “double quotes”. They can be turned off through a config option.

Quoting

Some times you want to mark some text to show it's a reply or comment. You can use the following syntax:

I think we should do it

> No we shouldn't

>> Well, I say we should

> Really?

>> Yes!

>>> Then lets do it!

I think we should do it

No we shouldn't

Well, I say we should

Really?

Yes!

Then lets do it!

Tables

DokuWiki supports a simple syntax to create tables.

Heading 1	Heading 2	Heading 3
Row 1 Col 1	Row 1 Col 2	Row 1 Col 3
Row 2 Col 1	some colspan (note the double pipe)
Row 3 Col 1	Row 3 Col 2	Row 3 Col 3

Table rows have to start and end with a | for normal rows or a ^ for headers.

^ Heading 1      ^ Heading 2       ^ Heading 3          ^
| Row 1 Col 1    | Row 1 Col 2     | Row 1 Col 3        |
| Row 2 Col 1    | some colspan (note the double pipe) ||
| Row 3 Col 1    | Row 3 Col 2     | Row 3 Col 3        |

To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!

Vertical tableheaders are possible, too.

	Heading 1	Heading 2
Heading 3	Row 1 Col 2	Row 1 Col 3
Heading 4	no colspan this time
Heading 5	Row 2 Col 2	Row 2 Col 3

As you can see, it's the cell separator before a cell which decides about the formatting:

|              ^ Heading 1            ^ Heading 2          ^
^ Heading 3    | Row 1 Col 2          | Row 1 Col 3        |
^ Heading 4    | no colspan this time |                    |
^ Heading 5    | Row 2 Col 2          | Row 2 Col 3        |

You can have rowspans (vertically connected cells) by adding ::: into the cells below the one to which they should connect.

Heading 1	Heading 2	Heading 3
Row 1 Col 1	this cell spans vertically	Row 1 Col 3
Row 2 Col 1		Row 2 Col 3
Row 3 Col 1		Row 2 Col 3

Apart from the rowspan syntax those cells should not contain anything else.

^ Heading 1      ^ Heading 2                  ^ Heading 3          ^
| Row 1 Col 1    | this cell spans vertically | Row 1 Col 3        |
| Row 2 Col 1    | :::                        | Row 2 Col 3        |
| Row 3 Col 1    | :::                        | Row 2 Col 3        |

You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.

Table with alignment
right	center	left
left	right	center
xxxxxxxxxxxx	xxxxxxxxxxxx	xxxxxxxxxxxx

This is how it looks in the source:

^           Table with alignment           ^^^
|         right|    center    |left          |
|left          |         right|    center    |
| xxxxxxxxxxxx | xxxxxxxxxxxx | xxxxxxxxxxxx |

Note: Vertical alignment is not supported.

No Formatting

If you need to display text exactly like it is typed (without any formatting), enclose the area either with <nowiki> tags or even simpler, with double percent signs %%.

This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it. The same is true for //__this__ text// with a smiley ;-).

<nowiki>
This is some text which contains addresses like this: http://www.splitbrain.org and **formatting**, but nothing is done with it.
</nowiki>
The same is true for %%//__this__ text// with a smiley ;-)%%.

Code Blocks

You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags <code> or <file>.

This is text is indented by two spaces.

This is preformatted code all spaces are preserved: like              <-this

This is pretty much the same, but you could use it to show that you quoted a file.

Those blocks were created by this source:

  This is text is indented by two spaces.

<code>
This is preformatted code all spaces are preserved: like              <-this
</code>

<file>
This is pretty much the same, but you could use it to show that you quoted a file.
</file>

Syntax Highlighting

DokuWiki can highlight sourcecode, which makes it easier to read. It uses the GeSHi Generic Syntax Highlighter – so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. <code java> or <file java>.

/**
 * The HelloWorldApp class implements an application that
 * simply displays "Hello World!" to the standard output.
 */
class HelloWorldApp {
    public static void main(String[] args) {
        System.out.println("Hello World!"); //Display the string.
    }
}

The following language strings are currently recognized: 4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic

There are additional advanced options available for syntax highlighting, such as highlighting lines or adding line numbers.

Downloadable Code Blocks

When you use the <code> or <file> syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this:

<file php myexample.php>
<?php echo "hello world!"; ?>
</file>

myexample.php

<?php echo "hello world!"; ?>

If you don't want any highlighting but want a downloadable file, specify a dash (-) as the language code: <code - myfile.foo>.

Embedding HTML and PHP

You can embed raw HTML or PHP code into your documents by using the <html> or <php> tags. (Use uppercase tags if you need to enclose block level elements.)

HTML example:

<html>
This is some <span style="color:red;font-size:150%;">inline HTML</span>
</html>
<HTML>
<p style="border:2px dashed red;">And this is some block HTML</p>
</HTML>

This is some inline HTML

And this is some block HTML

PHP example:

<php>
echo 'The PHP version: ';
echo phpversion();
echo ' (generated inline HTML)';
</php>
<PHP>
echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';
</PHP>

echo 'The PHP version: '; echo phpversion(); echo ' (inline HTML)';

echo '<table class="inline"><tr><td>The same, but inside a block level element:</td>';
echo '<td>'.phpversion().'</td>';
echo '</tr></table>';

Please Note: HTML and PHP embedding is disabled by default in the configuration. If disabled, the code is displayed instead of executed.

RSS/ATOM Feed Aggregation

DokuWiki can integrate data from external XML feeds. For parsing the XML feeds, SimplePie is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:

Parameter	Description
any number	will be used as maximum number items to show, defaults to 8
reverse	display the last items in the feed first
author	show item authors names
date	show item dates
description	show the item description. If HTML is disabled all tags will be stripped
nosort	do not sort the items in the feed
n[dhm]	refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours).

The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. DokuWiki will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells DokuWiki to re-render the page if it is more than refresh period since the page was last rendered.

By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the reverse parameter, or display the feed as is with nosort.

Example:

{{rss>http://slashdot.org/index.rss 5 author date 1h }}

As NASA Celebrates Successful Deployment of James Webb Telescope Mirror - What Happens Next? by EditorDavid (2022-01-09 20:36)
America's FAA Reveals 50 Airports Getting '5G Buffer' Zones for Six Months by EditorDavid (2022-01-09 19:38)
The Boy King of YouTube by EditorDavid (2022-01-09 18:34)
Threat Actors Can Simulate IPhone Reboots and Keep IOS Malware On a Device by EditorDavid (2022-01-09 17:34)
The Origin of the Blinking Cursor by EditorDavid (2022-01-09 16:34)

Control Macros

Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:

Macro	Description
~~NOTOC~~	If this macro is found on the page, no table of contents will be created
~~NOCACHE~~	DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the <php> syntax above is used), adding this macro will force DokuWiki to rerender a page on every call

Syntax Plugins

DokuWiki's syntax can be extended by Plugins. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:

Blog 2020-09-19 by Michael Hamann, Michael Klier, Gina Haeussge
Use DokuWiki as blogging tool. (previous authors: Esther Brunner)
Cloud Plugin 2020-09-27 by Michael Hamann, Michael Klier, Gina Haeussge
Displays the most used words in a word cloud.
Dir Plugin 2008-06-28 by Jacobus Geluk
Shows pages in one or namespaces in a table or list
Editor Plugin 2020-12-13 by Gina Häußge, Michael Klier, Esther Brunner
Displays a list of recently changed wiki pages by a given author
Feed Plugin 2020-10-26 by Michael Klier, Gina Haeussge
Generates feeds for other plugins
Indexmenu Plugin 2020-07-31 by Samuele Tognini
Show a customizable and sortable index for a namespace
Info Plugin 2020-06-04 by Andreas Gohr
Displays information about various DokuWiki internals
Meta plugin 2021-10-16 by Michael Hamann
Set Metadata for the current page. (previous authors: Esther Brunner, Gina Häußge, Michael Klier)
Note Plugin 2020-06-28 by Olivier Cortès, Eric Hameleers, Christopher Smith, Aurélien Bompard, LarsDW223
Add Note/Important/Tip/Warning Capability (DIV+CSS box)
Pagelist Plugin 2020-09-27 by Matthias Schulte, Michael Hamann, Michael Klier, Gina Haeussge
Lists pages in a nice formatted way
Tag Plugin 2020-12-02 by Michael Hamann, Gina Häussge, Christopher Smith, Michael Klier, Esther Brunner
tag wiki pages

¹⁾

This is a footnote

²⁾

when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing

DokuWiki

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:08:05+00:00

DokuWiki

DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It is loved by users for its clean and readable Formatting Syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make DokuWiki especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki.

Read the DokuWiki Manual to unleash the full power of DokuWiki.

Download

DokuWiki is available at https://download.dokuwiki.org/

All documentation and additional information besides the syntax description is maintained in the DokuWiki at www.dokuwiki.org.

About DokuWiki

Installing DokuWiki

Using DokuWiki

Customizing DokuWiki

DokuWiki Feedback and Community

Copyright

2004-2020 © Andreas Gohr andi@splitbrain.org³⁾ and the DokuWiki Community

The DokuWiki engine is licensed under GNU General Public License Version 2. If you use DokuWiki in your company, consider donating a few bucks .

Not sure what this means? See the FAQ on the Licenses.

³⁾

Please do not contact me for help and support – use the mailinglist or forum instead

Welcome to your new DokuWiki

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:07:51+00:00

Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,
– the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn't exist, this link will be red: start.

Go on, follow that link and create the page. If you need help with using the syntax you can always refer to the syntax page.

You might also want to use a sidebar. To create it, just edit the Blog page. Everything in that page will be shown in a margin column on the side. Read our FAQ on sidebars to learn more.

Please be aware that not all templates support sidebars.

Customize your Wiki

Once you're comfortable with creating and editing pages you might want to have a look at the configuration settings (be sure to login as superuser first).

You may also want to see what plugins and templates are available at DokuWiki.org to extend the functionality and looks of your DokuWiki installation.

Join the Community

DokuWiki is an Open Source project that thrives through user contributions. A good way to stay informed on what's going on and to get useful tips in using DokuWiki is subscribing to the newsletter.

The DokuWiki User Forum is an excellent way to get in contact with other DokuWiki users and is just one of the many ways to get support.

Of course we'd be more than happy to have you getting involved with DokuWiki.

owncloud

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:06:25+00:00

ownCloud

https://www.andunix.org/owncloud/index.php

online

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:06:10+00:00

andunix online

Here are some networks and communities were you can connect with me.

Chat

andunix@jabber.org

andunix.net

andunix (andunix@undisclosed.example.com) — 2020-08-29T21:05:50+00:00

andunix.net

Infos | Links | Projects

Recent Changes

Formatting Syntax	2020-08-29 21:08
DokuWiki	2020-08-29 21:08
Welcome to your new DokuWiki	2020-08-29 21:07
andunix.net	2020-08-29 21:05
Convert a Key	2019-01-17 20:19
Git	2018-12-06 11:07
Compare directories	2018-09-19 14:34

Convert a Key

andunix (andunix@undisclosed.example.com) — 2019-01-17T20:19:12+00:00

Convert a Key

Convert P12 to Java Keystore

keytool -importkeystore -srckeystore testkey.p12 -srcstoretype pkcs12 -srcalias 1 -destkeystore testkey.jks -deststoretype jks -destalias testkey

You can add -deststorepass PASSWORD to set the password on the command line. If you don't, keytool will ask you for a password.

Convert PEM to P12

To convert cert.pem and key.pem to key.p12:

openssl pkcs12 -export -in cert.pem -inkey key.pem -out key.p12

Export Certificate from P12

Export the certificate with the complete certificate chain:

openssl pkcs12 -in testkey.p12 -out testkey.pem -nokeys

Export the certificate only:

openssl pkcs12 -in testkey.p12 -out testkey.pem -nokeys -clcerts

openssl, security, cryptography, key, howto

Git

andunix (andunix@undisclosed.example.com) — 2018-12-06T11:07:22+00:00

Git

Basics

Init Repository

Standard:

git init [DIR]

Bare:

git init --bare [DIR]

Log

See commits between branches:

git log master..develop

Branches

List Branches

git branch

Switch Branch

git checkout BRANCH

Delete Branch

git branch -d BRANCH

Delete Remote Branch

git push origin -d BRANCH

List unmerges branches

List branches with commits, which are not in branch REF:

git branch --no-merged REF

For example, list unmerged branches, which are not in develop:

git branch --no-merged develop

List unmerges commits

List commits in branch BRANCH, which are not in branch REF:

git cherry -v REF BRANCH

For example, list commits in a feature branch, which are not in develop:

git cherry -v develop feature/FEATURE

Subversion

Update

git svn fetch

Git Flow

Init

git flow init

Feature

git flow feature start FEATURE
git flow feature finish FEATURE

Release

git flow release start RELEASE [BASE] 
git flow release finish RELEASE

Hotfix

git flow hotfix start VERSION [BASENAME]
git flow hotfix finish VERSION

Diff

If you only want the changes files between branches, you can user this:

git diff --name-status branchA..branchB

Compare directories

andunix (andunix@undisclosed.example.com) — 2018-09-19T14:34:39+00:00

Compare directories

For each of the directories, generate a digest file:

find DIR -type f -exec shasum {} + | LC_ALL=C sort -d -k 2 > shasums.txt

It's important to use LC_ALL=C and the option -d of sort, to get compareable results on different machines.

After that, you can diff the two shasums.txt:

diff shasums1.txt shasums2.txt

Or you use Meld as graphical diff tool:

meld shasums1.txt shasums2.txt

cli sysadmin

andunix.net

info:java:firefox_java-plugin

Install the Java-Plugin for Firefox

info:cryptography:plaintext

Plaintext

info:link:sidebar

andunix Infos

Tags

info:link:index

Link Lists

info:link:dokuwiki_plugins

DokuWiki Plugins

playground:playground

PlayGround

Formatting Syntax

Formatting Syntax

Basic Text Formatting

Links

External

Internal

Interwiki

Windows Shares

Image Links

Footnotes

Sectioning

Headline Level 3

Headline Level 4

Headline Level 5

Media Files

Supported Media Formats

Fallback Formats

Lists

Text Conversions

Text to Image Conversions

Text to HTML Conversions

Quoting

Tables

No Formatting

Code Blocks

Syntax Highlighting

Downloadable Code Blocks

Embedding HTML and PHP

RSS/ATOM Feed Aggregation

Control Macros

Syntax Plugins

DokuWiki

DokuWiki

Download

Read More

Copyright

Welcome to your new DokuWiki

Welcome to your new DokuWiki

Create your first pages

Customize your Wiki

Join the Community

owncloud

ownCloud

online

andunix online

Chat

andunix.net

andunix.net

Tags

Recent Changes

Convert a Key

Convert a Key

Convert P12 to Java Keystore

Convert PEM to P12

Export Certificate from P12

Git

Git

Basics

Init Repository

Log

Branches

List Branches

Switch Branch

Delete Branch

Delete Remote Branch

List unmerges branches