text:
By E.G. Nadhan, HP
It is not the first time that I am blogging about the evolution of fundamental service orientation principles serving as an effective foundation for cloud computing. You may recall my earlier posts in The Open Group blog on Top 5 tell-tale signs of SOA evolving to the Cloud, followed by The Right Way to Transform to Cloud Computing, following up with my latest post on this topic about taking a lesson from history to integrate to the Cloud. I thought I had said it all and there was nothing more to blog about on this topic other than diving into more details.
Until I saw the post by Forbes blogger Joe McKendrick on Before There Was Cloud Computing, There was SOA. In this post, McKendrick introduces a new term – Service Technology – which resonates with me because it cements the concept of a service-oriented thinking that technically enables the realization of SOA within the enterprise followed by its sustained evolution to cloud computing. In fact, the 5th International SOA, Cloud and Service Technology Symposium is a conference centered around this concept.
Even if this is a natural evolution, we must still exercise caution that we don't fall prey to the same pitfalls of integration like the IT world did in the past. I elaborate further on this topic in my post on The Open Group blog: Take a lesson from History to Integrate to the Cloud.
I was intrigued by another comment in McKendrick's post about "Cloud being inherently service-oriented." Almost. I would slightly rephrase it to Cloud done right being inherently service-oriented. So, what do I mean by Cloud done right. Voila:The Right Way to Transform to Cloud Computing on The Open Group blog.
So, how about you? Where are you with your SOA strategy? Have you been selectively transforming to the Cloud? Do you have "Service Technology" in place within your enterprise?
I would like to know, and something tells me McKendrick will as well.
So, it would be an interesting exercise to see if the first Technical standard for Cloud Computing published by The Open Group should be extended to accommodate the concept of Service Technology. Perhaps, it is already an integral part of this standard in concept. Please let me know if you are interested. As the co-chair for this Open Group project, I am very interested in working with you on taking next steps.
A version of this blog post originally appeared on the Journey through Enterprise IT Services Blog.
HP Distinguished Technologist and Cloud Advisor, E.G.Nadhan has over 25 years of experience in the IT industry across the complete spectrum of selling, delivering and managing enterprise level solutions for HP customers. He is the founding co-chair for The Open Group SOCCI project and is also the founding co-chair for the Open Group Cloud Computing Governance project. Connect with Nadhan on: Twitter, Facebook, Linkedin and Journey Blog.

subset: commoncrawl


text:
Find New Or Used Freightliner CASCADIA 125 Trucks for Sale in Orlando, Florida, Narrow down your search by make, model, or category. CommercialTruckTrader.com always has the largest selection of New Or Used Commercial Trucks for sale anywhere.
Commercial Truck Trader Disclaimer: The information provided for each listing is supplied by the seller and/or other third parties. CommercialTruckTrader.com is not responsible for the accuracy of the information. Please refer to the Commercial Truck Trader Terms of Use for further information.


text:
What To Do If Your Garden Is Getting Brown From Heat
It seems like summer is finally here. Finally! I don't know about you, but I am ready, and this year, it feels like the weather isn't waiting. Much of the country is already experiencing extreme heat. It's a nice respite from the dark and the damp of winter, at least if you're a human.
But if you're a plant? Maybe not so much.
Like the good gardener that I am, I had my seedlings going way back in the earliest days of spring. Starts were in the ground as soon as the final frost had come and gone. My precious little plants, nurtured by my own hands, have been slowly and steadily soaking up sun and rain ever since. And through spring they thrived. You should see the height on my sunflowers!
But then, summer set in. We had a couple of scorcher days, and my poor plants begin to wilt. And we DIY home improvers in San Diego haven't even had it as bad as other parts of the country. I was chatting with a friend from Baton Rouge the other day, who sadly laughed as she told the story of her poor arugula, which fought so hard for three weeks in record temperatures before, as she said "The arugula was finally just like 'nope, I'm over it' and collapsed in a little pile of surrender."
If you're battling this same sunny demon in your own garden, I've got a few tips that just may help you keep your plants from withering away into lifeless straw. Don't give up before you give these a shot!
1. Pamper your pots. For potted plants like flowers or container-garden veggies, you'll need to give them extra care. They don't have the insulation of the earth around them, so they're even more prone to heat damage and desiccation. Always move your potted plants into the shade. You'll need to water them at least once every day, if not twice for the shade-loving species.
2. Water not only often, but deeply. For garden beds and in-ground plants, it's important that the water penetrate deep into the earth to encourage the roots to continue to extend down. It's cooler down there and the deeper the roots, the more likely your plant will survive extreme heat. So water often but more importantly, water for extended periods, to fully-saturate the soil.
3. Don't fertilize! In extreme heat, water is taken up very quickly by plants. This is great for thirsty plants, but it can be dangerous if you try to fertilize – which you may be tempted to do if your plants seem to be dying. Remember that fertilizer is also taken in very fast when it's hot, so plants are easily burned in this weather. Focus on water; save the fertilizer for after the heat wave passes.
4. Mulch is your BFF. Mulch will have your back, for reals. A thick layer (a few inches at least) of organic mulch over your garden will greatly reduce moisture loss, as well as help to regulate soil temperature. It's also an awesome stand-in for the fertilizer you'll be forgoing, and will help return some much-needed nutrients to the plants. So don't skip it – mulch is a life saver!
5. Try a little shade. You can build little tents or umbrellas (or better yet have a carpenter build a garden structure) to shade your tender greens and lettuces, which will help to delay bolting. They will bolt no matter what in extreme heat, but shade may give you a little more time to maximize your yield.
If you can implement all these tips, then you can probably save your garden from certain death in the summer sun. Now get out there and enjoy the heat!
Sayward Rebhal writes for Networx.com.
Looking for a Pro? Call us(866) 441-6648


text:
Security Center: Difference between revisions
No edit summary
No edit summary
|Line 6:
|Line 6:
Zimbra not affected by log4j vulnerability

Zimbra not affected by log4j vulnerability

After intensive review and testing, Zimbra Development determined that the 0-day exploit vulnerability for log4j (CVE-2021-44228) does not affect the current Supported Zimbra versions (9.0.0 & 8.8.15). Zimbra Collaboration Server currently uses log4j1 version 1.2.16 which doesn't contain the lookup expression feature that is found within versions 2.0 to 2.17, which is the cause of the vulnerability.
After intensive review and testing, Zimbra Development determined that the 0-day exploit vulnerability for log4j (CVE-2021-44228) does not affect the current Supported Zimbra versions (9.0.0 & 8.8.15). Zimbra Collaboration Server currently uses log4j1 version 1.2.16 which doesn't contain the lookup expression feature that is found within versions 2.0 to 2.17, which is the cause of the vulnerability.
CVE-2021-4104vulnerability does not affect the Zimbra Collaboration Server (8.8.15 & 9.0.0). For this vulnerability to affect the server, it needs JMSAppender the does not use
, the
to .

