Apache Karaf update June 30 - July 6, 2013

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.12, 2.3.2, 2.4.0, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.12:

New Issues:
N/A

Updated Issues:
Karaf-2191 Karaf 3.0.x CLONE - Karaf startup fails with NullPointerException when logfile can't be written
Karaf-2299 WARN message should be logged when a boot feature installation fails
Karaf-969 Feature installer should not accept different features with equal names
Karaf-1560 config:update throws ClassCastException when used on a Configuration with boolean fields created in the web console
Karaf-1701 Parsing of config for a field with cardinality > 1 is incorrectlyprocessed and displayed on Admin Console
Karaf-1149 Karaf MBeanServer is not usable behind firewall
Karaf-1561 Restart Framework from Web Console's System Information tab results in Karaf dying
Karaf-2095 Camel Route (JMS Polling) not working when installing feature "jndi"
Karaf-1545 Jar files in lib directory require "karaf-" prefix in order to be loaded
Karaf-1894 Framework's active start level is set to org.osgi.framework.startlevel.beginning too early when launching Karaf with empty bundle cache
Karaf-2011 dev:watch looks in an incorrect local maven repository

Resolved Issues:
Karaf-2359 DirectoryWatcher for "deploy" directory should be configured to wait until framework start level reaches 60

Apache Karaf 2.3.2:

New Issues:
N/A

Updated Issues:
N/A

Resolved Issues:
Karaf-2370 Add alias command
Karaf-2206 The container fails to start correctly with IBM Java 6
Karaf-2372 Introduce boot features sync mode property (true|false)
Karaf-1925 Blueprint timeout exceptions after karaf startup
Karaf-2359 DirectoryWatcher for "deploy" directory should be configured to wait until framework start level reaches 60
Karaf-2357 features-create-kar goal of the karaf-maven-plugin ignores bundles listed in the features that have the "dependency" property set to "true"
Karaf-2376 Make PropertiesLoginModuleTest OS file separator agnostic

Apache Karaf 2.4.0:

New Issues:
N/A

Updated Issues:
Karaf-2232 Upgrade to Aries Blueprint Core 1.1.1
Karaf-2069 Provide less command
Karaf-2138 Add a status check script and karaf script argument
Karaf-2121 Add Support For Displaying Gogo Commands in Karaf Shell Help
Karaf-2191 Karaf 3.0.x CLONE - Karaf startup fails with NullPointerException when logfile can't be written
Karaf-2299 WARN message should be logged when a boot feature installation fails
Karaf-2313 The feature:list command does not support multiple versions of the same feature
Karaf-1560 config:update throws ClassCastException when used on a Configuration with boolean fields created in the web console
Karaf-2315 The check for jvm.dll happens to early in the bat file
Karaf-1561 Restart Framework from Web Console's System Information tab results in Karaf dying
Karaf-2095 Camel Route (JMS Polling) not working when installing feature "jndi"
Karaf-1545 Jar files in lib directory require "karaf-" prefix in order to be loaded
Karaf-1894 Framework's active start level is set to org.osgi.framework.startlevel.beginning too early when launching Karaf with empty bundle cache
Karaf-2011 dev:watch looks in an incorrect local maven repository
Karaf-2300 log command to list all the logging levels currently been set
Karaf-2070 Add support of !$ to recall the last command argument
Karaf-222 Provide karaf:run, karaf:deploy, karaf:client Maven goals
Karaf-2140 Add an explicit allowEmptyPasswords to the LDAPLoginModule defaulting to false
Karaf-2366 Cannot Update Factory Configuration Not Backed By A File With The "config:" Command
Karaf-2367 Config Not Released When Declarative Services Bundle Stopped

Resolved Issues:
Karaf-2370 Add alias command
Karaf-2206 The container fails to start correctly with IBM Java 6
Karaf-2372 Introduce boot features sync mode property (true|false)
Karaf-2359 DirectoryWatcher for "deploy" directory should be configured to wait until framework start level reaches 60
Karaf-2357 features-create-kar goal of the karaf-maven-plugin ignores bundles listed in the features that have the "dependency" property set to "true"

 Apache Karaf 3.0.0:

New Issues:
N/A

Updated Issues:
Karaf-2232 Upgrade to Aries Blueprint Core 1.1.1
Karaf-2069 Provide less command
Karaf-2138 Add a status check script and karaf script argument
Karaf-2020 log:tail blocks on ^D
Karaf-2191 Karaf 3.0.x CLONE - Karaf startup fails with NullPointerException when logfile can't be written
Karaf-2299 WARN message should be logged when a boot feature installation fails
Karaf-2313 The feature:list command does not support multiple versions of the same feature
Karaf-2189 blueprint disable service too soon at shutdown
Karaf-2315 The check for jvm.dll happens to early in the bat file
Karaf-1545 Jar files in lib directory require "karaf-" prefix in order to be loaded
Karaf-1894 Framework's active start level is set to org.osgi.framework.startlevel.beginning too early when launching Karaf with empty bundle cache
Karaf-2300 log command to list all the logging levels currently been set
Karaf-222 Provide karaf:run, karaf:deploy, karaf:client Maven goals
Karaf-2140 Add an explicit allowEmptyPasswords to the LDAPLoginModule defaulting to false
Karaf-2366 Cannot Update Factory Configuration Not Backed By A File With The "config:" Command
Karaf-2367 Config Not Released When Declarative Services Bundle Stopped

