similar to: Problem 'ssh root@server' not working...

Hi I just noticed different sequences of PAM/ssh-session calls. (env: OpenSSH 3.8p1 on Linux with PAM-0.75) The channel 0 (server-session) seems to be startet very early for root and and after the pam-session is started for regular users. As a result, regular users don't have a tty when the pam-session modules are called. Is this intended? Frank For root: Apr 6 09:53:53 garfield2

I am having trouble with the rfImpute function in the randomForest package. Here is a sample... clunk.roughfix<-na.roughfix(clunk) > > clunk.impute<-rfImpute(CONVERT~.,data=clunk) ntree OOB 1 2 300: 26.80% 3.83% 85.37% ntree OOB 1 2 300: 18.56% 5.74% 51.22% Error in randomForest.default(xf, y, ntree = ntree, ..., do.trace = ntree, : NA not

Hi Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

Hi, I built OpenSSH 7.7p1-1 to try to include some security fixes for an old OS version (SLES 10). We use a special PAM module for root to allow us to provide auto-expiring passwords. There is, however, one root password that should always work. root can login just fine on the console, which I assume means that the PAM module is working correctly because I can use both the always should work

https://bugzilla.mindrot.org/show_bug.cgi?id=1592 Summary: Fingerprints for SSHD host key don't match (local ssh-keygen -l vs. ssh localhost) Product: Portable OpenSSH Version: 5.1p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd

> When you carry out tests to ensure that the setup is working well, you will pull the power cord from the wall and wait until the UPS reaches LB. This means waiting and wasting time. You can speed up the testing by setting LB very high so that the UPS reaches it quickly. Later you can set a more reasonable value. After the first test and the NAS is restarted I had to change the setting

Hello, I am using Redhat 6.1 on pentium. I have a problem with sshd in openssh, when I try to connect by ssh to sshd even on the local machine, the pam module will not authenticate my password. Here is a transcript of sshd -ddd: debug1: sshd version OpenSSH_2.3.0p1 debug1: Seeding random number generator debug1: read DSA private key done debug1: Seeding random number generator debug1: Bind to port

Hey. I found references to my problem 'scp: command not found' in the archives. But I could not find a solution to this problem. Could someone please help me out here? Info: OpenSSH 1.2.3, RedHat 6.1 Thanks! -- Steve

Is anyone in the leadership of the R-project going to contact the New York Times and clarify that the article gave remarkably short shrift to the people who designed the user interface for R, to a large extent AT&T researchers from an earlier generation? It would be the appropriate thing to do. The R team did not develop the user interface for R, the designers of the S programming language

I have a problem w/ OpenSSH allowing root logins even though the PermitRootLogin directive in the conf file is set to "no". I double and triple checked that it was using the file I was editing with strings and just by adding a bogus line and sshd complaining about it. I then grabbed the latest source and built 3.6p1. It has the same problem. The host is running solaris 2.6. Anyone have

Hello All: I am trying to authenticate against an Active Directory using winbind in my /etc/pam.d/sshd configuration (below). If the user is in the local password file, I can authenticate successfully using that user's Active Directory credentials. However, if the user is not in the local password file, I get the following errors. Nov 3 10:07:48 mailnat pam_winbind[29805]: request failed:

-----BEGIN PGP SIGNED MESSAGE----- ###### ## ## ###### ## ### ## ## ###### ## # ## ## ## ## ### ## ###### . ## ## . ######. Secure Networks Inc. Security Advisory

I'm wondering if anyone can help me? I'm trying to run Secret of Monkey Island special edition in Steam on wine with Ubuntu Maverick Meerkat. I can install steam and use it to install the game (after it installs directx), apparently with no problems, but when I try to run the game, a window opens saying "Preparing to launch The Secret of Monkey Island: Special Edition". This

I can suggest a few things. krb5.conf ( if you use nfsv4 with kerberized mounts _ [libdefaults] ignore_k5login = true in But, it does not look like it in you logs your useing kerberized mounts. Im missing in SSHD_config : UseDNS yes And the defaults : # GSSAPI options GSSAPIAuthentication yes GSSAPICleanupCredentials yes Are sufficient for a normal ssh kerberized login. Optional,

Team, We upgraded sshd in our product from OpenSSH 8.6 to OpenSSH 9,.6. After the upgrade, clients are seeing significant increase in time to do ssh to the listener. Normally, a single ssh does not matter much but some of our workflows involve about 3000 to 4000 ssh connect and close and this is hitting us hard, I enabled logging on the server side. I see the most of the increase is here in

http://bugzilla.mindrot.org/show_bug.cgi?id=1185 Summary: remote ssh command runs very slow on windows 2003 Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: Cygwin on NT/2k Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org

To whomsoever it may concern, I have compiled openssh-2.9p2 in LynxOS and it works fine. But there is one problem. The ssh client program hangs on exit. I run the sshd server in LynxOS and connect from a ssh client in Linux system. This is the debug output that I get: < sshd running in LynxOS on i386 machine> # ./sshd -d debug1: Seeding random number generator debug1: sshd version

Hi, thanks for your hints. DNS, /etc/resolf.conf, /ets/hosts seem to be correct. I'm able to do a kerberized ssh with a user from subdom2.subdom1.example.de (testuser at SUBDOM2.SUBDOM1.EXAMPLE.DE) But I'm not able to do the same with a user from example.de (user1 at EXAMPLE.DE). -- Regards, Andreas Am 01.11.2017 um 10:51 schrieb L.P.H. van Belle via samba: > I can suggest a few

Below is a patch against the current OpenBSD OpenSSH CVS to workaround a behavior I have observed when converting from SSH 1.2.27 to OpenSSH while using the same old RSA1 host key for protocol 1. In several cases I saw that old SSH sshd reported a host key size of 1024 bits when OpenSSH saw it as 1023 bits. Without the patch, when OpenSSH's ssh client connects to an old SSH sshd it warns

On 02/13/2015 05:41 AM, James Hogarth wrote: > This is horrible advice anyway. It's not a good idea to run SSH on a port > greater than 1024 since if a crash exploit is used to kill the process a > non-root trojan process faking SSH to gather credentials could then bind on > that port trivially totally compromising the system. This is where an SELinux policy on your server can