Revision as of 16:50, 24 January 2022
Zimbra Security - News & Alerts
Note: A security related FAQ and links to version specific security related settings can be found under Security/Collab.
Zimbra not affected by log4j vulnerability
After intensive review and testing, Zimbra Development determined that the 0-day exploit vulnerability for log4j (CVE-2021-44228) does not affect the current Supported Zimbra versions (9.0.0 & 8.8.15). Zimbra Collaboration Server currently uses log4j1 version 1.2.16 which doesn't contain the lookup expression feature that is found within versions 2.0 to 2.17, which is the cause of the vulnerability. Following are some more updates on the existing and newly reported vulnerabilities:
- CVE-2021-4104: This RedHat vulnerability does not affect the current Supported Zimbra Collaboration Server versions (8.8.15 & 9.0.0). For this vulnerability to affect the server, it needs JMSAppender and the ability to append configuration files. Zimbra does not use the JMSAppender.
- CVE-2022-23307: Zimbra is vulnerable but is not exploitable. To be exploited the system must be running Chainsaw. It is included but is never running.
- CVE-2022-23305: Zimbra is not vulnerable to this vulnerability, since it does not run the JDBCAppender.
- CVE-2022-23302: Zimbra is not vulnerable to this vulnerability, since it does not run the JMSSink.
ZCS 9.0.0 Patch 21 Released
ZCS 9.0.0 Patch 21 was released on November 22, 2021. The release includes security fixes for:
- Upgraded Apache to 2.4.51 to avoid multiple vulnerabilities. CVE-2021-30641 CVE-2020-35452.
ZCS 8.8.15 Patch 28 Released
ZCS 8.8.15 Patch 28 was released on November 22, 2021. The release includes security fixes for:
- Upgraded Apache to 2.4.51 to avoid multiple vulnerabilities. CVE-2021-30641 CVE-2020-35452.
ZCS 9.0.0 Patch 20 Released
ZCS 9.0.0 Patch 20 was released on October 25, 2021. The release includes security fixes for:
- Upgraded OpenSSL to 1.1.1l to avoid multiple vulnerabilities. CVE-2021-3711 CVE-2021-3712.
ZCS 8.8.15 Patch 27 Released
ZCS 8.8.15 Patch 27 was released on October 25, 2021. The release includes security fixes for:
- Upgraded OpenSSL to 1.1.1l to avoid multiple vulnerabilities. CVE-2021-3711 CVE-2021-3712.
ZCS 9.0.0 Patch 16 Released
ZCS 9.0.0 Patch 16 was released on July 28, 2021. The release includes security fixes for:
- Proxy Servlet Open Redirect Vulnerability CVE-2021-35209.
- Open Redirect Vulnerability in preauth servlet CVE-2021-34807
- Stored XSS Vulnerability in ZmMailMsgView.java CVE-2021-35208
- XSS vulnerability in Zimbra Web Client via loginErrorCode CVE-2021-35207
ZCS 9.0.0 Patch 10 Released
ZCS 9.0.0 Patch 10 was released on December 16, 2020. The release includes security fixes for:
- Resolved XXE vulnerability (CWE-776) in saml consumer store extension (Network Edition) CVE-2020-35123
ZCS 8.8.15 Patch 17 Released
ZCS 8.8.15 Patch 17 was released on December 16, 2020. The release includes security fixes for:
- Resolved XXE vulnerability (CWE-776) in saml consumer store extension (Network Edition) CVE-2020-35123
ZCS 9.0.0 Patch 5 Released
ZCS 9.0.0 Patch 5 was released on July 27, 2020. The release includes security fixes for:
- Upgrade for tinymce to 5.4.0, to resolve XSS vulnerability CVE-2019-1010091
- Upgrade nodejs library mem to 4.3.0 to resolve memory leak WS-2018-0236
ZCS 9.0.0 Patch 4 and ZCS 8.8.15 Patch 11 Released
ZCS 9.0.0 Patch 4 and ZCS 8.8.15 Patch 11 were released on July 2, 2020. The release includes security fixes for:
- XSS Vulnerability in CVE-2020-13653
ZCS 9.0.0 Patch 3 and ZCS 8.8.15 Patch 10 Released
ZCS 9.0.0 Patch 3 and ZCS 8.8.15 Patch 10 were released on June 3, 2020. The release includes security fixes for:
- Potential upload of dangerous file type in upload servlet CVE-2020-12846
ZCS 9.0.0 Patch 2 released
ZCS Patch 2 was released on May 4, 2020. The release includes security fixes for:
- CVE-2020-1931, XSS through malicious JS embedded in Mail Message or Calendar Event
ZCS 8.8.15 Patch 9 released
ZCS Patch 9 was released on April 23, 2020. The release includes security fixes for:
- CVE-2020-1930, CVE-2020-1931 - Upgraded 3rd Party Apache SpamAssassin from version 3.4.1 to 3.4.4.
- CVE-2020-3123 - Upgraded 3rd Party ClamAV from version 0.99.4 to 0.102.2.
- CVE-2019-13565 - Upgraded 3rd Party Open LDAP from version 2.4.46 to 2.4.49.
ZCS 8.8.15 Patch 8 released
ZCS Patch 8 was released on March 9, 2020. The release includes security fixes for:
- CVE-2020-10194 - any authenticated user could view a GAL contact from another domain on the same Zimbra installation. After this fix, AutoCompleteGal request does not allow access to GalSync accounts of other domains.
ZCS 8.8.15 Patch 7 released
ZCS Patch 7 was released on Feb 10, 2020. The release includes security fixes for:
- CVE-2020-8633 - Revoked share calendars are now being removed from OLK profile.
- CVE-2020-7796 - Potential for SSRF if WebEx zimlet installed and zimlet JSP enabled.
ZCS 8.8.15 Patch 2 released
ZCS Patch 2 was released on September 30, 2019. The release includes security fixes for:
- Upgraded ClamAV to 0.101.4 CVE-2019-12625 / Bug 12356
ZCS 8.8.15 Patch 1 released
ZCS 8.8.15 Patch 1 was released on August 28, 2019. The release includes security fixes for:
- CVE-2019-12427 / Bug 109174 - Non-Persistent XSS - admin console (CWE-79)
- CVE-2019-15313 / Bug 109141 - Non-Persistent XSS - web client (CWE-79)
ZCS 8.7.11 Patch 11, 8.8.9 Patch 10, 8.8.10 Patch 8, 8.8.11 Patch 4 and 8.8.12 Patch 1 released
ZCS 8.7.11 Patch 11, 8.8.9 Patch 10, 8.8.10 Patch 8 and 8.8.11 Patch 4 were released on April 15, 2019. The releases includes security fixes for:
- CVE-2019-9621 / Bug 109127 - SSRF (CWE-918 CWE-807)
- CVE-2019-6981 / Bug 109096 - SSRF (CWE-918)
8.8.9 Patch 10, adds one additional security fix (which is already included in earlier updates of the other releases mentioned above):
- CVE-2019-6980 / Bug 109097 - Insecure object deserialization (CWE-502)
ZCS 8.8.12 Patch 1 was also released on April 15, 2019. The fixes mentioned above were in the initial release for 8.8.12, but this patch adds one additional security fix:
- CVE-2019-11318 / Bug 109117 - Persistent XSS - Drive (CWE-79)
ZCS 8.8.12 released
ZCS 8.8.12 was released on April 1, 2019 . The release includes security fixes for:
- CVE-2019-9621 / Bug 109127 - SSRF (CWE-918 CWE-807)
- CVE-2019-6981 / Bug 109096 - SSRF (CWE-918)
- Upgrades to the following 3rd party packages were also included: Apache (2.4.38) and PHP (7.3.1)
Recent Zimbra XXE / SSRF Vulnerability Disclosures
We published a blog post regarding recent Zimbra XXE / SSRF vulnerabilities disclosed by An Phuoc Trinh, of Viettel Cyber Security. In short:
- ZCS 8.8 - upgrade to 8.8.10 Patch 7 or 8.8.11 Patch 3
- ZCS 8.7 (LTS) - upgrade to 8.7.11 Patch 10
- ZCS 8.6 (unsupported) - upgrade to 8.6.0 Patch 13
↳ Please plan to upgrade to a supported version as other security fixes have not been backported.
- ZCS earlier versions - upgrade to a supported version as soon as possible!
See the blog post for a few additional details: Recent Zimbra XXE / SSRF Vulnerability Disclosure.
ZCS 8.7.11 Patch 10 and 8.6.0 Patch 13 released
ZCS 8.7.11 Patch 10 was released on March 18, 2019 and 8.6.0 Patch 13 was released on March 19, 2019. The releases includes security fixes for (8.8.x versions are not affected by this vulnerability):
- CVE-2019-9670 / Bug 109129 - XXE (CWE-611)
ZCS 8.7.11 Patch 9, 8.8.10 Patch 7 and 8.8.11 Patch 3 released
ZCS 8.7.11 Patch 9, 8.8.10 Patch 7 and 8.8.11 Patch 3 were released on March 4, 2019. The releases includes security fixes for:
- CVE-2019-6980 / Bug 109097 - Insecure object deserialization (CWE-502)
A special thanks to An Phuoc Trinh, of Viettel Cyber Security, who has been going the extra mile to report his findings to us. His efforts are greatly appreciated!
Please note, the rating has been upgraded to "major" as the original scoring did not cover all potential available attack vectors.
ZCS 8.7.11 Patch 8 released
ZCS 8.7.11 Patch 8 was released February 1, 2019. The release includes security fixes for:
- CVE-2018-20160 / Bug 109093 - XXE - Chat (CWE-611)
- CVE-2018-14013 / Bug 109017 - Non-persistent XSS - Web Client (CWE 79)
ZCS 8.8.9 Patch 9, 8.8.10 Patch 5 and 8.8.11 Patch 1 released
ZCS 8.8.9 Patch 9, ZCS 8.8.10 Patch 5 and ZCS 8.8.11 Patch 1 were released January 4, 2019. The releases include security fixes for:
- CVE-2018-20160 / Bug 109093 - XXE - Chat (CWE-611)
- CVE-2018-14013 / Bug 109017 - Non-persistent XSS - Web Client
- Note: this fix is already in the ZCS 8.8.11 release
ZCS 8.8.11 released
ZCS 8.8.11 was released December 17, 2018. The release includes a fix for a non-persistent XSS CVE-2018-14013 / bug 109017 (CWE 79).
ZCS 8.8.9 Patch 7 released
ZCS 8.8.9 P7 was released November 6, 2018. The patch includes a fix for a persistent XSS CVE-2018-18631 / bug 109020 (CWE 79).
ZCS 8.8.10 Patch 2 and 8.7.11 Patch 7 released
ZCS 8.8.10 P2 and ZCS 8.7.11 P7 were released October 29, 2018. Both patches include a fix for a persistent XSS CVE-2018-18631 / bug 109020 (CWE 79). ZCS 8.7.11 P7 also includes a fix (already in ZCS 8.8.10 P1) for a non-persistent XSS CVE-2018-14013 / bug 109018 (CWE 79). Please note, there is a second non-persistent XSS (bug 109017), also part of CVE-2018-14013, which is not fixed in this patch set.
ZCS 8.8.10 Patch 1 and 8.8.9 Patch 6 released
ZCS 8.8.10 P1 and ZCS 8.8.9 P6 were released October 17, 2018. They include a fix for a non-persistent XSS CVE-2018-14013 / bug 109018 (CWE 79). Please note, there is a second non-persistent XSS (bug 109017), also part of CVE-2018-14013, which is not fixed in this patch set.
ZCS 8.8.10 released
ZCS 8.8.10 was released October 2, 2018. It includes a fix for a limited text content injection vulnerability CVE-2018-17938 / bug 109021 (CWE 345).
ZCS 8.8.8 Patch9 released
ZCS 8.8.8 Patch9 was released August 30, 2018. It includes a fix for an Account Enumeration vulnerability, CVE-2018-15131 / bug 109012.
ZCS 8.8.9 Patch3, 8.7.11 Patch6 and 8.6.0 Patch11 released
ZCS 8.8.9 Patch3 and ZCS 8.7.11 Patch6 were released August 17, 2018. They include a fix for an Account Enumeration vulnerability, CVE-2018-15131 / bug 109012.
ZCS 8.6.0 Patch11 was released August 17, 2018. This includes fixes for 11 vulnerabilities. See the release notes for details.
ZCS 8.8.8 Patch7 and ZCS 8.8.9 Patch1 released
ZCS 8.8.8 Patch7 and ZCS 8.8.9 Patch1 were released July 19, 2018. They include a fix for a Persistent XSS vulnerability, CVE-2018-14425 / bug 108970.
ZCS 8.8.8 Patch4 and ZCS 8.7.11 Patch4 released
ZCS 8.8.8 Patch4 and ZCS 8.7.11 Patch4 were released May 24, 2018. They include a fix for a XSS vulnerability, CVE-2018-10939 / bug 108902.
ZCS 8.8.8 Patch1 and ZCS 8.7.11 Patch2 released
ZCS 8.8.8 Patch1 and ZCS 8.7.11 Patch2 were released April 12, 2018. They include a fix for a CSRF vulnerability, CVE-2015-7610 / bug 97579.
ZCS 8.7.11 Patch1 released
ZCS 8.7.11 Patch1 was released March 14, 2018. This includes a fix for three XSS vulnerabilities, CVE-2017-17703 / bug 108265, CVE-2017-8802 / bug 107925, and CVE-2018-6882 / bug 108786.
ZCS 8.8.7 released
ZCS 8.8.7 was released today. It includes fixes for a Persistent XSS vulnerability, CVE-2018-6882 / bug 108768 and Mailsploit related issues / bug 108709.
Note: We recommend that all sites upgrading to 8.8.7 manually set zimbraPrefShortEmailAddress to FALSE which is the default for new 8.8.7 installs.
ZCS 8.6.0 Patch9 released
ZCS 8.6.0 Patch 9 was released today and includes fixes for two Persistent XSS vulnerabilities, CVE-2017-8802 / bug 107925 and CVE-2017-17703 / bug 108265.
If this patch is not applied, one potential workaround to avoid this issue is to set zimbraPrefUseKeyboardShortcuts to FALSE (for all users/classes-of-service). Note: disabling keyboard shortcuts would have the side effect of disabling all ZCS controlled keyboard shortcuts and this may impact normal user client interaction.
ZWC affected by Mailsploit
All supported versions of Zimbra Web Client (ZWC) prior to 8.8.7 are affected by Mailsploit. We recommend that all sites upgrading to 8.8.7 manually set zimbraPrefShortEmailAddress to FALSE which is the default for new 8.8.7 installs.
The workaround which addresses most issues is to set zimbraPrefShortEmailAddress to FALSE (if you are an administrator) for all users/classes-of-service. As an end user you can also control this setting by going to 'Preferences > Display names in place of email addresses when available' and deselecting the checkbox for this option (this is the end user control for the preference attribute mentioned above). This issue is being tracked as bug 108709.
8.7.10 Released with a fix for one vulnerability
The following vulnerabilities were fixed in ZCS 8.7.10:
- bug 107878 CVE-2017-8783 Persistent XSS - location CWE-79
Affects: All supported versions before 8.7.10
- bug 107885 CVE-2017-8783 Persistent XSS - description CWE-79
Affects: All supported versions before 8.7.10
Thank you to Stephan Kaag of Securify for reporting bug 107878!
8.7.6 Released with fixes for two vulnerabilities
The following vulnerabilities were fixed in ZCS 8.7.6:
- bug 107712 CVE-2017-6821 Improper limitation of file paths CWE-22
Affects: All supported versions before 8.7.6
- bug 107684 CVE-2017-6813 Improper handling of privileges CWE-280
Affects: ZCS 8.5.0 - 8.7.5
Limited XXE in ZCS < 8.7.4 (CVE-2016-9924)
A fix for a limited capability XXE - CVE-2016-9924 / bug 106811 is included in release ZCS 8.7.4. This issue affects all supported versions of ZCS before 8.7.4.
A special thanks to Alastair Gray for taking the time to report this issue!
Multiple CSRF in Administration interface in ZCS < 8.7 (CVE-2016-3403)
The details of CVE-2016-3403 / bug 100899 (see also bug 100885) were publicly disclosed by Sysdream Labs on 2017-01-11.
Please note the fixes for the flaws were included as part of ZCS 8.7.0, which was released on 2016-07-13.
Thank you to Sysdream for your assistance and cooperation!
Ransomware targeting ZCS Servers
Lawrence Abrams of Bleeping Computer has reported that there is a new ransomware variant, written in Python, that is targeting ZCS server data under /opt/zimbra/store/.
At this point, no details have been provided about how any servers were compromised. Without any details, the best advice we can give is:
- Get (and stay) up to date on OS version and patches.
- Get (and stay) up to date on ZCS version and patches.
- Ensure servers are properly firewalled (see Ports and only allow access to the minimum number of services that is required to meet your business requirements.
- Review and compare your system configuration against best practices like the CIS benchmarks.
Workaround: OpenSSL padding oracle in AES-NI CBC MAC check (CVE-2016-2107)
The 2016-05-03 announcement by OpenSSL regarding a padding oracle in the AES-NI CBC MAC check affects supported releases of ZCS 8.0-8.6.0 (via MTAs and Proxy).
We anticipate releasing 8.6.1 (and 8.7) with fixes for this issue, however if this issue is impacting your environment, the recommended workaround is covered in bug 104982. NOTE: in ZCS 8.7+ we are able to easily patch third party packages included with ZCS via package repos.
First, test that you are vulnerable with the following tool:
- Edit /opt/zimbra/.bash_profile
- add the following to the end of user zimbra's .bash_profile (requires root privs):
# workaround CVE-2016-2107
export OPENSSL_ia32cap="~0x200000200000000"
- Edit sudoers - add the following line to your sudoers (/etc/sudoers or whatever is appropriate for your platform):
Defaults env_keep += "OPENSSL_ia32cap"
- Configure postfix - instructs postfix to honor the desired environment variable:
$ zmlocalconfig -e postfix_import_environment='OPENSSL_ia32cap'
A special thanks to Malte Stretz from our Gold Partner, Silpion, for his persistence and hard work to gather the information covered in this workaround! Also this article would be incomplete without mentioning that the original inspiration for this workaround came from https://mjanja.ch/2013/11/disabling-aes-ni-on-linux-openssl/.
In Brief: DROWN / Cross-protocol attack on TLS using SSLv2 (CVE-2016-0800)
The 2016-03-01 announcement by OpenSSL regarding DROWN via SSLv2 affects ZCS 8.0.x (via MTAs), but no other currently supported releases. See How to disable SSLv3, as it includes instructions on disabling SSLv2 and SSLv3. Additional info may also be found in bug 104130.
ZCS 8.6.0 Patch 5 availability
ZCS 8.6.0 Patch 5 is available (officially released Dec 21, 2015). Patch 5 includes fixes for five (5) CVE's (ref: Zimbra Security Advisories). Three of the CVE-IDs referenced in the patch come via 3rd party components shipped w/ZCS. Please note, one of the fixed vulnerabilities is rated as major. See the blog post or the release notes (available from the downloads area for additional notes on ZCS 8.6.0 Patch 5.
[Update: Feb 2, 2016]
If you can not patch immediately, the XSS bug classified as major (bug 101435) can be worked around by either disabling or uninstalling (zmzimletctl undeploy) the com_zimbra_url (aka URL links) zimlet.
OpenSSL alternative chains certificate forgery (CVE-2015-1793)
Today's announcement by OpenSSL (https://www.openssl.org/news/secadv_20150709.txt) regarding alternative chains certificate forgery does not affect any Zimbra Collaboration releases.
Specifically, the latest Zimbra Collaboration 8.6 release ships with OpenSSL 1.0.1l, but this issue affects the following OpenSSL versions 1.0.2c, 1.0.2b, 1.0.1n and 1.0.1o only.
A note on Logjam
There is a lot of chatter about Logjam - https://weakdh.org today.
At this time, the initial impacts to Collab seem to be minimal and are currently limited to the MTA, specifically possible setting changes, depending upon your environment.
Today we updated the MTA Ciphers section of our Collab 8.6 security wiki page. In short, for anyone concerned about the Logjam (cipher downgrade) style of MitM attacks, the use of 'export' and 'low' ciphers in Postfix should be avoided. Please note that Postfix, by default (http://www.postfix.org/postconf.5.html#smtp_tls_ciphers) allows use of lower ciphers. Changing these to 'medium' can reduce client interoperability and/or may cause some clients to fall back to in the clear communication channels instead of using lower grade encryption.
As usual, there are trade-offs involved, but in the light of FREAK (https://freakattack.com) and Logjam (https://weakdh.org) attacks, it may also be argued that using ciphers lower than 'medium' is now potentially providing an illusion of security. With this in mind, our current recommendation is to avoid both 'export' and 'low' ciphers with the hope that complete deprecation of these ciphers will be coming soon.
Please visit https://wiki.zimbra.com/wiki/Security/Collab/86 to keep up with our latest recommendations. Also, for those looking to strengthen their security posture, in Collab 8.7 we have a number of enhancements slated including the ability to strengthen DH params. A sneak preview of security related changes/enhancements in the works is available at https://wiki.zimbra.com/wiki/Security/Collab/87.
Lastly, for those with openssl 1.0.2 available, you may find this post from OpenSSL useful https://www.openssl.org/blog/blog/2015/05/20/logjam-freak-upcoming-changes/
Update for 8.0.x customers: In Collab 8.0.x, Java 1.7 is used. Unfortunately, in Java 1.7, the DH parameters are hard-coded to 768 bits (excluding when using export cipher suites, which use 512 bits, but those should already be disabled). The workaround is to use the (Nginx) Proxy always. The other option is to disable all DHE suites. Which has the side effect of losing forward secrecy for any user agents that do not support ECDHE. (ref: http://blog.ivanristic.com/2014/03/ssl-tls-improvements-in-java-8.html
What the FREAK attack means to Zimbra
Zimbra is aware of a newly disclosed SSL/TLS vulnerability that provides a potential malicious actor with a method to perform a Man-in-the-Middle (MitM) attack the vulnerability is being referred to as FREAK (Factoring attack on RSA-EXPORT Keys), utilizing CVE-2015-0204.
The attack allows a malicious actor to force a downgrade of a secure connection to a vulnerable, export grade encryption (READ: weak encryption). Which, according to Washington Post, is downgraded to 512-bit encryption that was the maximum allowed under the export controls in place during the 1990s in the U.S. The Washington Post piece goes on to say it is possible to crack 512-bit encryption, today, in approximately 7 hours with the use of 75 computers, which can be rented from a cloud computing provider for approximately $100.
Matthew Green, cryptographer and research professor from Johns Hopkins, provided a Cliffs Notes version:
A group of cryptographers at INRIA, Microsoft Research and IMDEA have discovered some serious vulnerabilities in OpenSSL (e.g., Android) clients and Apple TLS/SSL clients (e.g., Safari) that allow a 'man in the middle attacker' to downgrade connections from 'strong' RSA to 'export-grade' RSA. These attacks are real and exploitable against a shocking number of websites -- including government websites. Patch soon and be careful.
In addition to Matthew Green's post and the Washington Post article, the freakattack.com site has additional information, including a list of the top domains still vulnerable, as well as a built in check of the browser used to surf to the site.
Zimbra Specifics
Zimbra ships with the OpenSSL library. At this time, Zimbra has assessed Zimbra Collaboration 8.x, 7.x and found no susceptibility to the FREAK attack in the servers. As there is a client side component to this attack, please verify that you are running the latest browsers/clients to lower the risk to this type of attack.
As part of our security program, Zimbra will continue to monitor all developments related to the FREAK vulnerability and update this post as needed.
GNU C Library Vulnerability — aka GHOST
Zimbra is aware of a Linux vulnerability, specifically the GNU C Library.
The vulnerability appears to have been found by Qualys and disclosed in security advisory CVE 2015-0235. It should be noted that the vulnerability was patched in v 2.17 of the library, but at the time was not categorized as a security issue, leading many to maintain stable versions, i.e. vulnerable versions. This is an operating system vulnerability; at this time, and to the best of our knowledge, there are no known exploits against Zimbra's software related to CVE 2015-0235.
Zimbra recommends that anyone running Linux update their systems as soon as possible. And while Linux doesn't usually require a restart, it is recommended to ensure all underlying software services are patched.
Patches or acknowledgements
GNU C Library's upstream Git
Red Hat
- Phil
Note: the original post was updated slightly to clarify the relationship between the vulnerability and the lack of known exploits against software shipped by Zimbra.
POODLE Revisited
We have received a few inquiries about the reported TLS protocol vulnerability via the POODLE attack. SSL/TLS services in ZCS come from OpenSSL and Java. This vulnerability does not affect OpenSSL (ref: http://email@example.com/msg75804.html) and Java is not known to be affected.
For anyone looking for more information, I recommend you look at https://www.imperialviolet.org/2014/12/08/poodleagain.html by Adam Langley.
Zimbra Collaboration Updates (8.0.9 & 8.5.1)
Zimbra Collaboration 8.0.9 and 8.5.1 are out with security updates, including the update to OpenSSL 1.0.1j. For those looking to disable SSLv3 remember to (re)visit https://wiki.zimbra.com/wiki/How_to_disable_SSLv3.
Find here extra details on the releases:
- https://community.zimbra.com/collaboration/f/1884/t/1136138
- https://community.zimbra.com/zblogs/b/teamblog/archive/2014/11/06/zimbra-collaboration-updates-8-0-9-amp-8-5-1
And, as always, don't forget to read the release notes.
The Shellshock Flaw
Zimbra is aware of, and has been closely monitoring, the developments of the Shellshock vulnerability. At this time, Zimbra has found no impact on our products, nor do we anticipate any. We have posted initial information on our main blog. Please head over to https://community.zimbra.com/zblogs/b/teamblog/archive/2014/09/25/the-shellshock-flaw for any updates related to this issue.
Security Advisory: Zimbra Community 8.x Security Vulnerability
Security is top of mind for everyone here at Zimbra, which is why we want to inform you that our team just discovered a security vulnerability in Zimbra Community 8.0 (formerly Telligent Community and Telligent Enterprise). The vulnerability is relegated to a very specific scenario in which a user within Zimbra Community 8.0 is able to view a user password via a specific API call.
Summary: The Zimbra development team has identified a very specific scenario where a user's password in Community 8 is stored insecurely.
Affected Versions: 220.127.116.11997 (unpatched), 220.127.116.11116
Vulnerability Scoring: CVSS: 1.4
Obtaining a fix: http://telligent.com/support/m/support/1354746.aspx
Details: The administrative feature to create users leverages non-public APIs that can force a user's password to be inadvertently stored insecurely.
Reporter: Alex Crome (Zimbra)
When does this occur?
1. Creating a user through the control panel using Membership Administration (requires administrative privileges)
2. Could occur if a custom plugin was deployed that copied off the extended attributes on a create user event and in turn re-saved those attributes using the UpdateUser API (this is unlikely, but possible)
If you have any questions or would like assistance with applying the patch, please contact support.
This advisory was originally published here.
Zimbra Security Advisory on CVE-2014-0224 (CCS Injection Vulnerability)
20140606: Zimbra Security Advisory on CVE-2014-0224 (CCS Injection Vulnerability)
On June 5, 2014 the OpenSSL project released a security advisory. CVE-2014-0224 can allow for a man-in-the-middle (MITM) attack to be carried out between a vulnerable client and vulnerable server. It is also important to note that Zimbra does not use DTLS nor do we have SSL_MODE_RELEASE_BUFFERS enabled.
The impact to Zimbra Collaboration Server is as follows:
- ZCS 6 is not affected
- ZCS 7 is not affected
- ZCS 8 is affected
Specifically, nginx, postfix and OpenLDAP all link to OpenSSL shipped in ZCS8. Other components in the ZCS package also link to the openssl libraries, but the above three are the potentially Internet-facing services that would be attackable. All versions of ZCS8 as released today are vulnerable. ZCS7 is not vulnerable because it uses OpenSSL 1.0.0, which is not vulnerable.
If you are running a version prior to 8.0.3, your server is susceptible to other critical security vulnerabilities (reference: https://www.zimbra.com/forums/announcements/68752-urgency-security-fixes-bug-80338-bug-84547-a.html). Please upgrade to a newer version first, then run this patch.
Zimbra has produced a patch for OpenSSL vulnerabily for versions 8.0.3 to 8.0.7. The patch downloads the correct and patched version of OpenSSL for the following versions and then installs the new package:
- ZCS versions 8.0.3, 8.0.4, 8.0.5, 8.0.6, or 8.0.7
- ZCA versions 8.0.3 or 8.0.4
The following patch instructions must be done on a per server basis:
- As zimbra user:
zmcontrol stop
- As root:
cd /tmp wget http://files.zimbra.com/downloads/security/zmopenssl-updater.sh chmod a+rx zmopenssl-updater.sh ./zmopenssl-updater.sh
- As zimbra user:
zmcontrol start
After a successful patch, ZCS 8.0.7 will be running 1.0.1h. To verify this, run the following as zimbra user:
openssl version
On an 8.0.7 patched system the result should be:
zimbra$ openssl version OpenSSL 1.0.1h 5 Jun 2014
Earlier versions of ZCS will show other versions of OpenSSL - Zimbra patches the existing OpenSSL version appropriate to each ZCS version.
Continue to the next server and repeat the patch process.
Internet access from each node is required to run this patch automatically. The patch should be installed on all ZCS nodes, most importantly the proxies, MTAs and LDAP nodes.
Also, please note: if you upgrade to a GA release after patching, you would need to re-patch. For example, if you install this patch on ZCS 8.0.6, then upgrade to ZCS 8.0.7, you would need to re-patch against 8.0.7.
Finally, please note that the various Operating Systems are also vulnerable to this issue. The Zimbra patch will not update OS-level openssl libraries. It only updates the openssl package in /opt/zimbra.
Critical Security Advisory and Builds/Patches for the OpenSSL Heartbleed Vulnerability
Zimbra Collaboration Server 8 is susceptible to the OpenSSL Heartbleed bug:
- http://heartbleed.com
- https://www.openssl.org/news/secadv_20140407.txt
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160
Specifically, nginx, postfix and OpenLDAP all link directly to OpenSSL shipped in ZCS8. Other components in the ZCS package also link to the openssl libraries, but the above three are the potentially Internet-facing services that would be attackable. All versions of ZCS8 as released today are vulnerable. ZCS7 is not vulnerable because it uses OpenSSL 1.0.0, which is not vulnerable. Only OpenSSL 1.0.1 and later are reported as being vulnerable.
Zimbra has produced an OpenSSL patch for versions 8.0.3 to 8.0.7. If you are running a version prior to 8.0.3, your server is susceptible to other critical security vulnerabilities (reference: https://www.zimbra.com/forums/announcements/68752-urgency-security-fixes-bug-80338-bug-84547-a.html), so you would please need to upgrade to a secure version first, then run this patch.
The patch is located here:
The patch downloads the correct and patched version of OpenSSL for the following versions and then installs the new package:
- ZCS versions 8.0.3, 8.0.4, 8.0.5, 8.0.6, or 8.0.7
- ZCA versions 8.0.3 or 8.0.4
Internet access from each node is required to run this patch automatically. The patch should be installed on all ZCS nodes, most importantly the proxies, MTAs and LDAP nodes.
Please note: this vulnerability is being reported as having existed and actively attacked since 2012. As such, the private SSL keys for your platform may already have been compromised. After patching, it is recommended to regenerate your SSL certificates and private keys. This is unfortunate, but the only way to ensure that an attacker cannot decrypt your SSL session data.
Also, please note: if you upgrade to a GA release after patching, you would need to re-patch. For example, if you install this patch on ZCS 8.0.6, then upgrade to ZCS 8.0.7, you would need to re-patch against 8.0.7.
Finally, please note that the various Operating Systems are also vulnerable to this issue if running OpenSSL 1.0.1. The Zimbra patch will not update OS-level openssl libraries - it only updates the openssl package in /opt/zimbra. For example:
- RHEL6_64 and UBUNTU12_64 both use OpenSSL 1.0.1 at the OS level and are affected
- SLES11_64 and UBUNTU10_64 use OpenSSL 0.9.8 at the OS level, so are not affected
The steps to patch are the following:
(as root)
1) wget http://files.zimbra.com/downloads/security/zmopenssl-updater.sh
2) chmod a+rx zmopenssl-updater.sh
3) ./zmopenssl-updater.sh
[Generates the following output]
Downloading patched openssl
Validating patched openssl: success
Backing up old openssl: complete
Installing patched openssl: complete
OpenSSL patch process complete.
Please restart Zimbra Collaboration Suite as the Zimbra user via zmcontrol
(as user zimbra)
4) su - zimbra
5) zmcontrol restart[/CODE]
Manual Patching
If you don't have Internet access, manually installing the patch would require the following steps:
1) Download the appropriate openssl build:
(as root)
cd /tmp
wget the correct version, from this list:
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/RHEL6_64/openssl-1.0.1d.tgz
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/SLES11_64/openssl-1.0.1d.tgz
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/UBUNTU10_64/openssl-1.0.1d.tgz
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/UBUNTU12_64/openssl-1.0.1d.tgz
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/RHEL6_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/SLES11_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/UBUNTU10_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/UBUNTU12_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/RHEL6_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/SLES11_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/UBUNTU10_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/UBUNTU12_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/RHEL6_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/SLES11_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/UBUNTU10_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/UBUNTU12_64/openssl-1.0.1e.tgz
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/RHEL6_64/openssl-1.0.1f.tgz
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/SLES11_64/openssl-1.0.1f.tgz
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/UBUNTU10_64/openssl-1.0.1f.tgz
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/UBUNTU12_64/openssl-1.0.1f.tgz
The MD5 files are also available for verification purposes, here:
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/RHEL6_64/openssl-1.0.1d.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/SLES11_64/openssl-1.0.1d.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/UBUNTU10_64/openssl-1.0.1d.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.3_GA/openssl/UBUNTU12_64/openssl-1.0.1d.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/RHEL6_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/SLES11_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/UBUNTU10_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.4_GA/openssl/UBUNTU12_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/RHEL6_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/SLES11_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/UBUNTU10_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.5_GA/openssl/UBUNTU12_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/RHEL6_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/SLES11_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/UBUNTU10_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.6_GA/openssl/UBUNTU12_64/openssl-1.0.1e.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/RHEL6_64/openssl-1.0.1f.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/SLES11_64/openssl-1.0.1f.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/UBUNTU10_64/openssl-1.0.1f.tgz.md5sum
- http://files.zimbra.com/downloads/8.0.7_GA/openssl/UBUNTU12_64/openssl-1.0.1f.tgz.md5sum
(as root)
2) cd /opt/zimbra
3) mv openssl-OLDVERSION openssl-OLDVERSION.brokenheart
4) tar xfz /tmp/openssl-NEWVERSION.tgz
(as user zimbra)
5) su - zimbra
6) zmcontrol restart
Zimbra Collaboration 8.0.7 Builds
Zimbra Collaboration Suite 8.0.7 - both the Network Edition and Open-Source Edition - have been rebuilt to include the fix for the OpenSSL Heartbleed Vulnerability.
If you haven't yet upgraded to 8.0.7, the current versions up on the Download site now disable TLS Heartbeat and protect against the OpenSSL Heartbleed Vulnerability:
- Network Edition: http://www.zimbra.com/products/download-network.html
- Open-Source Edition: http://www.zimbra.com/products/download-opensource.html
In short:
- If you downloaded ZCS 8.0.7 prior to Thursday, April 10, then your version DOES NOT include the OpenSSL fix. This would be ZCS 8.0.7 build 6020 -> Vulnerable, you would still need the OpenSSL patch: https://www.zimbra.com/forums/announcements/70921-critical-security-advisory-patch-openssl-heartbleed-vulnerability.html
- If you downloaded ZCS 8.0.7 Thursday, April 10 or after, then your version DOES include the OpenSSL fix. This would be ZCS 8.0.7 build 6021 -> Not Vulnerable, no patch required
OpenSSL Patch Update for ZCS 8.0.3 Only
If you patched for the OpenSSL Heartbleed vulnerability for Zimbra Collaboration Server 8.0.3 prior to Wed April 09, 2014, 11:00 Eastern/08:00 Pacific, you will need to re-patch.
Please note: this is ONLY for ZCS 8.0.3. All other patches were fine, but the 8.0.3 openssl builds were still vulnerable. Repeating, this is only for ZCS 8.0.3.
Here is how you can check your build version:
$ zmcontrol -v
(look for "8.0.3")
Please use the test methods below to confirm.
There are a few ways you can confirm if your system is vulnerable:
1. If running ZCS 8.0.7, check your version tarball for the build number 6021. For example:
- http://files2.zimbra.com/downloads/8.0.7_GA/zcs-NETWORK-8.0.7_GA_6021.RHEL6_64.20140408123937.tgz - the build number here is "6021"
2. If running ZCS 8.0.7, check zmcontrol for the build number:
# su - zimbra
$ zmcontrol -v
Release 8.0.7_GA_6021.RHEL6_64_20140408123937 RHEL6_64 NETWORK edition.
3. If running any version of Zimbra Collaboration, check if the libssl shared library is built with dlts1_heartbeat:
$ strings /opt/zimbra/openssl/lib/libssl.so | grep dtls1_heartbeat
Not Vulnerable:
$ strings /opt/zimbra/openssl/lib/libssl.so | grep dtls1_heartbeat
Please let Zimbra know promptly if any problems or questions.
Urgency on Security Fixes for Bug 80338 and Bug 84547
Bug 80338 (Feb 2013) is a Local File Inclusion vulnerability that leads to potential Privilege Escalation
- Bug 80338: Privilege Escalation via LFI
- CVE: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7091
- Affected versions: 7.2.2 and 8.0.2 and all previous releases
Bug 84547 is a XXE Vulnerability which, among other things, could be abused to disclose information from local files (Dec 2013):
- Bug 84547: XXE (CWE-611)
- CVE: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7217
- Affected Versions: releases before 7.2.6 in the 7 series, and 8.0.6 in the 8.0 series
There is great urgency for getting this patched on your platform, as there is an exploit for Bug 80338 in the wild, discussed here:
And it has been used to install upload rogue Zimlets and bitcoin mining processes (and potentially others) on some customer systems. You can read about the clean-up steps for this here:
As noted, there are patches and upgrades available here:
- http://info.zimbra.com/zimbra-news-new-patch-release-new-training-courses-and-upcoming-events
- Critical Security Patches posted for 8.0.X/7.2.X
- Critical Security Vulnerability Addressed in 7.2.6/8.0.6 Maintenance Releases
Please let us know if further questions. Please upgrade or patch at first opportunity. Sorry for the difficulties on this.
Welcome to the Zimbra Security Group
Join this group to get the latest news, updates and alerts about security issues affecting your Zimbra product.
Zimbra Security Center
Zimbra is committed to providing a secure collaboration experience for our customers, partners, and users of our software.
"Watch" the Security Center pages to stay updated on Zimbra security related news.
Zimbra Support
Open a new Support Ticket or check your opening ones. For questions on becoming a supported Zimbra customer, please contact us.
Zimbra Product Releases
Go to our Zimbra Product Releases page for details about each release, including:
- Release Notes
- Patch Information
- Documents in PDF format
- Documents in ePub format
- Complete Bugzilla reports


