On 30 January 2015 at 11:40, Hon1nbo <hon1nbo.l...@gmail.com> wrote:

> Do you have a link for the ticket? I have to operate all non-<redacted my
> non ONE workplace> on my phone currently as I am maxing out all my machines
> for work.
>

This is the ticket:
http://dev.opennebula.org/issues/2068


>
> Random passwords would be even better!
>
> Also is there a contact point for a opennebula security team or is someone
> assigned to handle VNC issues? I found a vuln in the noVNC system that I
> need to report (not critical, but still an issue).
>

I have already checked the tickets you opened in our dev portal. We will
try to provide a fix for these issues. Thank you for your feedback


>
> -Jim
>
>
> On January 29, 2015 4:30:45 AM CST, Daniel Molina <dmol...@opennebula.org>
> wrote:
>>
>>
>>
>> On 29 January 2015 at 10:33, Daniel Molina <dmol...@opennebula.org>
>> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> On 28 January 2015 at 23:20, Hon1nbo <hon1nbo.l...@gmail.com> wrote:
>>>
>>>> Is it possible to contextualize the VNC password, similar to the
>>>> SSH_PUBLIC_KEY per user profile?
>>>>
>>>> I have VNC web viewing working now across my entire deployment, and
>>>> it's finally stable enough I want my users to use it for debugging (took
>>>> forever to find out there was a bug in the sunstone ruby code for secure
>>>> websockets preventing most browsers from allowing the viewer without
>>>> changing to a lower security setting, which I'll be submitting when I get
>>>> home).
>>>>
>>>
>>> Patches are more than welcome.
>>>
>>>>
>>>> But now that this is working, I'd like for my users to be able to use
>>>> it without having to modify the templates every time for a new VNC 
>>>> password.
>>>>
>>>> Is this possible currently, or should I put in a feature request?
>>>>
>>>
>>> This is not possible. You can provide custom attrs [1] on instantiation
>>> but the vnc password cannot be replaced. Could you please open a feature
>>> request in our dev portal?
>>>
>>
>> There is already a ticket related to this,  I don't know if this would
>> fit your use case. The idea is that a random password is generated for each
>> VM and then the user can retrieve it from the vm info in sunstone
>>
>>
>>> Thank you
>>>
>>> [1]
>>> http://docs.opennebula.org/4.10/user/virtual_resource_management/vm_guide.html#ask-for-user-inputs
>>>
>>>
>>>> -Jim
>>>> --
>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users@lists.opennebula.org
>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Daniel Molina
>>> Project Engineer
>>> OpenNebula - Flexible Enterprise Cloud Made Simple
>>> www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula
>>>
>>
>>
>>
>> --
>> --
>> Daniel Molina
>> Project Engineer
>> OpenNebula - Flexible Enterprise Cloud Made Simple
>> www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula
>>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>



-- 
--
Daniel Molina
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Reply via email to