December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-11408 at 12/9/13 7:37 AM: ------------------------------------------------------------------- This was reported to Eclipse when using the CVS tooling: https://bugs.eclipse.org/bugs/show_bug.cgi?id=179635 but the issue went out of discussion since ages (latest activity: 2007) was (Author: adietish): This was reported to Eclipse when using the CVS tooling: https://bugs.eclipse.org/bugs/show_bug.cgi?id=179635 > Eclipse SSH Preferences creates SSH keys with permissions 755 > ------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11408: ------------------------------------- Issue Type: Task (was: Bug) > Eclipse SSH Preferences creates SSH keys with permissions 755 > ------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, upstream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11408: ------------------------------------- Summary: Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER) (was: Eclipse SSH Preferences creates SSH keys with permissions 755) > Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER) > ----------------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, upstream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11408: ------------------------------------- Forum Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=179635 > Eclipse SSH Preferences creates SSH keys with permissions 755 (WATCHER) > ----------------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, upstream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12171) Link to the OpenShift status page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12171?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12171: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > Link to the OpenShift status page > --------------------------------- > > Key: JBIDE-12171 > URL: https://issues.jboss.org/browse/JBIDE-12171 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: LATER > > Attachments: openshift-status.png > > > OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). > We could also display the current status in the OpenShift explorer. > !openshift-status.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11408) Eclipse SSH Preferences creates SSH keys with permissions 755

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11408?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11408: ------------------------------------------ This was reported to Eclipse when using the CVS tooling: https://bugs.eclipse.org/bugs/show_bug.cgi?id=179635 > Eclipse SSH Preferences creates SSH keys with permissions 755 > ------------------------------------------------------------- > > Key: JBIDE-11408 > URL: https://issues.jboss.org/browse/JBIDE-11408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: windows 7 > Reporter: Nam Duong > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > similar to https://issues.jboss.org/browse/JBIDE-10061 > When I create a domain for the first time on a clean windows environment, I have to create a new set of keys. Those keys have permissions 755 but they need to be 600 in order to run git/ssh commands with them. I get this error: > git clone ssh://118b5a4772744905b3c19059c5c0ac9c@kitchensink-nduongdemo.rhcloud.com/~/git/kitchensink.git/ > Cloning into 'kitchensink'... > The authenticity of host 'kitchensink-nduongdemo.rhcloud.com (174.129.77.140)' can't be established. > RSA key fingerprint is cf:ee:77:cb:0e:fc:027:72:7e:ae:80:c0:90:88:a7. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'kitchensink-nduongdemo.rhcloud.com,174.129.77.140' (RSA) to the list of known hosts. > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > Permissions 0755 for '/home/spousty/.ssh/id_rsa' are too open. > It is required that your private key files are NOT accessible by others. > This private key will be ignored. > bad permissions: ignore key: /home/spousty/.ssh/id_rsa > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > fatal: The remote end hung up unexpectedly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14307) create unit-tests for Importing procedures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14307?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14307: ------------------------------------------ bumped to LATER since not sure we have enough time to do this in the near future even though it would be highly advisable. > create unit-tests for Importing procedures > ------------------------------------------ > > Key: JBIDE-14307 > URL: https://issues.jboss.org/browse/JBIDE-14307 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: LATER > > > The import startegies / procedures are pretty complex and we definitely should unit-test them. > Unfortunately they're still very tied to the UI and thus there's still some work to do to be able to unit-test them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14307) create unit-tests for Importing procedures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14307?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14307: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > create unit-tests for Importing procedures > ------------------------------------------ > > Key: JBIDE-14307 > URL: https://issues.jboss.org/browse/JBIDE-14307 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: LATER > > > The import startegies / procedures are pretty complex and we definitely should unit-test them. > Unfortunately they're still very tied to the UI and thus there's still some work to do to be able to unit-test them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15380) EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER=

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15380: ------------------------------------- Summary: EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER= (was: Show Git Hooks output and reset timeout when a new receiving new output) Issue Type: Task (was: Feature Request) Forum Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=418653 > EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER= > --------------------------------------------------------------------------------------- > > Key: JBIDE-15380 > URL: https://issues.jboss.org/browse/JBIDE-15380 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Mickael Istria > Assignee: Andre Dietisheim > Fix For: LATER > > > When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run. > Instead of this simple timeout, I'd rather see: > * The hooks output shown in the push dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15380) Show Git Hooks output and reset timeout when a new receiving new output

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15380 at 12/9/13 6:34 AM: ------------------------------------------------------------------- Turns out that this issue is about the EGit Push dialog still not being able to show the output of the push operation as it comes in - something that our tooling is perfectly capable of doing. In consequence this is a watcher issue for the Eclipse bugzilla entry here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=418653 was (Author: adietish): Turns out that this issue is about the EGit Push dialog still not being able to show the output of the push operation as it comes in - something that our tooling is perfectly capable of doing. > Show Git Hooks output and reset timeout when a new receiving new output > ----------------------------------------------------------------------- > > Key: JBIDE-15380 > URL: https://issues.jboss.org/browse/JBIDE-15380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Mickael Istria > Assignee: Andre Dietisheim > Fix For: LATER > > > When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run. > Instead of this simple timeout, I'd rather see: > * The hooks output shown in the push dialog > * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push was triggered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2013