text:
The Lyman Spitzer Building, the main administration building at the U.S. Department of Energy\'s Princeton Plasma Physics Laboratory (PPPL), has been certified LEED gold, one of the highest environmental distinctions for buildings.
\"We are delighted to receive this designation for the Lyman Spitzer Building — or LSB — from the U.S. Green Building Council,\" said Adam Cohen, PPPL\'s deputy director for operations. \"We spent nearly three years transforming the LSB, which serves as our main office building, into a \'greener\' and more energy-efficient structure.\"
LEED, which stands for Leadership in Energy and Environmental Design, is the most widely recognized, high-performance green building certification program in the nation.
The LSB, constructed in 1981, achieved gold — the second highest level of certification — under the LEED Existing Buildings: Operations and Maintenance standard. The success makes the building the third within the U.S. Department of Energy to achieve gold certification and the largest to do so. The LSB is named after PPPL\'s founder, Lyman Spitzer Jr., a leading theoretical astrophysicist who was a pioneer in magnetic fusion energy research and conceived a large-scale observatory that became the Hubble Space Telescope.
Improvements and existing \"best practices\" culminated in making the LSB more environmentally friendly and ultimately led to the LEED designation, said Keith Rule, environmental projects head at PPPL. LEED for existing buildings addresses cleaning and maintenance issues — including chemical use — recycling programs, exterior maintenance programs and systems upgrades, according to the U.S. Green Building Council.
Rule, who led the LEED project, said many improvements to the heating, ventilating and air-conditioning systems for the past decade, as well as to lighting and building automation systems, have resulted in better energy efficiency performance for the LSB.
These improvements included the installation of LED exterior lighting to pathways and entrances, low-flow and sensor water fixtures, and enhanced ventilation systems and controls. LED lighting refers to light-emitting diode lighting that is more energy efficient. Best practices in place include the 100 percent bio-based cleaning program, 100 percent green office renovations, LED lighting improvements, sustainable landscaping practices and overall building efficiency measures. Best practices are processes and techniques that improve an organization\'s performance and, in this case, refer to methods to heighten energy efficiency.
The age of the LSB increased the challenge. \"It is definitely more difficult to get LEED certification for an older building,\" Rule said. \"Our main concern was energy efficiency.\"
The LSB is among more than 40,000 projects currently participating in the commercial and institutional LEED rating systems, involving more than 7.9 billion square feet of construction space in all 50 states and 117 countries.
According to the U.S. Green Building Council, buildings in the United States are responsible for 39 percent of carbon dioxide emissions, 40 percent of energy consumption, 13 percent of water consumption and 15 percent of GDP per year, making green building a source of significant economic and environmental opportunity. The U.S. Green Building Council asserts that greater building efficiency can meet 85 percent of future U.S. demand for energy, and a national commitment to green building has the potential to generate 2.5 million American jobs.
\"Building operations are nearly 40 percent of the solution to the global climate change challenge,\" said Rick Fedrizzi, president, CEO and founding chair of the U.S. Green Building Council. \"While climate change is a global problem, innovative companies and institutions like PPPL are addressing it through local solutions.\"
PPPL\'s Rule said the gold award is a testament to not only the LEED team at the laboratory, but also to every PPPL employee who supports green building practices and \"being green.\" \"When people carpool, recycle, save water and electricity, or buy a green product, they are contributing toward a green building and a green laboratory,\" he said.
The laboratory, located in Plainsboro, N.J., is funded by the U.S. Department of Energy\'s Office of Science and managed by Princeton University. Laboratory researchers collaborate with others across the globe to develop fusion as an energy source for the world, and conduct research along the broad frontier of plasma science and technology. PPPL also nurtures the national research enterprise in these fields, and educates the next generation of plasma and fusion scientists. Fusion is the process that powers the sun and other stars. In the interior of stars, matter is converted into energy by the fusion, or joining, of the nuclei of light atoms to form heavier elements.
The U.S. Green Building Council is a nonprofit membership organization whose vision is a sustainable built environment within a generation. Its membership includes corporations, builders, universities, government agencies and other nonprofit organizations.


