similar to: [Bug 1904] New: sshd refuses certificate-based authentication if password has expired

https://bugzilla.mindrot.org/show_bug.cgi?id=1904 mathew <meta at pobox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #5 from mathew <meta at pobox.com> --- %

https://bugzilla.mindrot.org/show_bug.cgi?id=1904 --- Comment #6 from Damien Miller <djm at mindrot.org> --- Ok, so back in 2011 I pointed out that the pam_unix in your account stack is likely the problem. Did you check this before reopening the bug? -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=1904 Tomas Mraz <t8m at centrum.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t8m at centrum.cz --- Comment #7 from Tomas Mraz <t8m at centrum.cz> --- Actually pam_unix from Linux-PAM 1.3.0

https://bugzilla.mindrot.org/show_bug.cgi?id=1904 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Damien Miller <djm at

https://bugzilla.mindrot.org/show_bug.cgi?id=1904 mathew <meta at pobox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #8 from mathew <meta at pobox.com> ---

The reason I ask about the patches is because I think the problem you're seeing might actually be a bug in pam_unix.so.1 - it's something to try at least. We don't use password aging and we don't use the "passwd" command to change passwords, so we haven't run into this at our site even though we probably don't have pam_unix.so patched up. Also, the passwd

As background, I read: http://therowes.net/~greg/2011/03/23/ssh-trusted-ca-key/ http://www.ibm.com/developerworks/aix/library/au-sshsecurity/ http://bryanhinton.com/blog/openssh-security http://www.linuxhowtos.org/manpages/5/sshd_config.htm

https://bugzilla.mindrot.org/show_bug.cgi?id=2404 Bug ID: 2404 Summary: scp skips file/directory on permissions error Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: scp Assignee: unassigned-bugs at mindrot.org

Dear all, I'm rather new to glusterfs but have some experience running lager lustre and beegfs installations. These filesystems provide active/active failover. Now, I discovered that I can also do this in glusterfs, although I didn't find detailed documentation about it. (I'm using glusterfs 3.10.8) So my question is: can I really use glusterfs to do failover in the way described

Hi Stefan, I think what you propose will work, though you should test it thoroughly. I think more generally, "the GlusterFS way" would be to use 2-way replication instead of a distributed volume; then you can lose one of your servers without outage. And re-synchronize when it comes back up. Chances are if you weren't using the SAN volumes; you could have purchased two servers

On 8 June 2018 at 11:21, PGNet Dev <pgnet.dev at gmail.com> wrote: > fyi > > add'l -- and looks unrelated -- issue > /usr/include/pthread.h:251:12: note: previous declaration of ?pthread_join? was here > extern int pthread_join (pthread_t __th, void **__thread_return); What included pthread.h? That's explicitly not supported by sshd: $ grep THREAD

Hi Alex, Thank you for the quick reply! Yes, I'm aware that using ?plain? hardware with replication is more what GlusterFS is for. I cannot talk about prices where in detail, but for me, it evens more or less out. Moreover, I have more SAN that I'd rather re-use (because of Lustre) than buy new hardware. I'll test more to understand what precisely "replace-brick"

Back again with another oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k

:) Rgds/DP 9849111010 Sent from my iPhone. Pls excuse brevity and typos if any. > On 15-Jul-2018, at 5:00 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > certbot clearly hates me > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "B. Reino" <reinob at bbmk.org> > Date: 15/07/2018 11:49 (GMT+02:00) >

https://bugzilla.mindrot.org/show_bug.cgi?id=3576 Bug ID: 3576 Summary: The sftp-server does not provide the feature of changing expired passwords, which is provided by the sshd. Product: Portable OpenSSH Version: -current Hardware: All OS: Linux Status: NEW

Yes. Sorry about this.Sent from my Samsung Galaxy smartphone. -------- Original message --------From: Masaki Nemoto <itml at ma3ki.net> Date: 11/11/2018 10:00 (GMT+02:00) To: dovecot at dovecot.org Subject: The SSL certificate of repo.dovecot.org has expired. HiThe SSL certificate of https://repo.dovecot.org has expired.Do you have plans to update it? -------------- next part

https://bugzilla.netfilter.org/show_bug.cgi?id=1133 Bug ID: 1133 Summary: Expired host certificate Product: bugzilla Version: other Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: netfilter bugzilla Assignee: netfilter-buglog at lists.netfilter.org

I'll look into it. Something has failed. ---Aki TuomiDovecot oy -------- Original message --------From: Marc Weustink <m.weustink at cuperus.nl> Date: 13/02/2018 17:44 (GMT+02:00) To: dovecot at dovecot.org Subject: Certificate of package repository expired Hi, I just happened to do an apt update and got a notice that repo.dovecot.org was disabled. According to firefox:

FYI, it happened again :) On July 15, 2018 10:49:08 AM GMT+02:00, "B. Reino" <reinob at bbmk.org> wrote: >Dear Aki, > >I think the renewal failed again. The SSL certificate expired Saturday, > >14 July 2018. > >This affects (at least) the repo.dovecot.org website and debian >repository. > >Thanks, >Bernardo. > >On 2018-05-15 08:15, Aki Tuomi

Dear Aki, I think the renewal failed again. The SSL certificate expired Saturday, 14 July 2018. This affects (at least) the repo.dovecot.org website and debian repository. Thanks, Bernardo. On 2018-05-15 08:15, Aki Tuomi wrote: > On 15.05.2018 09:14, B. Reino wrote: >> Dear all, >> >> Just in case you've missed it, the certificate for repo.dovecot.org >> just