Sent: Monday, March 04, 2013 2:11 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: issue with 4.1
>>>
>>> +1 (again)
>>>
>>> On 3/4/13 1:06 PM, "Alex Huang" wrote:
>>>
>>>> +1. It does not belo
+1. Will be changed in 4.2. Didn't make it into 4.1 to disable to autoupgrade.
--Alex
> -Original Message-
> From: Edison Su [mailto:edison...@citrix.com]
> Sent: Monday, March 4, 2013 2:24 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: issue with 4.1
parated from mgt server.
>
>> -Original Message-
>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>> Sent: Monday, March 04, 2013 2:11 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: issue with 4.1
>>
>> +1 (again)
>
I even think db upgrade should be separated from mgt server.
> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Monday, March 04, 2013 2:11 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: issue with 4.1
>
> +1 (ag
gement server.
> >
> >--Alex
> >
> >> -Original Message-
> >> From: John Burwell [mailto:jburw...@basho.com]
> >> Sent: Monday, March 4, 2013 8:13 AM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: Re: issue with 4.1
&g
dstack-dev@incubator.apache.org
>> Subject: Re: issue with 4.1
>>
>> Chip,
>>
>> My recommendation in the ticket is to extract the script from the
>> management server to a external script provided as a connivence to end
>> users. If we encounter a situation
+1. It does not belong to the management server.
--Alex
> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Monday, March 4, 2013 8:13 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: issue with 4.1
>
> Chip,
>
> My reco
+1 to John's comment,
Regards
ilya
> -Original Message-
> From: John Burwell [mailto:jburw...@basho.com]
> Sent: Monday, March 04, 2013 11:16 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: issue with 4.1
>
> Chip,
>
> I neglected to mentio
Chip,
I neglected to mention in my reply that the extracted utility script would also
need to be refactored to accept the various important bits (e.g. password,
type, and length) into command line parameters or prompt the user. The core of
the security issue I see is the defaulting of the pass
Chip,
My recommendation in the ticket is to extract the script from the management
server to a external script provided as a connivence to end users. If we
encounter a situation where a certificate is not present, provide a meaningful
error message in the logs and exit. If a user needs help g
On Mon, Mar 04, 2013 at 11:08:32AM -0500, John Burwell wrote:
> Chip,
>
> I opened CLOUDSTACK-1389 for the exact issue described by Sebastien. As
> noted in the ticket, I believe the behavior implemented by the script
> represents a security vulnerability(with or without the use of sudo).
Have a
Chip,
I opened CLOUDSTACK-1389 for the exact issue described by Sebastien. As
noted in the ticket, I believe the behavior implemented by the script
represents a security vulnerability(with or without the use of sudo).
Thanks,
-John
On Mon, Mar 4, 2013 at 10:59 AM, Chip Childers wrote:
> On Mo
On Mon, Mar 04, 2013 at 08:51:03AM -0700, Marcus Sorensen wrote:
> There's a bug for this, I think it's related to passwordless sudo for
> cloud user on management server.
Is this the one?
https://issues.apache.org/jira/browse/CLOUDSTACK-1389
>
> On Mon, Mar 4, 2013 at 6:52 AM, Sebastien Goasgu
There's a bug for this, I think it's related to passwordless sudo for
cloud user on management server.
On Mon, Mar 4, 2013 at 6:52 AM, Sebastien Goasguen wrote:
> Hi I am trying to test the latest 4.1 (and 4.1l10n branch).
>
> I am on OSX 10.8.2, I had to update to JDK 1.7 to get things going.
>
Interesting, after 20 minutes or even more it went through with:
WARN [cloud.server.ConfigurationServerImpl] (Timer-2:) Failed to inject
generated public key into systemvm iso injectkeys.sh: Failed to mount original
iso
/Users/sebastiengoasguen/Documents/incubator-cloudstack/client/target/clou
15 matches
Mail list logo
