(using the last ISO in the sipx-stage area)

Ok. Question here. Did the install. Seeing the certificate being created
using the domain name, instead of hostname.

example:

host name used during creating: pbx
domain/realm/sipdomain: smoke.myitdepartment.net

resulting certificate being presented upon login should be:
pbx.smoke.myitdepartment.net, but it is smoke.myitdepartment.net.

As a result cannot login because the basic constraints of the certificate
seem to be invalid:

normal (I think, 4.4)

Subject Type=End Entity
Path Length Constraint=None

4.6

Subject Type=CA (which is probably OK)
Path Length Constraint=0

Specifies the maximum allowable path length, the maximum number of CA
certificates that may be chained below (subordinate to) the subordinate CA
certificate being issued. The path length affects the number of CA
certificates used during certificate validation. The chain starts with the
end-entity certificate being validated and moves up.
This parameter has no effect if the extension is set in end-entity
certificates.
The permissible values are 0 or *n*. The value must be less than the path
length specified in the Basic Constraints extension of the CA signing
certificate.
0 specifies that no subordinate CA certificates are allowed below the
subordinate CA certificate being issued; only an end-entity certificate may
follow in the path.
*n* must be an integer greater than zero. This is the maximum number of
subordinate CA certificates allowed below the subordinate CA certificate
being used.
If the field is blank, the path length defaults to a value determined by
the path length set on the Basic Constraints extension in the issuer's
certificate. If the issuer's path length is unlimited, the path length in
the subordinate CA certificate is also unlimited. If the issuer's path
length is an integer greater than zero, the path length in the subordinate
CA certificate is set to a value one less than the issuer's path length;
for example, if the issuer's path length is 4, the path length in the
subordinate CA certificate is set to 3.

No matter what browser I use, it complains of a bad signature. Did I miss
something during setup?

Also, I had to manually edit my IP and set my gateway because no matter
what I did during setup it reverted to DHCP. I am wondering if something
has been inadvertently left off the setup script for CentOS to assign this
manually before the sipx script runs?

FWIW - To be more easily usable to some of us, it would be nice to include
both nano and wget packages during the ISO install like 4.4 did.

On Fri, Jul 6, 2012 at 8:53 AM, Tony Graziano
<[email protected]>wrote:

