Thus said Warren Young on Fri, 11 Dec 2015 15:26:29 -0700:
> I'd say take it up with the plink developers, then. It *should* do
> interactive prompting in this case.
It's possible that there is something in the way Fossil forks the plink
process on Windows that is causing plink not to prompt
Thus said Daniel Dumitriu on Fri, 11 Dec 2015 23:18:41 +0100:
> By the way: Does the whole reasoning not hold for https URLs? They
> allow a password on the command line, too.
HTTP(S) urls behave differently than SSH because they are different
protocols/systems. The password in HTTP(S) i
On Dec 11, 2015, at 3:18 PM, Daniel Dumitriu wrote:
>
>> Why can’t you just use SSH keys? The wish for automated login without
>> leaking passwords is exactly the problem they solve.
> I can and I do. But maybe other users cannot
Why “cannot”? I get “will not,” but “CAN” not?
You’re asking f
> Why can’t you just use SSH keys? The wish for automated login without
> leaking passwords is exactly the problem they solve.
I can and I do. But maybe other users cannot, and they get tempted by
that :password bit. Or they like to carry on a stick plink next to their
fossil executable, so they
On Dec 11, 2015, at 2:59 AM, Daniel Dumitriu wrote:
>
> the documentation (e.g. fossil clone) mentions this
> possibility for ssh URL's ([userid[:password]@]host), so in my opinion
> either fossil passes the password further to plink
Interesting. It has a -pw flag for this.
(That is, “interest
On 11.12.2015 06:19, Andy Bradford said:
>> when called as a process [1]. I don't know if this can be solved
>> inside fossil; a workaround is to use a modified plink, e.g. that from
>> TortoiseSVN.
>
> You can configure Fossil to use the modified plink. Use:
>
> fossil clone --ssh-command /
Thus said Daniel Dumitriu on Thu, 10 Dec 2015 15:59:29 +0100:
> when called as a process [1]. I don't know if this can be solved
> inside fossil; a workaround is to use a modified plink, e.g. that from
> TortoiseSVN.
You can configure Fossil to use the modified plink. Use:
fossil clone --s
I would use Pageant if you don't want to have to respond to an interactive
password prompt.
On Thu, Dec 10, 2015 at 9:59 AM, Daniel Dumitriu
wrote:
> Hi,
>
> Coming back to my own unanswered question: it seems like it has to do
> with standard (PuTTY) plink's inability to hook itself to console
On Thu, Dec 10, 2015 at 03:59:29PM +0100, Daniel Dumitriu wrote:
> Still there seems to be another problem with fossil: it does not pass
> the password to plink when it was given on the command line as in
> user:pass@host:port. Maybe something along these lines ("-p pass")?
I would call that a sec
Hi,
Coming back to my own unanswered question: it seems like it has to do
with standard (PuTTY) plink's inability to hook itself to console input
when called as a process [1]. I don't know if this can be solved inside
fossil; a workaround is to use a modified plink, e.g. that from TortoiseSVN.
St
Hi,
I'm having problems using Fossil with the SSH protocol on Windows 8.1.
Somehow the password is not being prompted for. Interestingly enough,
when I run the relevant plink command by itself, the password prompt
comes up and connection succeeds.
Using keys (Pageant) works though - at least if o
11 matches
Mail list logo