[jira] [Created] (MYNEWT-124) Log buffer issues

[Christopher Collins (JIRA)]

Christopher Collins created MYNEWT-124:
--

 Summary: Log buffer issues
 Key: MYNEWT-124
 URL: https://issues.apache.org/jira/browse/MYNEWT-124
 Project: Mynewt
  Issue Type: Bug
  Components: Misc
Reporter: Christopher Collins
Assignee: Sterling Hughes
 Fix For: v0_8_0_beta2


When a message is written to a log, some buffers are allocated on the stack in 
various places in the code.  This results in two issues:

# Undue stack-size requirements placed on any task which uses sys/log.
# Hard limit placed on the maximum length of a log line.

There are two functions which exhibit this behavior:
* log_printf (LOG_PRINTF_MAX_ENTRY_LEN = 128)
* console_vprintf (CONS_OUTPUT_MAX_LINE = 128)

I do not have a proposed fix.  I believe Marko suggested streaming bytes to the 
destination, rather than writing to an intermediate buffer.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-91) Controller only nimble stack

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-91:
--
Fix Version/s: v1_0_0_beta1

> Controller only nimble stack
> 
>
> Key: MYNEWT-91
> URL: https://issues.apache.org/jira/browse/MYNEWT-91
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Nimble
>Affects Versions: v0_8_0_beta1
>Reporter: William San Filippo
>Assignee: William San Filippo
>Priority: Minor
>  Labels: controller
> Fix For: v1_0_0_beta1
>
>
> We need to implement a controller only BLE stack.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-38) Implement ECC correction in NFFS

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-38:
--
Fix Version/s: v1_0_0_beta1

> Implement ECC correction in NFFS
> 
>
> Key: MYNEWT-38
> URL: https://issues.apache.org/jira/browse/MYNEWT-38
> Project: Mynewt
>  Issue Type: New Feature
>  Components: NFFS
>Reporter: Sterling Hughes
>Assignee: Christopher Collins
> Fix For: v1_0_0_beta1
>
>
> Data stored in NFFS files should optionally have ECC coding applied to them 
> to correct for data corruption.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-37) Implement FS compression in NFFS

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-37:
--
Fix Version/s: v1_0_0_beta1

> Implement FS compression in NFFS
> 
>
> Key: MYNEWT-37
> URL: https://issues.apache.org/jira/browse/MYNEWT-37
> Project: Mynewt
>  Issue Type: New Feature
>  Components: NFFS
>Reporter: Sterling Hughes
>Assignee: Christopher Collins
> Fix For: v1_0_0_beta1
>
>
> Compression should be supported in NFFS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-97) If a slave is applying slave latency on a connection and gets handed a packet it should send it ASAP

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-97:
--
Fix Version/s: v0_9_0_beta1

> If a slave is applying slave latency on a connection and gets handed a packet 
> it should send it ASAP
> 
>
> Key: MYNEWT-97
> URL: https://issues.apache.org/jira/browse/MYNEWT-97
> Project: Mynewt
>  Issue Type: Improvement
>Reporter: William San Filippo
>Assignee: William San Filippo
>Priority: Minor
>  Labels: controller
> Fix For: v0_9_0_beta1
>
>
> The current controller code applies slave latency even if there are packets 
> on its transmit queue. If there are packets on the controller queue, the host 
> has the MD (more data) bit set or, while applying slave latency, gets a 
> packet handed to that connection by the host, the controller should stop 
> using slave latency and wake up on the next connection event instead of 
> applying latency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-45) Command history for Shell

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-45:
--
Fix Version/s: v1_0_0_beta1

> Command history for Shell
> -
>
> Key: MYNEWT-45
> URL: https://issues.apache.org/jira/browse/MYNEWT-45
> Project: Mynewt
>  Issue Type: Improvement
>Reporter: Marko Kiiskila
>Priority: Minor
> Fix For: v1_0_0_beta1
>
>
> Few lines of command history behind arrow key would be nice.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-76) Add newt command to show a summary of licenses used in the stack

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-76:
--
Fix Version/s: v1_0_0_beta1

