search for: nciaxp

Displaying 8 results from an estimated 8 matches for "nciaxp".

Did you mean: ncias
2002 Aug 28
0
patch almost works on 5.1A openssh 3.4p1 - get in, but get kicked out (fwd)
...; > > properly. > > > > > > > > > > > > ---------- previous message ---------- > > > > > > Date: Thu, 27 Jun 2002 11:29:42 -0400 (EDT) > > > > > > From: Toni L. Harbaugh-Blackford <harbaugh at nciaxp.ncifcrf.gov> > > > > > > To: secureshell at securityfocus.com > > > > > > Cc: Toni L. Harbaugh-Blackford <harbaugh at nciaxp.ncifcrf.gov> > > > > > > Subject: openssh 3.4p1 + Tru64 4.0G + SIA = "Account is disable...
2002 Aug 29
3
tru64 patch: openssh-SNAP-20020826.tar.gz does not contain 'configure', so how to build?
...eate a Makefile from the Makefile.in. Where are the directions for building a snapshot? The INSTALL file says to use the non-existant 'configure'. Thanks, Toni ----------------------------------------------------------------------- Toni Harbaugh-Blackford harbaugh at nciaxp.ncifcrf.gov AlphaServer 8400 System Administrator SAIC/NCI Frederick Advanced Biomedical Computing Center
2002 Sep 11
1
tru64 sia: move call of session_setup_sia() to do_setusercontext(), letting grantpty() and friends handle pty perms
...outside of SIA. Does anyone see any other problems with moving session_setup_sia() to do_setusercontext() when privsep is in use? Any comments on the list above? Toni ----------------------------------------------------------------------- Toni Harbaugh-Blackford harbaugh at nciaxp.ncifcrf.gov AlphaServer 8400 System Administrator SAIC/NCI Frederick Advanced Biomedical Computing Center
2002 Sep 04
2
uid transition and post-auth privsep (WAS Re: possible fundamental problem with tru64 patch) (fwd)
What do we loose by not having post-auth privsep? What code is executed between authorization and actual setting of the effective uid? On Tue, 3 Sep 2002, Chris Adams wrote: > Once upon a time, Toni L. Harbaugh-Blackford <harbaugh at nciaxp.ncifcrf.gov> said: > > It appears that the integration of the sia session setup will either > > have to be rethought or abandoned in order for privsep to work. > > That was the conclusion I came to a while back. I'd like to keep > pre-auth privsep (because th...
2001 Nov 08
0
openssh-3.0p1 + Tru64 4.0G: sia_ses_authent() always returns 0 (failure)
...someone know what the entity fields *should* look like after the call to sia_ses_init(), or have some other idea why the sia_ses_authent() call is failing? Thanks, Toni ----------------------------------------------------------------------- Toni Harbaugh-Blackford harbaugh at nciaxp.ncifcrf.gov AlphaServer 8400 System Administrator SAIC/NCI Frederick Advanced Biomedical Computing Center --------------------------------------------------------------------- To unsubscribe, e-mail: secureshell-unsubscribe at securityfocus.com For additional commands, e-mail: secureshell-help at...
2002 Aug 28
1
interested tru64 unix person - privsep patch against 3.4p1 + howto /regress
...have a problem it is likely related to the patch and not some unknown. Also, can someone point me to quick and dirty instructions for the /regress stuff? Thanks, Toni ----------------------------------------------------------------------- Toni Harbaugh-Blackford harbaugh at nciaxp.ncifcrf.gov AlphaServer 8400 System Administrator SAIC/NCI Frederick Advanced Biomedical Computing Center
2002 Aug 30
1
no, I see now, tru64 pty ownership wrong on entry to setup_sia, may need /usr/lbin/chgpt (WAS Re: Tru64 privsep patch testing)
Hi Toni, I'm sorry, I haven't had much time to work on this today. When I run sshd (from the patched snapshot) in a debugger, with a breakpoint early in setup_sia(), this is what I find after connecting with a client: (1) There are two sshd processes. One is running as root, and the other as the user I logged with using the client. The root process is the one in the debugger,
2002 Aug 28
5
Tru64 privsep patch testing
OK, I got a chance to try out the Tru64 patch for privsep. I applied the patch to 3.4p1. Partial success, in that it now works for me for logins to "root". Logins to ordinary accounts fail after authentication, when trying to set tty characteristics. See the excerpt from the debug messages below. This is for Tru64 V4.0F (with enhanced_security turned on, obviously.) I guess it's time