Displaying 20 results from an estimated 30000 matches similar to: "[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail"
2002 Jul 14
3
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
------- Additional Comments From jrj at purdue.edu 2002-07-14 13:31 -------
Created an attachment (id=131)
Update of bug #2 patch to 3.4p1
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2004 May 31
1
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #619 is|0 |1
obsolete| |
------- Additional Comments From dtucker at zip.com.au 2004-05-31 23:25 -------
2004 Mar 03
2
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
jrj at purdue.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #500 is|0 |1
obsolete| |
------- Additional Comments From jrj at purdue.edu 2004-03-04 10:33 -------
Created an
2002 Nov 15
0
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
------- Additional Comments From Brian.King at xwave.com 2002-11-16 07:20 -------
One of the suggested work-a-rounds was to set "UseLogin yes" in sshd_config.
This does not work 100% of the time. SSH clients used in non-interactive modes
still exhibit the problem.
e.g.:
ssh {hostname} "crontab -l >crontmp ; crontab
2003 Jan 03
1
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
------- Additional Comments From jrj at purdue.edu 2003-01-04 06:29 -------
The following attachment updates the suggested patch to 3.5p1.
The attachment is a gzip'd tar file. Once you download it, ungzip it and then
untar it into a temp directory (or use the 'z' option of GNU tar). Then look at
the README for more information.
2003 Jul 09
1
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
------- Additional Comments From jrj at purdue.edu 2003-07-10 08:23 -------
Created an attachment (id=355)
--> (http://bugzilla.mindrot.org/attachment.cgi?id=355&action=view)
Gzip'd tar file with 3.6p1 (and later) patch
This version of the patch applies against 3.6p1 (and later).
In addition to being an update to a new release,
2003 Nov 15
0
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
jrj at purdue.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #438 is|0 |1
obsolete| |
------- Additional Comments From jrj at purdue.edu 2003-11-15 16:00 -------
Created an
2003 Sep 19
3
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
jrj at purdue.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #192 is|0 |1
obsolete| |
Attachment #355 is|0 |1
obsolete|
2004 Apr 14
8
[Bug 125] with BSM auditing, cron editing thru ssh session causes cron jobs to fail
http://bugzilla.mindrot.org/show_bug.cgi?id=125
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |enhancement
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2003 Mar 12
1
Problems with ! -p
Hi there,
rsync version 2.5.5 protocol version 26.
I seem to be having some trouble using rsync to ignore permissions on a
remote host when syncing back to a local host. I want it to listen to
the umask of the user running the rsync locally. Eg:
[remote host - I've touched a file made it 4750, etc, etc]
hostb $ mkdir -p /data/rsync/temp
hostb $ touch /data/rsync/temp/foo
hostb $ chgrp
2004 Dec 20
6
[Bug 125] add BSM audit support
http://bugzilla.mindrot.org/show_bug.cgi?id=125
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #647 is|0 |1
obsolete| |
------- Additional Comments From dtucker at zip.com.au 2004-12-20 16:24 -------
2005 Mar 03
2
Question/concern about bsm auditing option on solaris
Hello,
I downloaded and compiled the Mar 2, 2005 snapshot and compiled it with
bsm auditing for solaris turned on. I've been noticing about a dozen or
so of the following messages per day now. Not sure exactly what it is, or
if it is a big issue.
Mar 3 13:46:10 machine_name sshd[15298]: [ID 800047 auth.crit] fatal: mm_request_send: write
If it matters it is running on solaris 8
2004 Aug 17
0
[Bug 125] add BSM audit support
http://bugzilla.mindrot.org/show_bug.cgi?id=125
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO|822 |914
nThis| |
------- Additional Comments From dtucker at zip.com.au 2004-08-17 18:58 -------
2005 Feb 25
7
[Bug 125] add BSM audit support
http://bugzilla.mindrot.org/show_bug.cgi?id=125
------- Additional Comments From phil at usc.edu 2005-02-25 13:09 -------
So we've done some internal testing with the latest snapshot over the last two
days, and things look good. It's not a thorough test, but the logging is as we
would expect, and everything else looks as expected.
A huge thanks to all the people who helped with
2005 Jan 24
15
[Bug 125] add BSM audit support
http://bugzilla.mindrot.org/show_bug.cgi?id=125
alex.bell at bt.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex.bell at bt.com
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the
2002 Oct 17
1
OpenSSH 3.5p1, Solaris 8, BSM, cron issue
We have started using BSM and have hit the BSM issue where cron is messed up if you SSH into a Solaris 8 box and try to issue a cron job.
I noticed the bug here:
http://bugzilla.mindrot.org/show_bug.cgi?id=125
Is this patch applied to the OpenSSH 3.5p1 release?
I tried installing OpenSSH 3.5p1 and turned off Privileged Separation in the sshd_config file, but I am still getting the cron issues
2002 Apr 11
3
[Bug 2] sshd should have BSM auditing on Solaris
http://bugzilla.mindrot.org/show_bug.cgi?id=2
Michael.Gerdts at alcatel.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Michael.Gerdts at alcatel.com
------- You are receiving this mail because: -------
You are the assignee for the bug, or are
2003 Jan 24
0
[Bug 2] sshd should have BSM auditing on Solaris
http://bugzilla.mindrot.org/show_bug.cgi?id=2
Michael.Gerdts at med.ge.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|Michael.Gerdts at alcatel.com |Michael.Gerdts at med.ge.com
------- You are receiving this mail because: -------
You are the assignee for the bug, or are
2003 Jan 03
1
OpenSSH, Solaris 8, and BSM works with BSM patch, but must disable privilege separation
To get BSM working on Solaris 8 with OpenSSH, I did this:
Download John R. Jackson's OpenSSH 3.5p1 BSM patch here, and save as "patch.tar.gz":
http://bugzilla.mindrot.org/show_bug.cgi?id=125
(NOTE TO OpenSSH DEVELOPERS, can you incorporate this patch into the next version of OpenSSH?)
Installing the OpenSSH 3.5p1 BSM patch:
?--------------------------------------
Turning on Sun BSM
2002 Jul 19
0
[Bug 363] No logging of SSH activities under Solaris BSM
http://bugzilla.mindrot.org/show_bug.cgi?id=363
mouring at eviladmin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From mouring at eviladmin.org