Bug 124482 - [SSH2] Dialogs that warn of creation of .ssh files are excessive and confusing
Summary: [SSH2] Dialogs that warn of creation of .ssh files are excessive and confusing
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-01-19 08:50 EST by Kim Horne CLA
Modified: 2019-09-06 16:06 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kim Horne CLA 2006-01-19 08:50:56 EST
I just created a new sandbox account on my mac.  When I created a new SSH connection I was warned about the creation of a series of different files.  Each file prompted the creation of a new dialog.  Could these not be condensed to one dialog?  Also, the last dialog seemed confusing to me.  It warned of the creation of a file and then told me to check the permissions.  Why do I need to check the permissions?  Did  the operation not succeed entirely?
Comment 1 Atsuhiko Yamanaka CLA 2006-04-12 10:05:34 EDT
(In reply to comment #0)
> creation of a file and then told me to check the permissions.  Why do I need to
> check the permissions?  Did  the operation not succeed entirely?

The sshd will expect that access permissions for home directory(~) and ~/.ssh
are 'rwx------', but Java API does not allow us to modify file permissions.

In using extssh CVS access, there is no poblem, but in the future if you 
need to login to that mac from other hosts with public authentication, 
you will get troubles.
Comment 2 Michael Valenta CLA 2006-09-14 11:04:16 EDT
There is no work planned for this item in 3.3.
Comment 3 Eclipse Webmaster CLA 2007-07-29 09:18:50 EDT
Changing OS from Mac OS to Mac OS X as per bug 185991
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:06:07 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.