text:
Your tree is 86.5% complete at the moment...
Did you ever wonder how soon you will get your golden owl if you keep learning at your current pace?
You are making 11.50 lessons per day on average and you still have to finish 139 lessons to finally get your shiny English golden owl, you would be there by 2023-10-15 if you keep doing L1 lessons at this pace.
Please, keep in mind that 41.69% of your lessons were some extra activity like stories or timed practice sessions and while these don't take you any closer to your golden owl, they actually give you some more experience.
It's a good thing... )
Keep going! =)


text:
Contura Switch Mounting Panels
3 Position Mounting Panel
- Modular design permits easy assembly in groups of varying sizes
- Designed for mounting in 6 different panel thicknesses:
0.06" (1.57mm) 0.09" (2.36mm) 0.13" (3.17mm)
0.19" (4.75mm) 0.25" (6.35mm) 0.38" (9.52mm)
WARNING: This product can expose you to chemicals including di(2-ethylhexyl)phthalate (dehp) which is known to the State of California to cause cancer, birth defects or other reproductive harm. For more information go to P65Warnings.ca.gov.
Blue Sea 8259 Contura 3 Position Mounting Panel
The vast majority of our products come from the United States, which explains our delivery times consequently between 1 and 4 weeks. It is possible to receive your parcels in express (7 working days) for some products, you will find all the information on the delays and on the costs according to each product on the product page.
1. Costs and shipping options Shipping costs vary according to the country of the recipient. Our products are shipped from the USA to France, and we dispatch all our orders from France. The final dispatch shipping costs will be displayed during the purchase of your order (before payment) according to each country and the delivery options chosen.
2. Delivery time Most of our products come from the USA. Therefore, we have a preparation time of 1 to 2 weeks to receive the goods at our French office at 7 rue Alaric II 31000 Toulouse for final shipment. It takes 1 to 3 weeks from the order date to the delivery date. It is possible to receive your parcels in accelerated shipment for certain products in stock at our French office. You will be able to see the exact delivery times, shipping costs, and whether the product(s) you have chosen is (are) eligible for express shipping when you place your order. This may vary depending on your delivery address.
We have a 30-day return policy, which means you have 30 days after receiving your item to request a return.
To be eligible for a return, your item must be in the same condition that you received it, unworn or unused, with tags, and in its original packaging. You'll also need the receipt or proof of purchase.
To start a return, you can contact us at firstname.lastname@example.com If your return is accepted, we'll send you a return shipping label, as well as instructions on how and where to send your package. Items sent back to us without first requesting a return will not be accepted.
You can always contact us for any return question at email@example.com.
Damages and issues
Please inspect your order upon reception and contact us if the item is defective, damaged or if you receive the wrong item, so that we can evaluate the issue and make it right.
We will notify you once we've received and inspected your return, and let you know if the refund was approved or not. If approved, you'll be automatically refunded on your original payment method. Please remember it can take some time for your bank or credit card company to process and post the refund too.
Return procedure
When you contact us to request a return, we will send you a prepaid return label with which you can return your package. This will be a label from your local post office or DHL depending on your location. You then just have to follow the procedure that will be indicated to you. Once we receive your return, we will send you your refund using the same method as your payment, or we will send a new product depending on your request.