Resolved Issues:
Karaf-2370 Add alias command
Karaf-2206 The container fails to start correctly with IBM Java 6
Karaf-2372 Introduce boot features sync mode property (true|false)
Karaf-2359 DirectoryWatcher for "deploy" directory should be configured to wait until framework start level reaches 60
Karaf-2357 features-create-kar goal of the karaf-maven-plugin ignores bundles listed in the features that have the "dependency" property set to "true"

Un-versioned Issues:

Karaf-2373 Generic capabilities should be formatted correctly when displaying bundle headers

Apache Karaf update June 23 - 29, 2013

In this Apache Karaf update report you'll find notes on development progress towards Apache Karaf 2.2.12, 2.3.2, 2.4.0, and 3.0.0 as up coming releases. All of the information here is collected from following Karaf's issues mailing list, and cross referencing with the community's issue tracker. The summary form is presented here courtesy of Savoir Technologies to help make keeping up with the community's fast pace a little easier.

Apache Karaf 2.2.12:

New Issues:
N/A

Updated Issues:
N/A

Resolved Issues:
Karaf-2368 Commands with more than one argument have incorrect help string

Apache Karaf 2.3.2:

New Issues:
Karaf-2370 Add alias command

Updated Issues:
Karaf-2206 The container fails to start correctly with IBM Java 6
Karaf-2232 Upgrade to Aries Blueprint Core 1.1.1
Karaf-1925 Blueprint timeout exceptions after karaf startup

Resolved Issues:
Karaf-2368 Commands with more than one argument have incorrect help string
Karaf-2365 jaas:manage selects wrong configuration
Karaf-2369 extend role.filter of LDAPLoginModule to support distinguishedName filter
Karaf-1487 Bundles in deploy are deployed before startup process had been finished

Apache Karaf 2.4.0:

New Issues:
Karaf-2370 Add alias command

Updated Issues:
Karaf-2206 The container fails to start correctly with IBM Java 6
Karaf-2232 Upgrade to Aries Blueprint Core 1.1.1

Resolved Issues:
Karaf-2368 Commands with more than one argument have incorrect help string
Karaf-2365 jaas:manage selects wrong configuration
Karaf-2336 Remove karaf-pax-exam and use pax-exam for itests
Karaf-2369 extend role.filter of LDAPLoginModule to support distinguishedName filter
Karaf-1487 Bundles in deploy are deployed before startup process had been finished
Karaf-2334 Upgrade to slf4j 1.7.5

 Apache Karaf 3.0.0:

New Issues:
Karaf-2370 Add alias command

Updated Issues:
Karaf-2206 The container fails to start correctly with IBM Java 6
Karaf-2247 Upgrade to Equinox 3.8.2.v20130124-134944
Karaf-2232 Upgrade to Aries Blueprint Core 1.1.1

Resolved Issues:
Karaf-2368 Commands with more than one argument have incorrect help string
Karaf-2365 jaas:manage selects wrong configuration
Karaf-2336 Remove karaf-pax-exam and use pax-exam for itests
Karaf-2369 extend role.filter of LDAPLoginModule to support distinguishedName filter
Karaf-1487 Bundles in deploy are deployed before startup process had been finished
Karaf-2334 Upgrade to slf4j 1.7.5

Un-versioned Issues:

Karaf-2348 Tooling-Exam does not wait for a complete test container shutdown
Karaf-1714 EIK can't create Karaf installation
Karaf-2276 SSH public key authentication missing in Karaf 2.3.X

Security BSides St John's 2013 Call for Papers

Call for Papers is open!

Will you step up to the podium this Fall?

BSides St. John’s 2013 is happening on October 18th, and will consist of a single speaking track. Regular presentation slot lengths are a fixed duration of 45 minutes plus 15 minutes for Q&A if necessary. And for 2013, BSides St. John’s is also accepting submissions for Lightning Talks. They will be limited to 10-15 minutes in duration and typically consist of 2 to 3 presentation slides. We are hoping that this short presentation time will encourage those new to presenting to submit.


We are currently investigating our options but hope to live stream the event and record all presentations for later distribution. If the recording and live streaming of your presentation poses an issue for you then please contact us to discuss your concerns.

It is important to note that any presentations or talks deemed to be of a marketing or sales pitch nature will be politely rejected.
Submissions will be in plain text and should address the following points:

• Your preferred email address
• Are you are representing anyone (yourself, company name, group name)
• The title and abstract for your presentation
• Approximate length of your presentation

Additionally, your submission should answer the following questions:

• Has this material been presented elsewhere? If so, where and when?
• May we record and stream your presentation? If not, why?
• Will you be traveling to the event? If so, from where?

Growing the Security Community in Newfoundland

Submissions must be emailed to BSidesStJohns@gmail.com. The CFP opens on June 27th and the deadline for submissions is October 4th. A confirmation of receipt of your submission will be sent within 48 hours. A follow-up email, if required, will be sent to you requesting further information or clarification.

Submissions will be reviewed as they are submitted. Submitter's will receive a personal response to their submission with our decision as to whether it has been accepted within two weeks of their submission date.

All submissions are greatly appreciated and we thank you in advance for your interest in BSides St. John’s 2013.