> Add newt command to show a summary of licenses used in the stack
> 
>
> Key: MYNEWT-76
> URL: https://issues.apache.org/jira/browse/MYNEWT-76
> Project: Mynewt
>  Issue Type: Improvement
>  Components: Newt
>Reporter: Aditi Hilbert
>Assignee: Sterling Hughes
>Priority: Minor
> Fix For: v1_0_0_beta1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-36) Implement FS encryption in NFFS

[Sterling Hughes (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sterling Hughes updated MYNEWT-36:
--
Fix Version/s: v1_0_0_beta1

> Implement FS encryption in NFFS
> ---
>
> Key: MYNEWT-36
> URL: https://issues.apache.org/jira/browse/MYNEWT-36
> Project: Mynewt
>  Issue Type: New Feature
>  Components: NFFS
>Reporter: Sterling Hughes
>Assignee: Christopher Collins
> Fix For: v1_0_0_beta1
>
>
> There should be an option to store data on a NFFS system in an encrypted 
> fashion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-122) Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info

[Justin Mclean (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151552#comment-15151552
 ] 

Justin Mclean commented on MYNEWT-122:
--

I've added the changes in SVN. Not sure how/when that page gets updated.

> Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
> --
>
> Key: MYNEWT-122
> URL: https://issues.apache.org/jira/browse/MYNEWT-122
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Image Mgmt
>Reporter: Aditi Hilbert
>Assignee: Justin Mclean
> Fix For: v0_8_0_beta2
>
>
> Justin, can you help us here since you are a PMC chair? We need to add the 
> link to the crypto code in our project on the following page: 
> http://www.apache.org/licenses/exports/
> The info is:
> Apache Mynewt Incubator Project
> Product Name: Apache Mynewt
> Version: development
> ECCN: 5D002
> Controlled Source: ASF
> Link: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-larva.git;a=tree;f=libs/mbedtls;hb=refs/heads/develop
> Once this is done, I can send the email notification to the US Govt.
> thanks!
> ---
> To satisfy the BIS requirements to make source code available for inspection, 
> while minimizing the number of notification emails needed to be sent, the ASF 
> maintains a single web page at http://www.apache.org/licenses/exports/ with 
> links to the applicable source code for each version of each ASF product 
> classified as ECCN 5D002.
> To make updates to this ASF-wide Exports page as simple and consistent as 
> possible, the source XML page contains a list of XML trees under eccnmatrix 
> that can be edited by anyone with site-dev karma (which includes all of the 
> PMC chairs). Note that the exports web page is generated from the XML.
> Any edits to the exports page should be tested using both the site build 
> process (view the index.html before committing any changes) and by running 
> the bisnotice.xsl transform on the product added/changed (see below). You can 
> probably figure out what the content of the XML fields should be by following 
> the example of other projects and reading the page. If you have any further 
> questions about the content, or if you are not sure that a BIS notice is 
> required, please check the FAQs first and then bring any remaining questions 
> to the legal-discuss mailing list. Note that the product data should only be 
> version-specific if the classification changes (e.g., Apache HTTP Server 
> version 1.3 vs 2.0) or if the link to the controlled source code needs to 
> change, such as if the encryption library included in the product for 
> different releases came from different manufacturers. In addition, note that 
> it is possible to include both controlled and non-controlled (ECCN "n/a") 
> products in the list, but a BIS notice is only necessary for the products 
> that have at least one version classified as 5D002.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-123) Send email to US govt. notifying our crypto code cryptography qualifies for the TSU exception

[Justin Mclean (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151545#comment-15151545
 ] 

Justin Mclean commented on MYNEWT-123:
--

MANUFACTURER(S) should be "ARM embed" not the ASF as be the FAQ here 
http://www.apache.org/dev/crypto.html#faq-manufacturer

> Send email to US govt. notifying our crypto code cryptography qualifies for 
> the TSU exception
> -
>
> Key: MYNEWT-123
> URL: https://issues.apache.org/jira/browse/MYNEWT-123
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Image Mgmt
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
> Fix For: v0_8_0_beta2
>
>
> Once the applicable source code is linked from the ASF-wide export page, we 
> have to send the following email to
> TO: cr...@bis.doc.gov
>e...@nsa.gov
>CC: d...@mynewt.incubator.apache.org 
>   legal-arch...@apache.org
> 
> SUBMISSION TYPE:  TSU
> SUBMITTED BY: {PMC member sending email}
> SUBMITTED FOR:Apache Software Foundation
> POINT OF CONTACT: Secretary, Apache Software Foundation
> FAX:  +1-919-573-9199
> MANUFACTURER(S)   "Apache Software Foundation.”
> PRODUCT NAME/MODEL #: Apache Mynewt Larva 
>   Code found at: 
> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git (currently 
> in branch named “develop” under  libs/mbedtls) 
> ECCN: 5D002
> NOTIFICATION: http://www.apache.org/licenses/exports/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-87) Implement channel map update LL control procedure

[William San Filippo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William San Filippo resolved MYNEWT-87.
---
Resolution: Fixed

Added code to perform the channel map update procedure. This also fixed a bug 
in the data channel index selection code when a channel was masked out.

> Implement channel map update LL control procedure
> -
>
> Key: MYNEWT-87
> URL: https://issues.apache.org/jira/browse/MYNEWT-87
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Nimble
>Affects Versions: v0_8_0_beta1
>Reporter: William San Filippo
>Assignee: William San Filippo
>Priority: Critical
>  Labels: controller
> Fix For: v0_8_0_beta2
>
>
> Many folks at the unplugfest noted that our controller did not support the 
> channel map update procedure. Most hosts/controllers attempt to perform this 
> procedure during a connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-80) Remove os_sem_delete and os_mutex delete as that functionality is not very useful

[William San Filippo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William San Filippo resolved MYNEWT-80.
---
Resolution: Fixed

Removed the API in question.

> Remove os_sem_delete and os_mutex delete as that functionality is not very 
> useful
> -
>
> Key: MYNEWT-80
> URL: https://issues.apache.org/jira/browse/MYNEWT-80
> Project: Mynewt
>  Issue Type: Improvement
>  Components: OS
>Affects Versions: v0_8_0_beta1
>Reporter: William San Filippo
>Assignee: William San Filippo
>Priority: Minor
> Fix For: v0_8_0_beta2
>
>
> We have decided that there is no need for os mutex or semaphore delete API. 
> Remove them. There are also issues with the current implementation of those 
> API so removing them will obviate those issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-119) Nimble stack crashing if PHY receives a PDU that is 257 bytes long.

[William San Filippo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William San Filippo resolved MYNEWT-119.

Resolution: Fixed

> Nimble stack crashing if PHY receives a PDU that is 257 bytes long.
> ---
>
> Key: MYNEWT-119
> URL: https://issues.apache.org/jira/browse/MYNEWT-119
> Project: Mynewt
>  Issue Type: Bug
>  Components: Nimble
>Affects Versions: v0_8_0_beta1
>Reporter: William San Filippo
>Assignee: William San Filippo
>Priority: Blocker
>  Labels: controller, mbuf
> Fix For: v0_8_0_beta2
>
>
> There is a bug in the code which will cause the device to crash if it 
> receives a mbuf that is too large. Unfortunately I dont have a debug output 
> of the crash but we could obtain one if we think it is necessary. Running the 
> un-fixed code in a noisy environment with lots of simultaneous connections 
> should reproduce it eventually.
> This problem was caused when we moved the controller code to use msys mbufs. 
> The buffer was not sized properly as the PHY still needs a flat buffer to 
> receive into and since the PHY currently uses mbufs, these mbufs need to 
> accommodate at least 257 bytes of data (they only had 256 bytes).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-122) Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info

[Justin Mclean (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151407#comment-15151407
 ] 

Justin Mclean commented on MYNEWT-122:
--

I'm not an PMC chair but see what I can do.

> Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
> --
>
> Key: MYNEWT-122
> URL: https://issues.apache.org/jira/browse/MYNEWT-122
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Image Mgmt
>Reporter: Aditi Hilbert
>Assignee: Justin Mclean
> Fix For: v0_8_0_beta2
>
>
> Justin, can you help us here since you are a PMC chair? We need to add the 
> link to the crypto code in our project on the following page: 
> http://www.apache.org/licenses/exports/
> The info is:
> Apache Mynewt Incubator Project
> Product Name: Apache Mynewt
> Version: development
> ECCN: 5D002
> Controlled Source: ASF
> Link: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-larva.git;a=tree;f=libs/mbedtls;hb=refs/heads/develop
> Once this is done, I can send the email notification to the US Govt.
> thanks!
> ---
> To satisfy the BIS requirements to make source code available for inspection, 
> while minimizing the number of notification emails needed to be sent, the ASF 
> maintains a single web page at http://www.apache.org/licenses/exports/ with 
> links to the applicable source code for each version of each ASF product 
> classified as ECCN 5D002.
> To make updates to this ASF-wide Exports page as simple and consistent as 
> possible, the source XML page contains a list of XML trees under eccnmatrix 
> that can be edited by anyone with site-dev karma (which includes all of the 
> PMC chairs). Note that the exports web page is generated from the XML.
> Any edits to the exports page should be tested using both the site build 
> process (view the index.html before committing any changes) and by running 
> the bisnotice.xsl transform on the product added/changed (see below). You can 
> probably figure out what the content of the XML fields should be by following 
> the example of other projects and reading the page. If you have any further 
> questions about the content, or if you are not sure that a BIS notice is 
> required, please check the FAQs first and then bring any remaining questions 
> to the legal-discuss mailing list. Note that the product data should only be 
> version-specific if the classification changes (e.g., Apache HTTP Server 
> version 1.3 vs 2.0) or if the link to the controlled source code needs to 
> change, such as if the encryption library included in the product for 
> different releases came from different manufacturers. In addition, note that 
> it is possible to include both controlled and non-controlled (ECCN "n/a") 
> products in the list, but a BIS notice is only necessary for the products 
> that have at least one version classified as 5D002.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MYNEWT-123) Send email to US govt. notifying our crypto code cryptography qualifies for the TSU exception

[Aditi Hilbert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aditi Hilbert updated MYNEWT-123:
-
Description: 

Once the applicable source code is linked from the ASF-wide export page, we 
have to send the following email to
TO: cr...@bis.doc.gov
   e...@nsa.gov
   CC: d...@mynewt.incubator.apache.org 
  legal-arch...@apache.org


SUBMISSION TYPE:  TSU

SUBMITTED BY: {PMC member sending email}

SUBMITTED FOR:Apache Software Foundation

POINT OF CONTACT: Secretary, Apache Software Foundation

FAX:  +1-919-573-9199

MANUFACTURER(S)   "Apache Software Foundation.”

PRODUCT NAME/MODEL #: Apache Mynewt Larva 

  Code found at: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git (currently 
in branch named “develop” under  libs/mbedtls) 

ECCN: 5D002

NOTIFICATION: http://www.apache.org/licenses/exports/



  was:
Once the applicable source code is linked from the ASF-wide export page, we 
have to send the following email to

SUBMISSION TYPE:  TSU

SUBMITTED BY: {PMC member sending email}

SUBMITTED FOR:Apache Software Foundation

POINT OF CONTACT: Secretary, Apache Software Foundation

FAX:  +1-919-573-9199

MANUFACTURER(S)   "Apache Software Foundation.”

PRODUCT NAME/MODEL #: Apache Mynewt Larva 

  Code found at: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git (currently 
in branch named “develop” under  libs/mbedtls) 

ECCN: 5D002

NOTIFICATION: http://www.apache.org/licenses/exports/




> Send email to US govt. notifying our crypto code cryptography qualifies for 
> the TSU exception
> -
>
> Key: MYNEWT-123
> URL: https://issues.apache.org/jira/browse/MYNEWT-123
> Project: Mynewt
>  Issue Type: Sub-task
>  Components: Image Mgmt
>Reporter: Aditi Hilbert
>Assignee: Aditi Hilbert
> Fix For: v0_8_0_beta2
>
>
> Once the applicable source code is linked from the ASF-wide export page, we 
> have to send the following email to
> TO: cr...@bis.doc.gov
>e...@nsa.gov
>CC: d...@mynewt.incubator.apache.org 
>   legal-arch...@apache.org
> 
> SUBMISSION TYPE:  TSU
> SUBMITTED BY: {PMC member sending email}
> SUBMITTED FOR:Apache Software Foundation
> POINT OF CONTACT: Secretary, Apache Software Foundation
> FAX:  +1-919-573-9199
> MANUFACTURER(S)   "Apache Software Foundation.”
> PRODUCT NAME/MODEL #: Apache Mynewt Larva 
>   Code found at: 
> https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git (currently 
> in branch named “develop” under  libs/mbedtls) 
> ECCN: 5D002
> NOTIFICATION: http://www.apache.org/licenses/exports/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-123) Send email to US govt. notifying our crypto code cryptography qualifies for the TSU exception

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-123:


 Summary: Send email to US govt. notifying our crypto code 
cryptography qualifies for the TSU exception
 Key: MYNEWT-123
 URL: https://issues.apache.org/jira/browse/MYNEWT-123
 Project: Mynewt
  Issue Type: Sub-task
Reporter: Aditi Hilbert
Assignee: Aditi Hilbert


Once the applicable source code is linked from the ASF-wide export page, we 
have to send the following email to

SUBMISSION TYPE:  TSU

SUBMITTED BY: {PMC member sending email}

SUBMITTED FOR:Apache Software Foundation

POINT OF CONTACT: Secretary, Apache Software Foundation

FAX:  +1-919-573-9199

MANUFACTURER(S)   "Apache Software Foundation.”

PRODUCT NAME/MODEL #: Apache Mynewt Larva 

  Code found at: 
https://git-wip-us.apache.org/repos/asf/incubator-mynewt-larva.git (currently 
in branch named “develop” under  libs/mbedtls) 

ECCN: 5D002

NOTIFICATION: http://www.apache.org/licenses/exports/





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (MYNEWT-122) Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info

[Aditi Hilbert (JIRA)]

Aditi Hilbert created MYNEWT-122:


 Summary: Update www.apache.org/licenses/exports/ with Apache 
Mynewt crypto info
 Key: MYNEWT-122
 URL: https://issues.apache.org/jira/browse/MYNEWT-122
 Project: Mynewt
  Issue Type: Sub-task
Reporter: Aditi Hilbert
Assignee: Justin Mclean


Justin, can you help us here since you are a PMC chair? We need to add the link 
to the crypto code in our project on the following page: 
http://www.apache.org/licenses/exports/

The info is:
Apache Mynewt Incubator Project
Product Name: Apache Mynewt
Version: development
ECCN: 5D002
Controlled Source: ASF
Link: 
https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-larva.git;a=tree;f=libs/mbedtls;hb=refs/heads/develop

Once this is done, I can send the email notification to the US Govt.

thanks!
---

To satisfy the BIS requirements to make source code available for inspection, 
while minimizing the number of notification emails needed to be sent, the ASF 
maintains a single web page at http://www.apache.org/licenses/exports/ with 
links to the applicable source code for each version of each ASF product 
classified as ECCN 5D002.

To make updates to this ASF-wide Exports page as simple and consistent as 
possible, the source XML page contains a list of XML trees under eccnmatrix 
that can be edited by anyone with site-dev karma (which includes all of the PMC 
chairs). Note that the exports web page is generated from the XML.

Any edits to the exports page should be tested using both the site build 
process (view the index.html before committing any changes) and by running the 
bisnotice.xsl transform on the product added/changed (see below). You can 
probably figure out what the content of the XML fields should be by following 
the example of other projects and reading the page. If you have any further 
questions about the content, or if you are not sure that a BIS notice is 
required, please check the FAQs first and then bring any remaining questions to 
the legal-discuss mailing list. Note that the product data should only be 
version-specific if the classification changes (e.g., Apache HTTP Server 
version 1.3 vs 2.0) or if the link to the controlled source code needs to 
change, such as if the encryption library included in the product for different 
releases came from different manufacturers. In addition, note that it is 
possible to include both controlled and non-controlled (ECCN "n/a") products in 
the list, but a BIS notice is only necessary for the products that have at 
least one version classified as 5D002.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-26) Revise Image Management Scheme

[Aditi Hilbert (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151195#comment-15151195
 ] 

Aditi Hilbert commented on MYNEWT-26:
-

So we need to add links to our code on the single exports page maintained by 
ASF:  http://www.apache.org/licenses/exports/.

Marko, you will also have to place the notice below in each distribution's 
README file:

` This distribution includes cryptographic software. The country in which you 
currently reside may have restrictions on the import, possession, use, and/or 
re-export to another country, of encryption software. BEFORE using any 
encryption software, please check your country's laws, regulations and policies 
concerning the import, possession, or use, and re-export of encryption 
software, to see if this is permitted. See  for more 
information.

The U.S. Government Department of Commerce, Bureau of Industry and Security 
(BIS), has classified this software as Export Commodity Control Number (ECCN) 
5D002.C.1, which includes information security software using or performing 
cryptographic functions with asymmetric algorithms. The form and manner of this 
Apache Software Foundation distribution makes it eligible for export under the 
License Exception ENC Technology Software Unrestricted (TSU) exception (see the 
BIS Export Administration Regulations, Section 740.13) for both object code and 
source code.

The following provides more details on the included cryptographic software: ... 
` 


> Revise Image Management Scheme
> --
>
> Key: MYNEWT-26
> URL: https://issues.apache.org/jira/browse/MYNEWT-26
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Image Mgmt
>Reporter: Sterling Hughes
>Assignee: Marko Kiiskila
> Fix For: v0_8_0_beta2
>
>
> We need the following in our image management and bootloader scheme: 
> - Image should contain a SHA-256 in it that uniquely identifies the image
> - Bootloader should support verifying the SHA-256 and the signature of the 
> image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (MYNEWT-26) Revise Image Management Scheme

[Justin Mclean (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYNEWT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151080#comment-15151080
 ] 

Justin Mclean commented on MYNEWT-26:
-

This may have an impact on the upcoming release due to US export controls - see 
http://www.apache.org/dev/crypto.html

> Revise Image Management Scheme
> --
>
> Key: MYNEWT-26
> URL: https://issues.apache.org/jira/browse/MYNEWT-26
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Image Mgmt
>Reporter: Sterling Hughes
>Assignee: Marko Kiiskila
> Fix For: v0_8_0_beta2
>
>
> We need the following in our image management and bootloader scheme: 
> - Image should contain a SHA-256 in it that uniquely identifies the image
> - Bootloader should support verifying the SHA-256 and the signature of the 
> image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (MYNEWT-26) Revise Image Management Scheme

[Marko Kiiskila (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYNEWT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marko Kiiskila resolved MYNEWT-26.
--
Resolution: Fixed

Brought in mbedTLS for crypto libraries. 

> Revise Image Management Scheme
> --
>
> Key: MYNEWT-26
> URL: https://issues.apache.org/jira/browse/MYNEWT-26
> Project: Mynewt
>  Issue Type: New Feature
>  Components: Image Mgmt
>Reporter: Sterling Hughes
>Assignee: Marko Kiiskila
> Fix For: v0_8_0_beta2
>
>
> We need the following in our image management and bootloader scheme: 
> - Image should contain a SHA-256 in it that uniquely identifies the image
> - Bootloader should support verifying the SHA-256 and the signature of the 
> image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)