[JBoss JIRA] (JBIDE-17972) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17972?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17972:
---------------------------------------------
[~adietish] says that if you answer Yes it will actually accept this hostkey - thus it already doing what we can do.
This dialog will come up for every new SSH host you connect to - exactly same as on command line ssh or rhc or in a browser for hosts without certificates.
> Add ability to "always accept" the hostkey of the SSH connection for cloning git repos
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17972
> URL: https://issues.jboss.org/browse/JBIDE-17972
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: uxtest
> Fix For: 4.3.x
>
>
> Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-3014) On Mac Maverick JVM shared library points to wrong directory
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3014?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3014:
-------------------------------------------
Martin - there are standard locations we can look at provide a better default and just saying "JDK does not work - fix it" is not helpful to the user.
Should say something like JDK does not work, need to be a full JDK Java 7 or higher or similar if user point to a broken jdk.
and if the folder does not contain anything it should not make it sound that a JDK is actually there ;)
> On Mac Maverick JVM shared library points to wrong directory
> ------------------------------------------------------------
>
> Key: JBDS-3014
> URL: https://issues.jboss.org/browse/JBDS-3014
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta1
> Environment: Mac on Maverick
> Reporter: Robb Greathouse
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 8.0.0.Beta3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The JVM shared library "/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/../lib/server/libjvm.dylib"
> does not contain the JNI_CreateJavaVM symbol.
> This prevents it from starting.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17973) Obscure database password
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ]
Catherine Robson commented on JBIDE-17973:
------------------------------------------
I think putting the sensitive information in a collapsed panel could be a good solution for now.
> Obscure database password
> -------------------------
>
> Key: JBIDE-17973
> URL: https://issues.jboss.org/browse/JBIDE-17973
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: uxtest
> Fix For: 4.3.x
>
>
> When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured.
> It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment.
> Reproduce steps:
> 1. Open new OpenShift Application wizard
> 2. Sign in & proceed to next screen
> 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen
> 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen
> 5. Click next on set up project screen
> 6. Click finish on next screen
> 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5...
> Expected: Password on this pop-up should be obscured.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-3100) JBDS 8 splash screen should be improved
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3100?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen closed JBDS-3100.
-------------------------------------
Resolution: Rejected
its an 8. Very few ways to draw those.
It is a different color.
Different font.
Rejecting as FUD :)
> JBDS 8 splash screen should be improved
> ---------------------------------------
>
> Key: JBDS-3100
> URL: https://issues.jboss.org/browse/JBDS-3100
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 8.0.0.Beta3
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: uxtest
>
> There was a usability testing yesterday focused on OpenShift plugin. One note talked about splash screen:
> {quote}
> The 8 for JBDS spash screen looks a lot like Oracle 8 when that came out - big red 8. Probably need to do something different for the branding.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months