> chalk that us to lack of coffee. I forgot I had been.
>
>
> On Fri, Jul 6, 2012 at 8:43 AM, Douglas Hubler <[email protected]> wrote:
>
>> you should have been prompted during the install to enter your own root
>> password
>>
>> On Fri, Jul 6, 2012 at 8:24 AM, Tony Graziano
>> <[email protected]> wrote:
>> > what is the default password for the 4.6 iso during install? seems to no
>> > longer be root:setup.
>> >
>> >
>> > On Thu, Jul 5, 2012 at 5:22 PM, Michael Picher <[email protected]>
>> wrote:
>> >>
>> >> I was testing on an Amazon virtual with 1.7 GB of RAM an it was
>> swapping
>> >> hard and just killing the performance of the entire system.
>> >>
>> >> I'll re-test once we get to production and test it on Amazon Linux.
>> >>
>> >> Mike
>> >>
>> >>
>> >> On Thu, Jul 5, 2012 at 12:04 PM, Douglas Hubler <[email protected]>
>> wrote:
>> >>>
>> >>> "use memory" is a very complicated statement.
>> >>>
>> >>> It wasn't clear what the old system used for memory because it wasn't
>> >>> a server.  also, mongo uses a lot of virtual memory, which i don't
>> >>> think really counts.
>> >>>
>> >>> On Thu, Jul 5, 2012 at 11:56 AM, Todd Hodgen <[email protected]>
>> >>> wrote:
>> >>> > Mike – thanks for the heads up.
>> >>> >
>> >>> >
>> >>> >
>> >>> > I thought I had seen emails in the past that indicated MondoD and
>> 4.6
>> >>> > was
>> >>> > actually using less memory that the old database, I guess that isn’t
>> >>> > the
>> >>> > case any longer.
>> >>> >
>> >>> >
>> >>> >
>> >>> > This particular machine is for use in my own lab.
>> >>> >
>> >>> >
>> >>> >
>> >>> > From: [email protected]
>> >>> > [mailto:[email protected]] On Behalf Of Michael
>> >>> > Picher
>> >>> > Sent: Thursday, July 05, 2012 3:53 AM
>> >>> > To: sipXecs developer discussions
>> >>> > Subject: Re: [sipx-dev] Install of 4.6 ISO in State Area notes and
>> >>> > issues
>> >>> >
>> >>> >
>> >>> >
>> >>> > also, fyi, in my testing 2 GB of RAM will only work for very small
>> >>> > installs.
>> >>> > Mongo seems to like RAM and anything less than 4 seemed to cause
>> >>> > swapping
>> >>> > which killed performance on the server.  RAM seems more important
>> than
>> >>> > processor cores / speed with the new database.
>> >>> >
>> >>> >
>> >>> >
>> >>> > thanks,
>> >>> >
>> >>> >   mike
>> >>> >
>> >>> > On Wed, Jul 4, 2012 at 8:31 PM, Douglas Hubler <[email protected]>
>> >>> > wrote:
>> >>> >
>> >>> > On Wed, Jul 4, 2012 at 6:06 PM, Todd Hodgen <[email protected]>
>> >>> > wrote:
>> >>> >> MY workaround for now is to reboot, go into setup and then exit
>> setup.
>> >>> >> Seems to boot just fine after that.
>> >>> >
>> >>> > Thanks for testing.
>> >>> >
>> >>> > Sounds like setup didn't finish, so this is probably a show stopper.
>> >>> > Can you email me /var/log/sipxpbx/sipxagent.log?
>> >>> >
>> >>> > Does CentOS 6 install without issue on the machine?
>> >>> >
>> >>> > We've not seen any issues like this what-so-ever.
>> >>> >
>> >>> > _______________________________________________
>> >>> > sipx-dev mailing list
>> >>> > [email protected]
>> >>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Michael Picher, Director of Technical Services
>> >>> > eZuce, Inc.
>> >>> >
>> >>> > 300 Brickstone Square
>> >>> >
>> >>> > Suite 201
>> >>> >
>> >>> > Andover, MA. 01810
>> >>> >
>> >>> > O.978-296-1005 X2015
>> >>> > M.207-956-0262
>> >>> > @mpicher <http://twitter.com/mpicher>
>> >>> >
>> >>> > linkedin
>> >>> > www.ezuce.com
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> ------------------------------------------------------------------------------------------------------------
>> >>> >
>> >>> > There are 10 kinds of people in the world, those who understand
>> binary
>> >>> > and
>> >>> > those who don't.
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > _______________________________________________
>> >>> > sipx-dev mailing list
>> >>> > [email protected]
>> >>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>> >>> _______________________________________________
>> >>> sipx-dev mailing list
>> >>> [email protected]
>> >>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Michael Picher, Director of Technical Services
>> >> eZuce, Inc.
>> >>
>> >> 300 Brickstone Square
>> >>
>> >> Suite 201
>> >>
>> >> Andover, MA. 01810
>> >>
>> >> O.978-296-1005 X2015
>> >> M.207-956-0262
>> >> @mpicher <http://twitter.com/mpicher>
>> >> linkedin
>> >> www.ezuce.com
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------------------------------------
>> >> There are 10 kinds of people in the world, those who understand binary
>> and
>> >> those who don't.
>> >>
>> >>
>> >> _______________________________________________
>> >> sipx-dev mailing list
>> >> [email protected]
>> >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>> >
>> >
>> >
>> >
>> > --
>> > ~~~~~~~~~~~~~~~~~~
>> > Tony Graziano, Manager
>> > Telephone: 434.984.8430
>> > sip: [email protected]
>> > Fax: 434.465.6833
>> > ~~~~~~~~~~~~~~~~~~
>> > Linked-In Profile:
>> > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> > Ask about our Internet Fax services!
>> > ~~~~~~~~~~~~~~~~~~
>> >
>> > Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
>> > 2013!
>> >
>> >
>> > LAN/Telephony/Security and Control Systems Helpdesk:
>> > Telephone: 434.984.8426
>> > sip: [email protected]
>> >
>> > Helpdesk Customers: http://myhelp.myitdepartment.net
>> > Blog: http://blog.myitdepartment.net
>> >
>> > _______________________________________________
>> > sipx-dev mailing list
>> > [email protected]
>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>> _______________________________________________
>> sipx-dev mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>>
>
>
>
> --
> ~~~~~~~~~~~~~~~~~~
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.465.6833
> ~~~~~~~~~~~~~~~~~~
> Linked-In Profile:
> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> Ask about our Internet Fax services!
> ~~~~~~~~~~~~~~~~~~
>
> Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
> 2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013%22>
>
>


-- 
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013%22>

-- 
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to