Endpoint name, domain, and secret validation

Document created by cdnadmin on Jan 24, 2014
Version 1Show Document
  • View in full screen mode
This document was generated from CDN thread

Created by: Christopher Verges on 23-02-2011 02:50:58 AM
In the EnergyWise configuration guide on cisco.com, the domain/secret are defined as follows:
 
------------------------------------------------------------------------------

From the Cisco EnergyWise Configuration Guide:


domain domain-name
Assign the entity to a domain with the specified domain-name.

<ul>
<li class="level1">
You can enter alphanumeric characters and symbols such as #, (, %, !, or &.
</li>
<li class="level1">
Do not use an asterisk (*) or a blank space between the characters and symbols.
</li>
</ul>

secret [0 | 7] password
Set the password for secure communication among the entities in the domain.

<ul>
<li class="level1">
Optional) 0¿Use an unencrypted password.
</li>
<li class="level1">
(Optional) 7¿Use an hidden password.
</li>
</ul>

If you do not enter 0 or 7, the entity uses the default value of 0.

<ul>
<li class="level1">
You can enter alphanumeric characters and symbols such as #, (, %, !, or &.
</li>
<li class="level1">
Do not use an asterisk (*) or a blank space between the characters and symbols.
</li>
</ul>
------------------------------------------------------------------------------
 

Based on empirical testing, the following are not allowed:

<ul>
<li class="level1">
Semicolon (;)
</li>
<li class="level1">
Asterisk (*)
</li>
<li class="level1">
Question mark (?)
</li>
<li class="level1">
Single quote (')
</li>
<li class="level1">
Double quote (¿)
</li>
<li class="level1">
Tick mark (`)
</li>
<li class="level1">
Vertical pipe (|)
</li>
<li class="level1">
Backslash (\)
</li>
<li class="level1">Whitespace (space, \t, \n, \r, etc.)</li>
</ul>
Everything else tested was allowed:
 
RegEx:   [A-Za-z0-9_\-[\]()~!@#$%^&=+{}:;<>./]+
 
In short, what is the full list of actual alphanumeric characters and symbols permitted?  The term "such as" in the Configuration Guide seems to indicate that only 5 characters are allowed, but testing shows that quite a few more are.
 
Thanks,
Chris

Subject: RE: Endpoint name, domain, and secret validation
Replied by: Brock Miller on 28-02-2011 06:39:04 PM
Hi Chris,

You are correct that the "such as" reference in the config guide is not clear enough.

Currently, we have a white list of allowed characters listed here:

"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789~!@#$%^&()_-+={}[]:.></"

Additionally, the ROLE field allows whitespaces.

Thanks,

Brock

Attachments

    Outcomes