Displaying 20 results from an estimated 700 matches similar to: "Forward only specific identities"
2013 Apr 30
3
[Bug 2095] New: ssh client not respecting IdentitiesOnly=yes option
https://bugzilla.mindrot.org/show_bug.cgi?id=2095
Bug ID: 2095
Summary: ssh client not respecting IdentitiesOnly=yes option
Classification: Unclassified
Product: Portable OpenSSH
Version: 6.2p1
Hardware: All
OS: All
Status: NEW
Severity: trivial
Priority: P5
Component: ssh
2008 Feb 27
4
Error in cor.default(x1, x2) : missing observations in cov/cor
Hello,
I'm trying to do cor(x1,x2) and I get the following error:
Error in cor.default(x1, x2) : missing observations in cov/cor
A few things:
1. I've used cor() many times and have never encountered this error.
2. length(x1) = length(x2)
3. is.numeric(x1) = is.numeric(x2) = TRUE
4. which(is.na(x1)) = which(is.na(x2)) = integer(0) {the same goes for
is.nan()}
5. I also try
2019 Oct 09
3
[Bug 3080] New: Document IdentityFile=none and clarify interaction of defaults with IdentitiesOnly
https://bugzilla.mindrot.org/show_bug.cgi?id=3080
Bug ID: 3080
Summary: Document IdentityFile=none and clarify interaction of
defaults with IdentitiesOnly
Product: Portable OpenSSH
Version: 8.0p1
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: P5
2019 Apr 02
2
IdentityFile vs IdentitiesOnly
Hi Darren,
On 4/1/19 10:41 AM, Darren Tucker wrote:
> On Mon, 1 Apr 2019 at 08:12, Harald Dunkel <harald.dunkel at aixigo.de> wrote:
>> I've got a moderate number of keys in my ssh config file.
>> Problem: Very often I get an error message like
> [...]
>> The solution seems to be to set IdentitiesOnly, e.g.:
> [...]
>> Shouldn't an explicit
2024 Apr 19
2
[Bug 3681] New: SSH Agent Certificate Not Recognized with 'IdentitiesOnly' Configured
https://bugzilla.mindrot.org/show_bug.cgi?id=3681
Bug ID: 3681
Summary: SSH Agent Certificate Not Recognized with
'IdentitiesOnly' Configured
Product: Portable OpenSSH
Version: 9.7p1
Hardware: All
OS: All
Status: NEW
Severity: trivial
Priority: P5
Component:
2009 Jan 22
0
Unintended key info disclosure via ForwardAgent?
It seems that users may be disclosing unintended public key info
when logging into remote hosts.
Use of the words keypair/keyid/etc have been bastardized. Signature
is likely better. Note also, the author may be without clue.
Setup:
[g] - refers to an administrative group of hosts
[n] - refers to a host within that group
ws[g][n] - management workstations [trusted]
User ssh-add's keys for
2004 Mar 30
0
[Bug 448] ssh ignores key specified with -i if agent is running
http://bugzilla.mindrot.org/show_bug.cgi?id=448
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From djm at mindrot.org 2004-03-30 16:12
2019 Apr 01
2
IdentityFile vs IdentitiesOnly
Hi folks,
I've got a moderate number of keys in my ssh config file.
Problem: Very often I get an error message like
Received disconnect from 2001:db8::8077 port 999:2: Too many authentication failures
Authentication failed.
AFAIU the ssh-agent is to blame here, trying out all keys
he has ever seen. This conflicts with MaxAuthTries 6, set by
default on the peer.
The solution seems to be to
2008 Jun 09
2
Plot timer in a for loop
Hello,
This code works fine but is so fast I can't see anything but the last plot.
for (i in nrow(X)){
plot(as.numeric(d[i,])) }
I'd like to view a plot every 500 milliseconds, nrow(X) = 400. How?
Thanks
--
View this message in context: http://www.nabble.com/Plot-timer-in-a-for-loop-tp17741975p17741975.html
Sent from the R help mailing list archive at Nabble.com.
2008 Feb 08
2
When I cbind the POSIXct gets lost
I would like to create a new dataframe from the DateTime column of an
existing dataframe and a numeric vector. When I do cbind(x[,1], y) the
result is:
[1,] 1199370600 12.500
[2,] 1199371200 69.375
[3,] 1199371800 23.750
where the first column you see used to look like:
"2008-01-03 08:30:00 Central Standard Time"
"2008-01-03 08:40:00 Central Standard Time"
2024 Aug 10
1
'Too many authentication failures' nuisance
On 8/10/24 17:13, Chris Green wrote:
> I have several ssh keys in the ~/.ssh directory of my desktop machine.
> As a result whenever I try to connect to a system which uses password
> authentication I get the "Too many authentication failures" error.
>
> Yes, I know I can get round this by setting PreferredAuthentications
> but this is rather a nuisance to have to do
2020 Oct 04
6
ability to select which identity to forward when using "ForwardAgent" ?
Hi,
I usually have around 10 identities loaded in my local ssh-agent and when I
use the "ForwardAgent" option all them are forwarded to the remote server,
which is not ideal. I usually only need to forward one (or two) of the
identities and I would like to be able to choose which one(s) to forward.
Looking for solutions it seems that the only option is to create a new
ssh-agent, add
2024 Oct 01
1
ssh while ssh-agent is running
> ssh should do this already
Hi Damien,
Let's discuss what it does already... For example, if ssh-agent already has
six keys, will it append the "-i key" as the seventh choice?
Apparently there is a "six-key authentication limit on most servers". A
seventh key will fail. If ssh is adding the new key to the end of the list
it would be expected to fail.
This limit is
2014 Jan 09
1
OSX - SSH agent functionality differing based upon CLI arguments
Trying to get SSH agent forwarding working for a popular open source configuration management system called Ansible.
I?ve had some unexpected behaviour, the only cause of which I can find is how I express the command line arguments.
http://stackoverflow.com/questions/20952689/vagrant-ssh-agent-forwarding-how-is-it-working?noredirect=1#comment31511341_20952689
In summarise:
In the first
2020 Apr 23
6
[Bug 3153] New: Prefer user specified keys to avoid the agent overloading MaxAuthTries before even trying the key that was specified
https://bugzilla.mindrot.org/show_bug.cgi?id=3153
Bug ID: 3153
Summary: Prefer user specified keys to avoid the agent
overloading MaxAuthTries before even trying the key
that was specified
Product: Portable OpenSSH
Version: 8.2p1
Hardware: Other
OS: Linux
Status: NEW
2014 Mar 20
1
[Bug 2214] New: Key is detected as existing if LogLevel=QUIET
https://bugzilla.mindrot.org/show_bug.cgi?id=2214
Bug ID: 2214
Summary: Key is detected as existing if LogLevel=QUIET
Product: Portable OpenSSH
Version: 6.2p1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: ssh-copy-id
Assignee: unassigned-bugs at
2016 Mar 12
3
Problem with ssh-copy-id when home folder contains spaces
Hi,
some guy on the Cygwin mailing list found that ssh-copy-id chokes
on directories with spaces, which are quite common on Windows.
He also provided an easy fix, basically just adding quotes, which I
attached to this mail. Would that be ok to apply upstream?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
-------------- next part --------------
diff --git
2007 Oct 26
2
calculating correlation of a Supply/Demand measure and price change (in high frequency time series data)
Regarding "financial" data: I have a high frequency (1 minute) measure of
supply/demand and I'd like to know if it has any influence on short term
price changes (also 1 minute).
Question: How do I calculate the correlation between this supply/demand
measure and price changes (correctly)?
Some facts about that data:
The price changes and supply/demand measure are non-normal. An
2011 Aug 25
1
Add missing -o options in ssh(1) manual
A few options appear to be missing from the list in ssh's manual.
The one I didn't add is EnableSSHKeysign, whose description implies
it is only effective when placed in the system-wide config file.
Index: ssh.1
===================================================================
RCS file: /cvs/src/usr.bin/ssh/ssh.1,v
retrieving revision 1.319
diff -u -p -r1.319 ssh.1
--- ssh.1 7 May 2011
2024 Oct 01
1
[Possible phishing attempt] Re: ssh while ssh-agent is running
> A problem with that, it's a bit cumbersome. You have to realize what the
> cause of the problem, so that adding the flag will fix it (why is ssh
> failing anyway?). And then check the exact syntax. And write that, on the
> command-line. It is another option though.
Personally, I set IdentitiesOnly yes as the global default in ~/.ssh/config, and explicitly set the preferred key