text:
These are Republicans who think that the key to winning elections is to do more of what the Democrats are doing. In effect, they say "me too" on issues such as immigration, in hopes of gaining more new votes than they lose by betraying their existing supporters.
In the wake of last year's presidential election debacle for the Republicans, the explanation preferred by "moderate" Republicans has been that the GOP has been too narrowly ideological, and needs to reach out to minorities, women and young people, rather than just to conservatives.
In the words of the "Growth and Opportunity Project," the problem is that conservative Republican candidates have been "driving around in circles on an ideological cul-de-sac."
But the report itself says that the Republicans' election problems have been at the national level, not at the state level, where a majority of the governors are Republicans. Are the Republican moderates suggesting that the reason Mitt Romney lost in 2012 is that he was driving around in a conservative cul-de-sac? Romney was as mushy a moderate as Senator John McCain was before him -- and as many other Republican losers in presidential elections have been, going all the way back to the 1940s. The only Republican candidate who might fit the charge of being a complete conservative was Ronald Reagan, who won two landslide elections.
The report to the Republican National Committee is on firmer ground when it says that national Republican candidates have not articulated their case very well -- that "we too often sound like bookkeepers." Republican candidates "need to do a better job talking in normal, people-oriented terms."
Absolutely. It doesn't matter how good your case is, if you don't bother to articulate it so that voters understand you.
The heart of the report, however, is the argument that Republicans need to reach out to minorities, women and young people. With Hispanics and blacks becoming a growing proportion of the American population -- and both groups voting overwhelmingly for Democrats -- the Republicans are obviously in big trouble in future elections if they don't do something.
But if they do what this report advocates, they could be in even bigger trouble. Here again, facts seem to mean nothing to those who wrote this report.
They propose going through such organizations as the NAACP to reach black voters, as if the NAACP owns blacks, in violation of the 13th Amendment. Not only is the NAACP virtually a wholly owned subsidiary of the Democratic Party, the kind of black voters that the Republicans have some hope of winning over are unlikely to be enthralled to the NAACP, and many of them may see through such race hustlers.
Or do all blacks look alike to those who wrote this report?
It is the same story with Hispanics and Asian Americans. The Republicans are supposed to go through these groups' "leaders" as well -- mostly leaders tied to the Democratic Party ideologically or otherwise. You might think that a Republican Party that talks about individualism would try to appeal to individuals.
Individuals whom the Republicans have some chance of winning over may well be a small minority within these groups. However, if the GOP can reduce the Democrats' 80 percent of these groups' votes to 70 percent, that can swing elections.
But a shotgun approach to minorities won't do it.
When it comes to minority votes, the Democratic Party is much like Eastman Kodak during the long period when it sold the vast majority of the film and cameras in the country. How did its competitors manage to drive Kodak into bankruptcy?
Not by saying "me too" while trying to imitate Kodak and trying to outdo Kodak with better film and better film cameras. They went digital instead. But that approach requires a lot more thought than apparently went into this report. Polls and focus groups are not a substitute for thought.


text:
Usually, it is really simple to get a rental car by complying with the following:
The most affordable car in
IIf you are thinking about how to save some money, select the pick-up time alike drop-off time. Every car rental service takes money for a full day of rental, so when you take a vehicle for 25 hours, you have to pay for 48 hours (2 full days) of rental, and 74 hours will cost you as 96 hours (4 full days).
Subscription successful! Thank you!


