similar to: [PATCH] customize: password: use SHA-512 on openSUSE >= 11.0

They are rolling distributions, so we can assume they have a glibc version greater than 2.7 (cca Oct 2007). --- customize/password.ml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/customize/password.ml b/customize/password.ml index 94b2f27..8a9fed3 100644 --- a/customize/password.ml +++ b/customize/password.ml @@ -165,6 +165,9 @@ and default_crypto g root = |

On Fri, Jul 24, 2015 at 03:26:45PM +0200, Pino Toscano wrote: > When warning that there is no known default password encryption for the > current guest, print its version in MAJOR.MINOR format if MAJOR is zero. > > Also, fix wrapping (and indentation) of the message. > --- > customize/password.ml | 11 +++++++++-- > 1 file changed, 9 insertions(+), 2 deletions(-) > >

--- customize/password.ml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/customize/password.ml b/customize/password.ml index 258d726..1f9b8fe 100644 --- a/customize/password.ml +++ b/customize/password.ml @@ -165,6 +165,9 @@ and default_crypto g root = | "opensuse", v when v >= 11 -> `SHA512 | "opensuse", _ -> `MD5 + | "sles", v when v >=

CirrOS has its random-seed file in /etc. --- customize/random_seed.ml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/customize/random_seed.ml b/customize/random_seed.ml index 34a7af7..5a15ad9 100644 --- a/customize/random_seed.ml +++ b/customize/random_seed.ml @@ -30,6 +30,7 @@ let rec set_random_seed (g : Guestfs.guestfs) root = "/var/lib/systemd/random-seed"; (* Fedora

Read the information from os-release, and make it behave like a Debian distribution (i.e. using dpkg, and apt). --- daemon/inspect_fs.ml | 2 ++ daemon/inspect_fs_unix.ml | 1 + daemon/inspect_types.ml | 2 ++ daemon/inspect_types.mli | 1 + generator/actions_inspection.ml | 4 ++++ 5 files changed, 10 insertions(+) diff --git a/daemon/inspect_fs.ml

When warning that there is no known default password encryption for the current guest, print its version in MAJOR.MINOR format if MAJOR is zero. Also, fix wrapping (and indentation) of the message. --- customize/password.ml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/customize/password.ml b/customize/password.ml index 111240e..7a050d6 100644 ---

Kali Linux is a Debian derivative, so add basic support for it by using most of the Debian code paths. The only exception is the crypto algorithm for passwords in passwd, which is always assumed as SHA512 (as Kali Linux is relatively new). --- customize/firstboot.ml | 2 +- customize/hostname.ml | 2 +- customize/password.ml | 2 +-

Having SELinux enabled (even if not enforcing) in the appliance causes troubles to applications/libraries that read/write SELinux attributes. --- builder/builder.ml | 6 +++++- customize/customize_main.ml | 6 +++++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/builder/builder.ml b/builder/builder.ml index a407924..5195cfd 100644 --- a/builder/builder.ml +++

Dear all, I send you a new email to know what is the progress of SCRAM-SHA-***(-PLUS) supports? Currently there is only SCRAM-SHA-1: https://doc.dovecot.org/configuration_manual/authentication/password_schemes/. - RFC6331: Moving DIGEST-MD5 to Historic: https://tools.ietf.org/html/rfc6331 - RFC5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms:

Hi guys, Here are two patches to get opensuse images in virt-builder. Cédric Bosdonnat (2): Allow curl to follow redirects. builder: add opensuse images sources builder/Makefile.am | 3 ++- builder/downloader.ml | 4 ++-- builder/opensuse.conf.in | 3 +++ builder/opensuse.gpg | 21 +++++++++++++++++++++ configure.ac | 1 + 5 files changed, 29 insertions(+), 3

> You could configure default scheme as CRYPT. It covers these all. Otherwise > you need to make sure passwords have {SCHEME} prefix when it differs from > default or oddities occur. --- Thank you for the tip with CRYPT. Is there any explanation for this behaviour though? Why are BCRYPT hashes accepted when default_pass_scheme is set to SHA512-CRYPT and not vice versa? Is this

Hi Cédric, On Tuesday 08 September 2015 09:40:21 Cédric Bosdonnat wrote: > Here are two patches to get opensuse images in virt-builder. > > Cédric Bosdonnat (2): > Allow curl to follow redirects. > builder: add opensuse images sources > > builder/Makefile.am | 3 ++- > builder/downloader.ml | 4 ++-- > builder/opensuse.conf.in | 3 +++ >

Greetings, this is less of a bug report or a help request, but we would like to know if someone can explain the following: Environment: Centos 7 with Dovecot 2.3.4-2 default_pass_scheme = BLF-CRYPT password hash in database : BLF-CRYPT login = works default_pass_scheme = SHA512 or SHA256-CRYPT password hash in database : BLF-CRYPT login = also works default_pass_scheme = BLF-CRYPT password

Hello Stephan, Thanks for the link about SCRAM-SHA-256, good news for this point, hope a merge soon :) I am from this page: https://wiki.dovecot.org/Authentication/PasswordSchemes ^^ The -PLUS variant for all SCRAM is not possible too for have (with other SCRAM): SCRAM-SHA-1(-PLUS), SCRAM-SHA-224(-PLUS), SCRAM-SHA-256(-PLUS), SCRAM-SHA-384(-PLUS), SCRAM-SHA-512(-PLUS) Some softwares use

Hello all, I would like to know if it is possible to add SCRAM-SHA-256 and SCRAM-SHA-512 supports? RFC7677: SCRAM-SHA-256 and SCRAM-SHA-256-PLUS: Simple Authentication and Security Layer (SASL) Mechanisms https://tools.ietf.org/html/rfc7677 Thanks in advance. Regards, Neustradamus -------------- next part -------------- An HTML attachment was scrubbed... URL:

Op 20/01/2019 om 00:45 schreef - Neustradamus -: > Hello all, > > I would like to know if it is possible to add SCRAM-SHA-256 and > SCRAM-SHA-512 supports? > > RFC7677: SCRAM-SHA-256 and SCRAM-SHA-256-PLUS: Simple Authentication > and Security Layer (SASL) Mechanisms > https://tools.ietf.org/html/rfc7677 > > Thanks in advance.

When saving a configuration file, Augeas creates a new file and replaces the old one with it; this creates a /etc/shadow file without the SELinux xattrs, since they are missing. Thus, create a temporary file with all the attributes of /etc/shadow, so all the attributes of it (permissions and xattrs, among others) can be restored properly on the new /etc/shadow. As side effect, if a guest is

The cryptic subject is the outcome of my looking into how to do a particular thing. I wonder if anyone else has solved this problem in a way that hasn't occurred to me. I'm using dovecot 1.1.11 on Ubuntu Server 9.10. I could consider upgrading to my own install of a newer dovecot if it made a difference to this problem. I have two populations of dovecot users. Some users have Unix

'distro' isn't used anywhere for Windows guests. However, if it's set, it's required to be matched in virt-v2v.conf. Rather than have to update the config again, just don't set it for Windows guests. --- lib/Sys/VirtConvert/Converter.pm | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/lib/Sys/VirtConvert/Converter.pm

Hi Richard I've noticed this snippet in import-to-ovirt.pl my $minor_version = $g->inspect_get_major_version ($root); I guess you meant here my $minor_version = $g->inspect_get_minor_version ($root); Emmanuel