search for: 491a

Howdy folks, The chroot patch in the contrib directory had gotten stale and didn't apply cleanly, so I've updated it... The attached patch works fine with 3.0p1. Is there any reason this patch stays in the contrib directory rather than being applied to the source? I find it incredibly useful. Thanks for your hard work on OpenSSH! Bret PS: Please cc me with any responses as I'm

...ects/ The porting effort included moving all auth code to the new privilege separation model. Enjoy. -- Theo Schlossnagle Principal Consultant OmniTI Computer Consulting, Inc. -- http://www.omniti.com/ Phone: +1 301 776 6376 Fax: +1 410 880 4879 1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984 2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7

Hi! the script ssh-copy-id assumes, that the remote machine has a POSIX Compatible shell as login shell. So you have to write in line 41: ? ssh $1 'sh -c "umask 077; test ? instead of ? ssh $1 "umask 077; test ? Patch is appended. Greetings, Benjamin Kellermann -- GPG-Key-ID: 491A3D9C Fingerprint: D19E 04A8 8895 020A 8DF6 0092 3501 1A32 491A 3D9C http://pgpkeys.pca.dfn.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: ssh-copy-id.patch Type: text/x-patch Size: 246 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openss...

I have a few questions: 1) Is OpenSSH 2.9p2 (or any other version of OpenSSH) vulnerable to the same problem as SSH3.0.0? (described here: http://www.kb.cert.org/vuls/id/737451 ) 2) There is a "SECURID" patch in the contrib section since 2.5.2p2. I am using it, but applying this patch to each new version is growing more difficult as time goes on. Would you consider merging this

Hello, I have 2 boxes with 1.5TB storage with ext3 fs, and the kernel is 2.6.11.8. I'm using E2fsprogs 1.37 for FS creation. And, Filesystem revision #: 1 (dynamic) There are 2 scenarios: 1. All SATA drives, RAID5 2. All PATA drives, RAID5 and wrapped in log volumes. I'm having lots of issues with fsck. I did search, but somehow not getting the right information. needs_recovery

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on 64eb5e3b-b25d-4fe7-b344-71ce6561195f. sources=0 [2] sinks=1 [2017-10-25 10:40:32.919372] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on d80f8a62-6a4b-491a-837a-ff3d9906db7d. sources=0 [2] sinks=1 [2017-10-25 10:40:32.920903] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on d80f8a62-6a4b-491a-837a-ff3d9906db7d [2017-10-25 10:40:32.926055] I [MSGID: 108026] [afr-self-heal-c...