text:
Difference between revisions of "BeagleBone Community"
Linuxfanrld (talk | contribs)
(→Expansion Boards and Accessories)
Linuxfanrld (talk | contribs)
(→USB 2.0 Powered Hubs)
|Line 92:
|Line 92:
= USB 2.0 Powered Hubs =
= USB 2.0 Powered Hubs =
USB 2.0 Powered Hub connects USB devices Keyboard , Mouse ,etc to the Single USB Host Port on the BBB Device. The Advantage Powered USB Hub VS USB Port is the Power .
* [http://www.belkin.com/us/F4U040-Belkin/p/P-F4U040/ Belkin USB 2.0 Powered Hub]
* [http://www.belkin.com/us/F4U040-Belkin/p/P-F4U040/ Belkin USB 2.0 Powered Hub]
|Line 98:
|Line 98:
:* 4 Port Powered USB 2.0 Hub
:* 4 Port Powered USB 2.0 Hub
:* Plug and Play
:* Plug and Play
:* Power Adaptor
Power Adaptor Made In China provides 5V 2.6A Power Supply
:* lsusb Info - ID 05e3:0608 Genesys Logic Inc. USB-2.0 4-Port Hub
:* lsusb Info - ID 05e3:0608 Genesys Logic Inc. USB-2.0 4-Port Hub
:* NO LED Indicator for Activity / Plugged In
:* NO LED Indicator for Activity / Plugged In
:* Packaging indicates Part # -
:* Packaging indicates Part # -
:* Packaging does not mention Linux compatibility OR Power
:* Packaging does not mention Linux compatibility OR Power the
:* Packaging indicates compatibility with Windows 7 & Mac OS 9.2 and Above
:* Packaging indicates compatibility with Windows 7 & Mac OS 9.2 and Above
= Expansion Boards and Accessories =
= Expansion Boards and Accessories =
Revision as of 03:55, 23 November 2013
This page collects information about BeagleBoard.org's range of BeagleBone boards based on the TI Sitara AM335x, an application processor SoC containing an ARM Cortex-A8 core. The range currently consists of the original BeagleBone and the upgraded but lower cost BeagleBone Black.
Most features are common to the two models. The differences between them are described in each section under a BeagleBone Black subheading.
- 1 Events
- 2 Description
- 3 Specifications
- 4 Expansion Connectors
- 5 USB 2.0 Powered Hubs
- 6 Expansion Boards and Accessories
- 7 BeagleBone Operating Systems
- 8 Board recovery
- 9 Software Development
- 10 Kernel
- 12 Links
- 13 Subpages
- ongoing 2009: Beagle Sponsored Project Program - add a cool project and get a free BeagleBoard to realize it!
The two models of BeagleBone share most features in common through employing only slightly different versions of the same TI Sitara SoC. In addition they both adhere to the same standard for expansion and interfacing through "cape" daughterboards.
BeagleBone (original)
The BeagleBone is a low-cost, high-expansion board from the BeagleBoard product line. It uses the TI AM3358/9 SoC based on an ARM Cortex-A8 processor core using the ARMv7-A architecture. It is similar in purpose to earlier BeagleBoards, and can be used either standalone or as a USB or Ethernet-connected expansion for a BeagleBoard or any other system. The BeagleBone is small even by BeagleBoard standards yet still provides much of the performance and capabilities of the larger BeagleBoards.
BeagleBone ships with a 4GB micro-SD card preloaded with the Angstrom ARM Linux distribution.
The board uses a TI TPS65217B PMIC to generate stable supply voltages regardless of input power variation. +5V DC power can be supplied to the BeagleBone through a barrel connector or from the mini-USB, both of which are located near the large RJ45 Ethernet connector.
The mini-USB type-A OTG/device client-mode socket is multi-functional. In addition to providing an alternative source of power, it gives access to an on-board front-end two-port USB client-side hub. (This is not related to the separate host-mode USB socket described later). One port of the hub goes directly to the USB0 port of the TI AM3358/9 SoC, while the other port connects to a dual-port FTDI FT2232H USB-to-serial converter to provide board-to-external-host serial communications and/or JTAG debugging. The BeagleBone's Linux serial console is available through this USB serial connection.
The SoC's USB0 connection to the front-end hub works in one of two modes, and you can toggle between them at any time: it either presents the SD card as a mountable USB storage device to the host, or it provides an Ethernet-over-USB networking interface which yields a simple method of quick-start. The Ethernet-over-USB facility is additional to the BeagleBone's normal 10/100 Ethernet interface, which is directly implemented in the SoC rather than hanging off USB as in some other designs. Full IPv4 and IPv6 networking is provided by the supplied Linux system out of the box.
In addition to the USB OTG Device or client-mode facilities already described, BeagleBone also provides one host-mode USB type-A socket on the other end of the board. This is driven from the USB1 connection on the AM3358/9 SoC, and provides access to USB host peripherals such as mice, keyboards, storage, and wifi or Bluetooth dongles, or a USB hub for further expansion.
BeagleBone Black
On 23rd April 2013, Beagleboard officially announced BeagleBone Black at a price approximately half that of the original BeagleBone.
The new board's most important new features include a AM3359 SoC upgraded to 1GHz, doubling of memory to 512MB, use of faster DDR3 memory in contrast to the DDR2 of the original BeagleBone, and a new HDMI audio/visual output. (The original BeagleBone required an additional cape daughterboard for graphic output).
The two boards are very similar in those features provided directly by the SoC. Despite the original BeagleBone being specified as using "AM3358/9", in practice most boards are believed to have shipped with the AM3359 generic part. BeagleBone Black has therefore upgraded only the specific device selected from the AM3359 range, and hence the differences are few. In contrast, the boards have significantly different designs but a high degree of compatibility.
- Up to 720 MHz superscalar ARM Cortex-A8 AM3358/9
- 10/100 Ethernet RJ45 socket, IPv4 and IPv6 networking
- MicroSD slot and 4GB microSD card supplied
- Preloaded with Angstrom ARM Linux Distribution
- Single USB 2.0 type A host port
- Dual USB hub on USB 2.0 type mini-A OTG device port
- On-board USB-to-serial/JTAG over one shared USB device port
- Storage-over-USB or Ethernet-over-USB on other USB device port
- Extensive I/O: 2 I2C, 5 UART, SPI, CAN, 66 GPIO, 8 PWM, 8 ADC
- +5V DC power from barrel connector or USB device port
- Power consumption of 300-500mA at 5V
- Two 46-pin 3.3-V peripheral headers with multiplexed LCD signals
- Board size: 3.4" × 2.1" (86.4mm x 53.3mm) -- fits in an Altoid tin
BeagleBone Black (differences)
- 1 GHz superscalar ARM Cortex-A8 AM3359
- On-board 2 GB eMMC flash, preloaded with Angstrom ARM Linux Distribution
- MicroSD slot for additional user data or operating systems (no card supplied)
- USB 2.0 type A host port
- Dedicated single mini-USB 2.0 client port (no additional 2-port hub)
- New micro-HDMI audio/visual output
- USB-to-serial and USB-to-JTAG interfaces removed (available on expansion headers)
- Power expansion header for backlight removed, battery charging moved onto pads
- Lower power consumption of 210-460 mA at 5V
Expansion Connectors
The BeagleBone provides two 46-pin dual-row expansion connectors "P9" and "P8" which are also known as "Expansion A" and "Expansion B", respectively. The location and pinout of these connectors is illustrated below (click tables to enlarge). All signals on expansion headers are 3.3V except where indicated otherwise.
P9 and P8 - Each 2x23 pins
In addition to the two large headers above, a small 10-pin dual-row connector "P6" provides a "PMIC Expansion" that brings out some additional signals from the TPS65217B Power Management IC, using the following pinout:
P6 - 2x5 pins
NB. P6 is not available on BeagleBone Black
This diagram of P6 provides an UNDERSIDE PINOUT view.
It is therefore laterally inverted relative to the photograph.
To obtain the top-side pinout that corresponds to the physical orientation shown in the photograph, swap the two rows of pins so that odd-numbered pins are on the left of even-numbered pins.
USB 2.0 Powered Hubs
USB 2.0 Powered Hub connects multiple USB devices i.e. Keyboard , Mouse ,etc to the Single USB Host Port on the BBB Device. The Advantage a Powered USB Hub provide VS USB Port is the Power draw available for device connected to the Hub.
- Expanded Hub Features
- 4 Port Powered USB 2.0 Hub
- Plug and Play
- includes Micro USB Cable
- Includes Power Adaptor which is Made In China and provides 5V 2.6A Power Supply
- lsusb Info - ID 05e3:0608 Genesys Logic Inc. USB-2.0 4-Port Hub
- NO LED Indicator for Activity / Plugged In Display
- Packaging indicates Part # - F4U040SA
- Packaging does not mention Linux Kernel compatibility OR Power in Amps provided by the Hub
- Packaging indicates compatibility with Windows 7 & Mac OS 9.2 and Above
Expansion Boards and Accessories
A BeagleBone Cape is an expansion board which can be plugged into the BeagleBone's two 46-pin dual-row Expansion Headers and which in turns provides similar headers onto which further capes can be stacked. Up to four capes at a time can be stacked on top of a BeagleBone. An expansion board which can be fitted only at the top of a stack of capes (usually for physical reasons) is a special case of "cape", but this usage is common for display expansion boards such as LCDs (see next section).
Capes are required to provide a 32Kbyte I2C-addressed EEPROM which holds board information such as board name, serial number and revision, although this is typically omitted on simple prototyping capes. Capes are also expected to provide a 2-position DIP switch to select their address in the stack, although this too is often omitted in prototyping capes.
The Capes Registry seeks to index all existing capes and cape concepts, including private projects. A registration page is available to help add capes to the list.
This section lists only those capes which are available commercially or which are close to a production release, as well as open hardware designs.
- CircuitCo BeagleBone DVI-D cape
- CircuitCo BeagleBone Breadboard cape
- CircuitCo BeagleBone Breakout cape
- CircuitCo BeagleBone CANBus cape
- CircuitCo BeagleBone RS232 cape
- CircuitCo BeagleBone Battery cape
- Adafruit Proto Cape kit for BeagleBone
- TowerTech TT3201 Multi-Channel CAN Cape
- Special Computing Spartan-3A FPGA cape for BeagleBone -- in development
- Thinking Machines LCD-IO Expansion Cape -- in development
- Open Source BeagleBone Prototyping Board -- piranha32 GitHub repository
- Embest BeagleBone HDMI cape
- BeagleBone 6502 RemoteProc cape -- in development
- Logic Supply LGX BeagleBone Proto Cape
These USB Wifi modules have been tested and validated to work with the BeagleBone Black:
- Logic Supply UWN100 Compact USB Wifi Module
- Logic Supply UWN200 Compact USB Wifi Module with Antenna
See here for how to use the I2S interface for audio.
Battery Power, Charging and Power Management
The BeagleBone Black has a built-in power management IC (PMIC) which generates and controls all of the voltage levels used by the board. The PMIC contains Li-Po / Li-Ion battery charging capability which means that it is extremely simple (and low cost) to enable portable use. There is also a built-in push-button on the BBB which can be used to soft power on/power off the board. See this link for information.
Intelligent Power Switch
The Pi Supply Switch v1.1 was originally designed for use as an automatic on off power supply switch for the Raspberry Pi which includes on, off and soft shutdown switches. The soft shutdown switch is fully programmable using software on the Pi to control the GPIO.
However the Pi Supply Switch v1.1 is also compatible with BeagleBone boards (both the classic and black) as well as the OLIMEX A13-OLINUXINO single board computer.
A very useful add on to help you manage power on your BeagleBone.
LCD Displays and Other Expansions
LCD displays for the BeagleBone are typically implemented as capes which plug in as the top board in a stack of capes, for reasons of visibility. Such displays are often larger than the BeagleBone itself, so the normal physical relationship in which a daughterboard is smaller than its host board is inverted. In this arrangement it is the expansion board that provides the physical support for the BeagleBone.
- NAXING Electronics BeadaFrame with BeagleBone companion board
- Expanded Hardware Features:
- 7" 800x480 TFT LCD screen
- PWM Backlight control
- Resistive touch panel
- Plastic frame
- 256MB Nand flash(K9F2G08)
- RS232 serial ports(UART1 w/ CTS&RTS)
- Stereo audio out
- Micro-phone in
- 6 x USER buttons
- PWM Beeper
- RTC with Battery(DS1302)
- 3.5" TFT LCD screen, resolution 320x240, 4-wire resistive touchscreen, seven buttons at finger-friendly positions.
- 4" TFT LCD screen, resolution 480x272, 4-wire resistive touchscreen, seven buttons at finger-friendly positions.
- 7" TFT LCD screen, resolution 800x480, 4-wire resistive touchscreen, rear mount for BeagleBone and capes.
- A very low cost LCD implementation for the BeagleBone Black using the PRU-ICSS is here. It requires a graphics library to be written; currently it just displays a couple of lines on the screen.
- ChipSee BBB-EXP-C BeagleBone Black 7 inch LCD cape and expansion I/O
- 7" LCD screen, resolution 1024*600, 5 point Capacitive touchscreen, 5 user keys, audio in/out, RS232/485/CAN, 3 axis accelerometer. Available at Logic Supply US and Logic Supply EU.
- Adafruit Bone Box - Enclosure for Beagle Bone
- An Altoids Tin - Beaglebone Black fits very nicely inside a regular sized Altoids tin
- SK Pang Acrylic Cover for BeagleBone
- Special Computing Bone Acrylic Case
- canadaduane's 3D-printable BeagleBone Case design
- NinjaBlock's 3D-printable Beaglebone front panel design
- builttospec's laser-cut design for BeagleBone Enclosure with DVI Cape
- Built to Spec BeagleBone Case Update, and final product
- Phenoptix (UK) BeagleBone Black clip-together enclosure
- BeagleBone Black Compact Metal Enclosure in Black - Logic Supply US Logic Supply EU. Open Source design available on GitHub
- BeagleBone Black Compact Metal Enclosure in Orange - Logic Supply US Logic Supply EU
BeagleBone Operating Systems
BeagleBone's default operating system is Angstrom, which ships with the board. This section provides basic information on Angstrom and other operating systems commonly used on BeagleBone. This information may help in making a preliminary choice, but full details should be obtained from the home sites.
The latest images of the official Angstrom images for BeagleBoard.org products can be found at the beagleboard.org latest images web page
- Home site: http://www.angstrom-distribution.org/
- Mailing lists: angstrom-distro-devel and angstrom-distro-users
- IRC channel: irc://irc.freenode.net/#angstrom
Ångström was started by a small group of people who worked on the OpenEmbedded, OpenZaurus and OpenSimpad projects to unify their effort to make a stable and user-friendly distribution for embedded devices like handhelds, set top boxes and network-attached storage devices. Ångström can scale down to devices with only 4MB of flash storage.
The Angstrom community does not provide a forum, intentionally.
Angstrom uses Busybox for many key utilities, which has both pros and cons. Advantages include requiring less storage space and a smaller memory footprint for many common utilities, which also improves system startup time and performance. The main disadvantages stem from those utilities not mirroring exactly their full-size counterparts. These differences can be annoying if one is used to standard behavior, and may also break shell scripts that rely on portable functionality.
Angstrom uses connman for network connection management, but no documentation is available for this currently. Also, man(1) and man pages are not provided by default, nor debugging utilities like strace(1) and tcpdump(1). Getting started may therefore present difficulties, depending on experience.
- See BeagleBoardDebian
- Home site: http://wiki.debian.org/ArmEabiPort
- Mailing list: http://lists.debian.org/debian-arm/
- IRC channel: irc://irc.debian.org/debian-arm
The ARM EABI port is the default port of the standard Debian distribution of Linux for the ARM architecture ("armel"). EABI ("Embedded ABI") is actually a family of ABIs, and one of the "subABIs" is the GNU EABI for Linux which is used for this port. Starting with Debian 7.0 (Wheezy) there is a port targeted at newer (armv7 with fpu) hardware with another ABI ("armhf").
The Debian Project is strongly committed to software freedom, and has a long pedigree and a good reputation.
- See ARMhf
The vision for Ubuntu is part social and part economic: free software, available free of charge to everybody on the same terms, and funded through a portfolio of services provided by Canonical.
The first version of Ubuntu was based on the GNOME desktop, but has since added a KDE edition, Kubuntu, and a server edition. All of the editions of Ubuntu share common infrastructure and software. In recent years, special emphasis has been placed on netbooks for lightweight, connected, mobile computing, and on the cloud as a new architecture for data centres.
- See BeagleBoardFedora.
- Home site: http://fedoraproject.org/wiki/Architectures/ARM
- Mailing list: http://lists.fedoraproject.org/pipermail/arm/
- IRC channel: irc://irc.freenode.net/#fedora-arm
The Fedora Project is sponsored by Red Hat, which invests in its infrastructure and resources to encourage collaboration and incubate innovative new technologies. Some of these technologies may later be integrated into Red Hat products. They are developed in Fedora and produced under a free and open source license from inception, so other free software communities and projects are free to study, adopt, and modify them.
Red Hat has been a major player since the earliest days of Linux distributions, and has earned a good reputation for solidity which continues in Fedora. The Fedora ARM initiative is very active (see mailing list).
- Home site: http://archlinuxarm.org/platforms/armv7/beaglebone
- Source repository: https://github.com/archlinuxarm/PKGBUILDs
- IRC channel: irc://irc.freenode.net/#archlinux-arm
Arch Linux for BeagleBone is a version of the Arch Linux ARM distribution. This carries forward the Arch Linux philosophy of simplicity and user-centrism, targeting and accommodating competent Linux users by giving them complete control and responsibility over the system. Instructions are provided to assist in navigating the nuances of installation on the varied ARM platforms; however, the system itself will offer little assistance to the user.
The entire distribution is on a rolling-release cycle that can be updated daily through small packages instead of huge updates on a defined release schedule. Most packages are unmodified from the code which upstream developers release.
- Home site: http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml
- IRC channel: irc://irc.freenode.net/#gentoo-embedded
Gentoo is a source-based meta-distribution of Linux. Instead of distributing a standard system image built with predefined options, Gentoo gives each user the means to create their own customized system that doesn't contain unused bloat and with minimum dependencies. Upgrades are incremental and under user control, so a Gentoo system is normally always up-to-date and wholesale upgrades are avoided.
Being a source-based system, the downside of Gentoo for low-power ARM systems is very long install times for large applications. Cross-compilation on x86 machines and distcc can overcome this problem, but they add complexity.
- Home site: wiki.sabayon.org/Hitchhikers Guide to the BeagleBone
- IRC channel: irc://irc.freenode.net/#sabayon
Sabayon Linux uses the mechanisms of Gentoo to create a pre-configured Linux distribution that can be installed as rapidly as a normal binary distribution, but still retains the benefits of Gentoo's source-based package management. Sabayon on Intel/AMD also provides the Entropy binary package management system, which could in principle greatly ease installation of packages on resource-constrained embedded Linux devices, but this is not yet available for ARM.
Although it is still early days for Sabayon on ARM (and hence on BeagleBone), there is regular progress reported on lxnay's blog, and contributions from the community would probably accelerate the work.
- Home site: http://www.zoobab.com/beaglebone
- Buildroot project site: http://buildroot.uclibc.org/
Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system. Buildroot can generate any or all of a cross-compilation toolchain, a root filesystem, a kernel image and a bootloader image. Buildroot is useful mainly for people working with small or embedded systems, using various CPU architectures (x86, ARM, MIPS, PowerPC, etc.) : it automates the building process of your embedded system and eases the cross-compilation process.
The resulting root filesystem is mounted read-only, but other filesystems can be mounted read/write for persistence. Although user accounts can be created, in practice almost everything is done as root. Buildroot uses no package manager. Instead, package selection is managed through make menuconfig.
Nerves Erlang/OTP
- Home site: http://nerves-project.org/
- Source repository: https://github.com/nerves-project/bbone-erlang-buildroot
- Erlang project site: http://www.erlang.org/
Erlang is a programming language used to build massively scalable soft realtime systems with high availability requirements (5-9's). Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.
OTP is a set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.
The Nerves project provides an embedded Linux-based environment for running Erlang and an easy-to-use API to access common I/O interfaces, based on Buildroot (see above). If you are interested in running an Erlang node on a low power ARM-based board such as BeagleBone, this project can get you started.
Board recovery
- See BeagleBoardRecovery --- (*) Check applicability
Software Development
Software development on the BeagleBone is normally no different to any other Linux platform, and typically varies with language and with the IDE used, if any. This section deals only with development issues that are specific to BeagleBone, or mostly so.
Cloud9 IDE and Bonescript
..... description here .....
- Source repository: https://github.com/jadonk/bonescript
- Language documentation: http://nodejs.org/
BeagleBone JTAG Debugging
..... description here .....
Using Netbeans to remotely compile and debug C/C++
When developing c/c++ on a linux desktop, a toolchain is available for cross-compiling the code for arm. However no such toolchain is readily available for windows. Netbeans can be used to write the code on your desktop, save it in a location accessible to the beagle, and then automatically compile it on the beagle itself using ssh and the built in compiler on the beaglebone's OS.
Netbeans can also use GDB for remote debugging over ssh.
- Set up a samba / smb network share through which code can be shared between both desktop and beagle
- Give netbeans the SSh login details of the beagle
- Give netbeans the path mapping so it can translate between the desktop code folder and beagle code folder
- Setup only takes a few minutes.
More info
- Download Netbeans (Windows/Linux/OS-X/Solaris): http://www.netbeans.org/
- Example tutorial on setting this up: http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans
Getting the Right Kernel
The modern BeagleBone kernels are Maintained by Koen Kooi and are available on the 3.8 branch at https://github.com/beagleboard/kernel/tree/3.8 . This repo contains a set of patches and a script which downloads a mainline kernel and then patches it appropriately. Exact steps for building it are in the README.
Step-by-step guide to building a BBB kernel
There is a step-by-step guide to building a BeagleBone Black (BBB) kernel at http://elinux.org/Building_BBB_Kernel
Device Tree
The 3.5 and newer BeagleBone kernels make use of Device Tree. A Device Tree is a text file which describes the layout of a machine, commonly the combination of a system-on-chip (SoC) and a board, so that the kernel can know at what addresses and on which buses hardware is located. The BeagleBone kernels make use of an extension called Capemgr which allows dynamic loading and unloading of device tree fragments both at compile time and from userspace post-boot. Learning about the Device Tree is very essential, if you wish to be able to manipulate pins and be able to use them as inputs/outputs. There is a short guide to it here (part-way down the page). In a nutshell, the device tree can be manipulated by creating a text 'fragment' file that can be converted into a .dtbo file using a program called dtc which is already installed on the BeagleBone Black. The .dtbo file can then be installed and uninstalled as desired. The procedures to install and uninstall are at that link:
echo cape-bone-name > $SLOTS to install, and
echo -<slotnum> > $SLOTS to uninstall, but read through the web page and comments section first to see what $SLOT is set to).
For BeagleBoard frequently asked questions (FAQ) see community FAQ and "official" BeagleBoard.org FAQ.
Home site and Community
- beagleboard.org -- home for BeagleBoard and BeagleBone products
- BeagleBone Black -- manufacturer's page for the second BeagleBone board
- irc://irc.freenode.net/#beagle -- official combined IRC channel
- Google Groups forums/mailing list -- English, Japan, Brasil, Turkey
- BeagleBoard and BeagleBone projects list
- Capes Registry and its registration page
- BeagleBone articles at Adafruit blog -- products, projects and tutorials
- Use Google to search beagleboard.org (including IRC logs) using site:beagleboard.org <search term>
- Linux.com report on BeagleBone Black -- with words from beagleBoard.org's cofounder Jason Kridner
- github.com/selsinork/beaglebone-black-pinmux -- pinmux data for BeagleBone Black, including extraction scripts
- Element 14 knode blog: Working with the PRU-ICSS -- detailed tutorial on starting with the PRU on BBB
- BBB, NEON and making Tintin bigger - introduction to using NEON on the BBB
- BeagleFu -- BeagleBone/Board Community, News and Projects.
Tutorials and Videos
- BeagleBone: BeagleBoard-101 Intro -- slides (turn off Javascript for single page)
- BeagleBone Intro, video by Jason Kridner, Texas Instruments
- How-To: Get Started with the BeagleBone, video by Matt Richardson, MakeMagazine
- The Beaglebone - Unboxing, Introduction Tutorial and First Example, video by Derek Molloy, DCU/EE
- Beaglebone: C/C++ Programming Introduction for ARM Embedded Linux Development using Eclipse, video by Derek Molloy, DCU/EE
- Beaglebone: GPIO Programming on ARM Embedded Linux, video by Derek Molloy, DCU/EE
- C code for GPIO polling, sample code by Andrew Montag
- First steps with the Beaglebone, introductory HOWTO by octavio at borderhack
- Adafruit Learning System - BeagleBone -- web page
Manuals and resources
- BeagleBone System Reference Manual (rev. A3_1.0)
- Texas Instruments - Sitara AM335x ARM Cortex-A8 Microprocessor overview
- Texas Instruments - AM3359 Sitara ARM Cortex-A8 Microprocessor full documentation
- ARM/ARMv7-AR Architecture -- ARM Cortex-A8 architecture overview
- ARM Cortex-A8 Technical Reference Manual r2p1
- ARM Cortex-A Development Platforms -- ARM page on Beagle boards
- TI TPS65217 Power Management IC, TPS65217 PMIC datasheet
- FTDI FT2232H Hi-Speed Dual USB UART/FIFO IC overview, FT2232H datasheet
- Linux-USB Gadget API Framework and USB OTG, and kernel config -- Ethernet-over-USB
- Beaglebone and the 3.8 Kernel Details about the 3.8 Kernel, its use of DT and the capemanager.
- SolidWorks 3D model of the BeagleBone Black on GitHub, includes 3D PDF.
- 한국어:KR:BeagleBone
http://elinux.org/BeagleBone_Usb_Networking http://elinux.org/BeagleBone_and_the_3.8_Kernel


text:
In the world of smartphones, nothing stands still for long – not even the look of the virtual buttons we swipe and press. In the last year, Samsung, HTC, BlackBerry, LG, Google, and Firefox have introduced brand new user interfaces. They've generated some buzz, but most critics focused more on new features than the aesthetics of the new menus and icons.
Yet the moment Apple changed things up with iOS 7 last week, all hell broke loose.
Everyone on the Internet has become a design expert, picking apart the OS on a granular level. From color schemes to gradients and the size of icons, no one seems content with Jony Ive's revamp of iOS. What the hell, guys? Did everyone lose the ability to see the big picture? I didn't realize that all tech journalists double majored in iconography.
Joshua Topolsky of The Verge kicked things off right after Apple debuted the new OS. He called it "simply confusing." Some of his more entertaining criticisms are of the Messages icon, which has a word balloon that is "so puffed up and oversized compared to its fine point that it looks like it will topple over." All the icons are a mess, he complains, specifically citing the "inconsistency" of the camera app from the lock screen to the home screen … though failing to acknowledge that the same inconsistency exists in iOS 6.
If I'm accusing Topolsky of being nitpicky, then I don't know what to say about Network World. Writer Yoni Heisler goes icon by icon, app by app through Apple's new OS, criticizing every single icon. The Newsstand icon looks "generic;" the Calculator icon is too flat; the Game Center icon isn't flat enough; the photos icon has colors that are "too muted." He's meanest to the poor Maps icon though:
"The iOS 6 icon, with a touch of gloss and 3D perspective, is aesthetically pleasing. Contrast that to the new Maps icon where Apple, yet again, went with a putrid shade of yellow and utterly lifeless shades of blue and green," writes Heisler.
For your reference, here are the two Map apps.
Does the icon on the bottom upset you? Does it make your blood boil? If it does, please get a hobby. No one outside of Apple should have the time or energy to get upset about the design differences between these icons. At least Cult of Mac has a sense of humor about the change.
Gizmodo is getting in on the nitpicking game, too. In "What's Wrong With the iOS 7 Icons," writer Ian Storm Taylor (who actually is a designer) picks apart Apple's icons one by one, explaining precisely why he hates them. His criticisms go beyond mere ranting, but his suggestions, like the Squarespace icon below, look worse to my eyes. Maybe you have to be a designer to appreciate them?
Throughout the article, Taylor criticizes Apple for continuing to rely on skeumorphism and failing to deliver a "consistent" set of app icons. He microexamines each icon, going so far as to demand the removal of a yellow dot on the camera icon. Seriously?
TechCrunch posted a Dribble.com artist's interpretation of what he wished the iOS 7 app icons looked like, which illustrates the triviality of all this. If you can't tell, his is on the left. Is this much of a change what we're upset about? He removed a few details and made logos smaller. That's it.
Does anyone honestly think that a normal person is going to walk into a store and choose an Android phone because the icons of iOS don't seem cohesive enough? No, they are not.
Even people who do hate Apple's new icons shouldn't care because most of us don't even use them. We use other apps – dozens of them. It's impossible to keep iOS icons consistent unless Apple VP of Design Jony Ive plans to redesign a million App Store icons. Apple can rejigger all of its dozen or so icons, but after that, the look and feel of the iOS home screen is out of its control. There are more than 900,000 other apps in the App Store and few of them have icons that will "cohesively" fit with whatever work of art we want to pretend iOS 7 should be.
We can rip apart the icons and design decisions of iOS 7 all we want, but does anyone believe that iOS 6 is a monument to visual design? Its glossy menus look like they're straight out of 2001 (because they are) and it's full of weird oddities.
It's impossible to keep iOS icons consistent unless Apple VP of Design Jony Ive plans to redesign a million App Store icons.
But hey, none of this matters. If iOS 7 looks unfinished that's because it is unfinished. This is a beta. The final design will likely look different.
And even if this is iOS 7, it looks pretty good. No one is going to care about the iconography. iOS 7 looks fresh and different from the last six years of iPhones. That matters. When people go into a store to buy a new phone, iOS 7 will surprise them. That matters. When regular people compare the next iPhone to the Galaxy S4 or HTC One, it will look just as new. DT readers, you probably already know what phone you will buy next. But we're not the majority. Most people buy what seems best when they get to the phone store.
I enjoy over-discussing meaningless tech topics in excruciating detail as much as the next guy, but the skeptics dissected every nuanced "mistake" in iOS 7 need to give it a rest. The success of the next iPhone will have absolutely nothing to do with the colors or gradient style of the default icons on its home screen. There are plenty of things that I hope Apple fixes by the time iOS 7 rolls out in September or October, but I'm not going to spend the summer yelling at Jony Ive because he had the guts to mix things up
iOS has never been a holy grail for user interface style and icon design. Let's not pretend it is.
Editors' Recommendations
- How to use StandBy in iOS 17 to turn your iPhone into a smart display
- How to download iPadOS 17 on your iPad
- I've been using iOS 17 for months. These 4 new things are the best
- How to reset your iPhone, restart it, and wipe it clean
- How to use iOS 16 photo cutout to cut and paste images


text:
Request a Quote
If you have already spoken to your officiant and know they are available for your wedding, please search for them by name on the Wedding Officiants page and click the button under the photo on their profile to request them.
If you would like to see who is available for your date, time and location, please fill in the form below.
You can review our wedding packages here.
Requested Officiant: Danielle Ingster
- Wedding Details
- Confirmation
- Complete


text:
Glass – Blue murrine glass
Shape – Rounded triangle
Measurement (HxW) – 7/8" x 1/2"
Chain - 24" silver plated
Small Blue Murrine Glass Necklace
Tech Specifics
All Glass items are unique. There can be slight variation of color, shapes, and measurements as depicted in the photos.
Custom Orders
All in-store items can be custom ordered. Please give us a minimum of 3 weeks notice. Contact us at email@example.com
Return Policy and Liabilities
Due to the personal nature of the glass art items, they cannot be returned, however, if any part of the non-glass jewelry item breaks from natural wear, kindly return it to us within 90 days and we will repair. We just ask that you pay postage for the return. We recommend using a bubble envelope mailer.
All glass items can break and we are not liable for any breakage or harm from breakage.


text:
Book apartments in Cave City
Find your home-away-from-home when you book your next stay at an apartment in Cave City. Apartments are ideal for families, groups of friends and even solo travelers. More space, more options and more freedom—apartments are short-term digs that feel like a long-term arrangement. From one-bedroom apartments to three bedrooms or more, Orbitz has an incredible selection to choose from. It's never been easier to live like a local in Cave City.
Apartments for everyone in Cave City
Family apartments in Cave City have plenty of room for everyone. You'll find multiple bedrooms, laundry facilities and furnished living rooms, so you can have movie nights just like at home. Plus, hotels with kitchens cut down on time spent finding kid-friendly restaurants. Spend that time making memories instead.
Friends are the family you choose, but you don't need to be too close this vacation. Luckily, you can book apartments even your pickiest pal will love. This getaway with the girls or guys doesn't have to break the bank, either. Cheap apartments in Cave City are just a click away. When it comes time to split the bill, no one will bail.
If you want the finer things in life, we'll help you find luxury apartments in Cave City faster than you can say "thousand thread count sheets." Get your best sleep ever, then wake up with a freshly brewed espresso and a full breakfast. It's just like home, only much, much better.
Whether you're a bargain hunter or a luxury lover, kitchens and kitchenettes are one of the most important features of short-term apartments in Cave City. It's simple, really: Cooking your own meals is downright convenient. Even if you're not a five-star chef, late-night snacks and morning mimosas get a whole lot easier when you've got a fully stocked kitchen to play with.
|13 Apartments
Lowest Price
Highest Price
Popular accommodation
|DowntownBrowntown, Apartment with Shared Amenities on 50 Acres, Rustic Retreat: Treestand+1, Pet-Friendly Brownsville Retreat w/ Porch!, Brownsville Studio Cottage - Walk to Mammoth Cave!, Apartment With Shared Amenities on 50 Acres, Wanderlust: Here for your outdoor adventure, Brownsville Vacation Rental Near National Park!, Brownsville Vacation Rental Near National Park!