similar to: [Bug 224] configure.ac changes for crays

Displaying 20 results from an estimated 100 matches similar to: "[Bug 224] configure.ac changes for crays"

2002 Apr 22
0
[Bug 224] New: configure.ac changes for crays
http://bugzilla.mindrot.org/show_bug.cgi?id=224 Summary: configure.ac changes for crays Product: Portable OpenSSH Version: 3.1p1 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: wendyp
2001 Jun 21
0
Output of last command is strange on Solaris 2.6/8 (OpenSSH 2.9p2)
Hi. OS: Solaris 2.6 and 8 OpenSSH: 2.9p2 I found a bug. Output of last command becomes strange in case of "UseLogin yes" in sshd_config. # Two entries are output with one time of login. strange case: % last fuga pts/3 bar.foo.co.jp Thu Jun 21 12:45 - 20:02 (07:16) fuga pts/3 bar.foo.co.jp Thu Jan 1 09:00 - 12:45 (11494+03:45) hoge pts/2
2002 Dec 29
0
[Bug 460] New: ut_addr_v6 not used
http://bugzilla.mindrot.org/show_bug.cgi?id=460 Summary: ut_addr_v6 not used Product: Portable OpenSSH Version: 3.5p1 Platform: All URL: http://bugs.debian.org/167867 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at
2001 Apr 29
2
PATCH: UseLogin fix for 2.9p1 (w/improved last-login time)
Attached is the latest version of my UseLogin patch that makes "UseLogin true" work on Solaris and UNICOS. As usual, I have provided configure.in changes that set the appropriate defines for Solaris, but I have not provided the configure.in changes for UNICOS (since they would be incomplete, and Wendy is working on this). This version fixes a problem with the last-login time always
2001 Aug 02
3
Cray patch against openssh-SNAP-20010802
Significant changes since last patch. Deleted patches to packet.c and channel.c - not needed. Add small patch to sshd.c and openbsd/ssh-cray.c to disable cray process privileges. Depending on how a cray unicos/unicosmk system is configured user could su to root without a password with out this mod. Add no_sco flag to noop check for -lrpc which assumes that their was a -lyp library.
2024 Oct 14
1
openssh 9.9p1
The following alteration needs to be made to loginrec.c in the routine record_failed_login() #ifdef USE_UTMP ??????? construct_utmp(&li, &ut); #endif It was missing "#ifdef USE_UTMP" which causes an problem if you are not using UTMP. gt
2002 Jul 22
0
[Bug 224] configure.ac changes for crays
http://bugzilla.mindrot.org/show_bug.cgi?id=224 wendyp at cray.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From wendyp at cray.com 2002-07-23 08:42
2001 Jun 06
1
One more UseLogin tweak
One other thing I noticed in the record_utmp_only() function is that it wasn't setting the timestamp in the logininfo structure. The following patch takes care of this: --- old/loginrec.c Wed Jun 6 11:12:14 2001 +++ loginrec.c Wed Jun 6 11:13:42 2001 @@ -448,6 +448,8 @@ login_utmp_only(struct logininfo *li) { li->type = LTYPE_LOGIN; + /* set the timestamp */ +
2008 Apr 01
1
strange permission denied problem
I built an embedded box which uses mount.cifs to mount network shares. I've shipped several of these and all are working fine except for one, which gives me permission denied on certain files: root@Mnemosyne:~/mnt/bgrp1/c/Ballance Group Folders/Scully/Client Photos-Scully# cat "Office Pics 002.jpg" > /dev/null cat: Office Pics 002.jpg: Permission denied
2001 Oct 08
2
Porting OpenSSH 2.9.9p2 to Dynix V4.4.4
Hello Porters, I am attempting to compile OpenSSH 2.9.9p2 on a Dynix V4.4.4 host. I have set USE_PIPES and BROKEN_SAVED_UIDS (the latter because there are no functions for set{eu,eg}id() that I can find). I configured with "./configure '--with-libs=-lnsl -lsec'". Each time I attempt to login, I get this error: No utmp entry. You must exec "login" from
2004 Jul 08
1
openssh 3.8.1p1 problem on SCO 5.0.7
On SCO 5.0.7 and openssh 3.8.1p1, two entries are written to /etc/wtmp and /etc/wtmpx each time a user logs in via ssh. This can be demonstrated using the last(C) command. Any user connected via ssh will have two identical login and logout entries. On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined). wtmp_write_entry()
2001 Aug 21
0
Resend: loginrec.c patch
I'm resending this patch just in case it got lost. The first hunk of the patch fixes a problem with the LOGIN_NEEDS_UTMPX support in that the date was not being set in the logininfo structure (causing wrong timestamps in the "last" log). The second hunk just omits the USE_WTMPX code in the LOGIN_NEEDS_UTMPX section if USE_UTMPX is defined. This prevents duplicate events in the
2007 Jan 17
0
login_get_lastlog - nss enviornment - works in shell env, doesn't work when sshd calls it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello to every one! Maybe this is not exactly the right place, but I don't know where to ask, so... I have a FreeBSD-6-STABLE machine, setuped with custom nss lib which reads from pgsql database. It seems to be working just fine except that I can't login trought ssh, when trying the normal method. When I do $>ssh host.com tcsh I get
2008 Sep 11
1
Trouble finding all smb shares on network
Hi, just joined the list and know very little about smb. I'm trying to do something that should be simple, but my current solution isn't working 100% All I need is a list of smb shares on the network. I'm doing this: /usr/bin/nmblookup -M -- - and then use this on each ip returned: /usr/bin/smbclient -g -p 139 -NL <ip addr> That works for most cases but it fails to find
2001 Jul 26
7
Updated Cray patch against openssh SNAP-20010725
This patch fixes my botched attempted to patch deattack.c. I created a bsd-cray.h file and cleaned up a few error cases in bsd-cray.c. Fixed cray_setup call to pass uid and login name in session.c and moved its call so that its called with root privs. Its been tested on a irix, sun, aix, unicos(SV1) and unicosmk(T3E) systems. If you are building this on a T3E you may have to edit the Makefile
2000 Jun 12
1
AIX and 2.1.1p1
The new login code works fine with AIX 4.3. Two nits, though. If --disable-lastlog is defined, the code still tries to slog through wtmp to determine the last login time. Is this a bug or a feature? If a feature, change the DISABLE_LASTLOG test below to WITH_AIXAUTHENTICATE. Also, a small typo in configure.in, plus an AIX tweak. --- configure.in.orig Thu Jun 8 21:58:35 2000 +++ configure.in Mon
2017 Feb 28
2
Dict protocol changes string
On 09/23/2016 08:05 AM, Aki Tuomi wrote: > On 29.07.2016 15:35, Nagy, Attila wrote: >> I use pass and userdb with dict protocol in a similar way: >> >> key passdb { >> key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: >> %s^MClient-IP: %r >> format = json >> } >> >> (^M is an \r character, inserted with vi CTRL-v + enter)
2017 Mar 13
0
Dict protocol changes string
On 28.02.2017 17:59, Nagy, Attila wrote: > On 09/23/2016 08:05 AM, Aki Tuomi wrote: >> On 29.07.2016 15:35, Nagy, Attila wrote: >>> I use pass and userdb with dict protocol in a similar way: >>> >>> key passdb { >>> key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: >>> %s^MClient-IP: %r >>> format = json >>> }
2016 Jul 29
2
Dict protocol changes string
Hi, I use pass and userdb with dict protocol in a similar way: key passdb { key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: %s^MClient-IP: %r format = json } (^M is an \r character, inserted with vi CTRL-v + enter) Until 2.2.24 this has worked, but 2.2.25 seems to convert that ASCII 13 into an ASCII 1 and an "r". Python printout from what I get with 2.2.25:
2004 Apr 28
1
Autoreply: Protected message
This mailbox is unmonitored. Mail sent to this address is not received or read. I am unable to offer support for general technical issues via private e-mail. I only provide support via the newsgroups, so that others may benefit from the solution to a given problem. In addition, many others will see your post, and may have an answer that I do not. If your message was a follow up to a post I