Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Need to read/write files to 3rd part encryption format/schema via an I/O exit able to utilize sub processes for the decrypt/encrypt step.
We would be able to read/write to encrypted devices having proprietary formats.
CD for system i does not have possibility IFS directories and libraries restriction as on other platforms
In CD for unix is possible to define restriction for download and source directories in user map configuration on local functional user. I do not see this possiblity on CD for system i, Please could you add this functionality also for transfer fro...
Add cipher support
Need to connect to a wide variety of Customers.
TLS_RSA_WITH_AES_256_CCM (0xC0,0x9D)TLS_DHE_RSA_WITH_AES_128_CCM (0xC0,0x9E)TLS_DHE_RSA_WITH_AES_256_CCM (0xC0,0x9F)TLS_RSA_WITH_AES_128_CCM_8 (0xC0,0xA0)TLS_RSA_WITH_AES_256_CCM_8 (0xC0,0xA1)TLS...
Make the version info in the banner of the CLI commands (direct, ndmcli, ...) & GUIs consult a file in the install tree
We have received several security findings because CD gives version details that will allow hackers info on how to hack the software.
Add TLS 1.3 Support to Connect:Direct for HPE Nonstop Platform
It was mentioned in HPE NonStop Forum that TLSv1.3 will be coming out later 2019 year. It was also mentioned by HPE that TLSv1.0 is a degraded security protocol and that HPE NonStop Client Applications running on X86 and Itanium Platform need to m...
certificate-based authentication support for CDAIJ and CDW
Many customers from banks need to change their OS users' password every 1 or 3 months for all OS according to their security regulation which means all applications or middleware using the old password must change at the same time. For customers, ...
Update SNMP support to v3
Security benefits, as per security issues detailed here: https://www.us-cert.gov/ncas/alerts/TA17-156A
Connect:Direct for HP Non-Stop v126.96.36.199 bug fix needed to display protocol in full in NDM log
Currently in NDM log for C:D HP Non-Stop v188.8.131.52, the protocol is not displayed in full. In v184.108.40.206 there was only SSL vs TLS, but in v220.127.116.11, it is TLS1.0 and TLS1.2, thus truncation happened. Since operation/application support teams do not u...
Make ECHDE ciphers available for Selection in Connect Direct for IBM i
Current only RSA ciphers are available on Connect Direct for IBM in version 3.8. RSA ciphers are not considered deprecated due to ROBOT vulnerability.
C:D support for Multi Factor Authentication
Incorporate into the C:D security processing to allow for users signing on with multi factor authentication credentials.
Do not place IBM confidential, company confidential, or personal information into any field.