Where is readme.debian

If you maintain a package whose upstream developers use GitHub, please feel free to join this group and mirror such project here. Most often such repositories should be made available on the Debian project's public forge Salsa to guarantee autonomy. You might find following tools available from Debian useful for your interaction with GitHub.

Many thanks to the GitHub admins for their prompt action to release the previous unused "Debian" account. Debian does not maintain or distribute the GitHub engine codebase because it is not available under free and open-source license see Wikipedia for a list of available free and open-source alternatives. Moreover, this GitHub organization is not an official part of the Debian project. It is maintained by individual Debian developers signed below with the sole purpose of being useful.

Skip to content. See man luksformat 8 for more information. If you wish to perform a Debian installation to an encrypted root, you might be interested in using a version of Debian Installer with partman-crypto, which will install the system and setup cryptsetup and initramfs-tools.

Encrypted swap partition s An encrypted swap partition prevents spying on plaintext secrets passwords that may be written to disk when memory is swapped to disk. With initramfs-tools 0. You have a crypted swap device.

Moving mouse and keyboard typing might help in this case. Read the crypttab 5 manpage for more information, for example options to use a different encryption algorithm than the default. If a key is stored on a vfat filesystem very common for removable media , chmod and chown will not work. The vfat filesystem and several others too does not support file permissions and ownership. Cryptsetup and udev As a workaround for some yet-to-be-fixed race condition in kernel, device-mapper or udev, cryptsetup currently runs udevsettle.

This leads to problems if you invoke cryptsetup as part of a udev rule. Due to cryptsetup itself being a "run program" in this case, this ends in a deadlock. Therefore cryptsetup should be detached directly after invocation in this case, so that it runs asynchronously. Useful keyscripts: askpass and passdev The cryptsetup package ships with several keyscripts.

Two special keyscripts, worth being mentioned here, are askpass and passdev. It's a simple helper program that supports different methods console, fifo, splashy, Please send us your checks, if you write new ones.

Depending on your configuration, completing the upgrade from 2. The package upgrade process first exports your databases to LDIF format using slapcat 8 , then updates the slapd package, and finally imports the LDIF files using slapadd 8. If the slapadd process fails, it must be completed manually after resolving whatever issues caused the failure. If you use a slapd. See below for suggestions for some specific issues. If the slapadd command failed, go back to step 2.

After the slapadd command succeeds, change the permissions on the slapd. For each configured database: 1. These were configured by default in older versions of the slapd package.

Edit the exported configuration LDIF as described above, and make the following changes: 1. If you have an olcBackend: bdb or hdb entry, change it to mdb, or delete it if you don't have to override any global LMDB settings. Also update structuralObjectClass.

If not configured, the default is 10 MiB. The external schema is no longer used, and conflicts with the internal copy.

If you have the ppolicy schema loaded, slapadd fails with the following message: olcAttributeTypes: value 0 olcAttributeTypes: Duplicate attributeType: "1.

Remove the entire ppolicy schema entry. Change olcModuleLoad: pw-argon2 to argon2.