similar to: Q: patch for logging rsa-fingerprint on login/logout?

Displaying 20 results from an estimated 5000 matches similar to: "Q: patch for logging rsa-fingerprint on login/logout?"

2015 May 08
1
Q: respecting .ssh/id_rsa
--On Friday, May 08, 2015 09:58:32 AM -0400 "James B. Byrne" <byrnejb at harte-lyne.ca> wrote: > While attempting to debug something else I ran across this: > > ssh -vvv somehost > . . . > debug1: Connection established. > debug1: permanently_set_uid: 0/0 > debug1: identity file /root/.ssh/identity type -1 > debug1: identity file /root/.ssh/identity-cert
2015 May 08
0
Q: respecting .ssh/id_rsa
Devin Reade wrote: > --On Friday, May 08, 2015 09:58:32 AM -0400 "James B. Byrne" > <byrnejb at harte-lyne.ca> wrote: > >> While attempting to debug something else I ran across this: >> >> ssh -vvv somehost >> . . . >> debug1: Connection established. >> debug1: permanently_set_uid: 0/0 >> debug1: identity file /root/.ssh/identity
2015 May 09
0
Q: respecting .ssh/id_rsa
On Fri, May 8, 2015 13:23, m.roth at 5-cent.us wrote: > Devin Reade wrote: >> --On Friday, May 08, 2015 09:58:32 AM -0400 "James B. Byrne" >> <byrnejb at harte-lyne.ca> wrote: >> >>> While attempting to debug something else I ran across this: >>> >>> ssh -vvv somehost >>> . . . >>> debug1: Connection established.
2009 Feb 02
2
did_not_yield
Hello, I have some rudimentary code for loging into my app and database, it works ok (I think) but in Production, it does some strange things. I''ve reduce the problem to a more simplest approach, without rendering, simply creating a variable of what should do. Here is what I get in the log: Processing ScannsController#status (for 127.0.0.1 at 2009-02-02 14:24:25) [GET] Session ID:
2011 Jan 05
1
Prediction error for Ordinary Kriging
Hi ALL, Can you please help me on how to determine the prediction error for ordinary kriging?Below are all the commands i used to generate the OK plot: rsa2 <- readShapeSpatial("residentialsa", CRS("+proj=tmerc +lat_0=39.66666666666666 +lon_0=-8.131906111111112 +k=1 +x_0=0 +y_0=0 +ellps=intl +units=m +no_defs")) x2 <- readShapeSpatial("ptna2",
2004 Mar 03
8
[Bug 806] openssh after 3.6.1p1 can not authenticate via public rsa2 key
http://bugzilla.mindrot.org/show_bug.cgi?id=806 Summary: openssh after 3.6.1p1 can not authenticate via public rsa2 key Product: Portable OpenSSH Version: 3.8p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: openssh-bugs at
2006 Apr 04
1
integration tests - 1.1
I?m using the new 1.1 integration test facility? I?m trying to write a test that sees if a controller redirects to the correct place and preserves the query string. Here?s the code: class LoginRedirectTest < ActionController::IntegrationTest def test_non_admin_auth request_uri = "/datafeed/event/report?blah=blah" get(request_uri) follow_redirect!
2005 Aug 11
3
[Bug 1069] session being terminated after succesful authentication
http://bugzilla.mindrot.org/show_bug.cgi?id=1069 Summary: session being terminated after succesful authentication Product: Portable OpenSSH Version: 4.1p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org
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 Sep 12
1
Q: 2.5.2p2, RSA auth and expired passwords
Quick question: ssh client and server 2.5.2p2, RSA authentication. Should the user be prompted to change their password if it's expired? -- John Hardin <johnh at aproposretail.com> Internal Systems Administrator voice: (425) 672-1304 Apropos Retail Management Systems, Inc. fax: (425) 672-0192
2020 Jun 02
2
"ssh -Q key" does not list rsa-sha2 algorithms
On Tue, 2 Jun 2020 at 18:48, Brian Candler <b.candler at pobox.com> wrote: [about ssh -Q ssh_config_keyword] > There is also "-Q key-sig" in recent versions (not sure exactly how recent, but 7.6 doesn't have it) Added in the same commit (Feb this year), first released in 8.3: https://github.com/openssh/openssh-portable/commit/d4d9e1d40514e2746f9e05335d646512ea1020c6 --
2003 Jul 01
1
Question about comment field for keys
The manual page for ssh-keygen says: "For RSA1 keys, there is also a comment field in the key file this is only for convenience to the user to help identify the key." It seems though that RSA2 and DSA keys also have comment fields, not just RSA1. Is this just an error in the documentation? Also the documentation says that only RSA1 key comments can be changed with ssh-keygen's
2020 Jun 01
3
"ssh -Q key" does not list rsa-sha2 algorithms
With the upcoming deprecation of ssh-rsa I was trying to see what keys my version of OpenSSH ( 7.8p1 ) supports. I noticed that "ssh -Q key" does not actually list the suggested algorithms to transition to ( rsa-sha2-256 and rsa-sha2-512 ) even though they are supported. Looking through the code, it looks like an issue with the arguments passed to sshkey_alg_list in ssh.c where it should
2001 Nov 15
1
ssh -2 and hostbasedauth
Hi, I'm trying to figure out how to read OpenSSH's log files (to assist our people in diagnosing "why is it always asking me for passwords"). All clients and servers are 3.0p1. First: server does not have the client's RSA2 key in known_host. debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got
2015 May 08
4
Q: respecting .ssh/id_rsa
While attempting to debug something else I ran across this: ssh -vvv somehost . . . debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/identity-cert type -1 debug3: Not a RSA1 key file /root/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing
2018 Feb 11
0
Best mail encryption solution for per-user
Quoting tai74 at vfemail.net: > Aki really thanks for reply,, I hope for continue the conversation, > >>> Do you have advice about Dovecot plugins for mail encryption: >>> >>> https://wiki2.dovecot.org/Plugins/MailCrypt >>> https://0xacab.org/riseuplabs/trees >>> >>> I like NaCL based encryption but the MailCrypt plugin is better
2020 Jun 01
5
"ssh -Q key" does not list rsa-sha2 algorithms
On Tue, 2 Jun 2020 at 06:12, Christian Weisgerber <naddy at mips.inka.de> wrote > On 2020-06-01, Ethan Rahn <ethan.rahn at gmail.com> wrote: > > > With the upcoming deprecation of ssh-rsa I was trying to see what keys my > > version of OpenSSH ( 7.8p1 ) supports. I noticed that "ssh -Q key" does not > > actually list the suggested algorithms to
2000 Nov 17
8
To Do list...
This is just portable todo list. From the sounds of it Markus has his own to do list. But can everyone review and let me know if there is anything missing from this list. (Note.. I'm not looking for 'SSH should support XYZ feature.' unless it's directly related to portability.) Or if there is anything on this list that has been completed. (Namely Tru64 SIA support?) Thanks.
2006 Nov 28
2
[LLVMdev] moving to svn?
On Tue, 28 Nov 2006, Bill Wendling wrote: > Perhaps someone could come up with a list of different versioning > software, list the pros and cons, and then we could vote? (Has anyone > mentioned Bitkeeper yet? :-) There are a couple reasons we are using CVS still: 1. CVS works and is well understood by all involved. 2. The main deficiencies of CVS don't impact us much (we aren't
2011 Dec 19
1
Using Amazon S3 storage for Maildir ?
I wonder if anyone has tried using an IMAP server with Amazon S3 as a backend. There would be many factors to consider (speed, etc). However, moreso, I don't know that Maildir(++) would support multiple folders that might be linked into the cloud. For example, higher-I/O local incoming mail is on disk, some folders archived on S3. Could be easily done by simply creating another