| Author |
Message
|
| mk621 |
 Posted: Sat Oct 27, 2018 8:28 am Post subject: |
 |
|
Novice
Joined: 15 Oct 2012
Posts: 15
|
| zpat wrote: |
| Just to be clear, using a CCDT you do not need an updated version to use TLS 1.2 (or any cipher). |
Thanks for guidance, but I am new to CCDT. Can u give any link to tutoirial or any thread where I can learn to setup that.
Sorry if my questions feels silly to you.
Thanks again |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat Oct 27, 2018 10:17 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| dallen wrote: |
| As long as I don't publicly redistribute my modified copy or profit off it then I am not violating any laws... |
Did your IT management approve this? Did you/they run this by your HR and legal departments?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Oct 28, 2018 1:29 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| mk621 wrote: |
| zpat wrote: |
| Just to be clear, using a CCDT you do not need an updated version to use TLS 1.2 (or any cipher). |
Thanks for guidance, but I am new to CCDT. Can u give any link to tutoirial or any thread where I can learn to setup that.
Sorry if my questions feels silly to you.
Thanks again |
Why not google MQ CCDT ?
Or ask your qualified and experienced MQ administrator, which every company using MQ would be insane not to employ at least one of....
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| tczielke |
| Posted: Sun Oct 28, 2018 5:27 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
|
| Back to top |
|
|
| mk621 |
| Posted: Sun Oct 28, 2018 11:55 pm Post subject: |
|
|
Novice
Joined: 15 Oct 2012
Posts: 15
|
| zpat wrote: |
| mk621 wrote: |
| zpat wrote: |
| Just to be clear, using a CCDT you do not need an updated version to use TLS 1.2 (or any cipher). |
Thanks for guidance, but I am new to CCDT. Can u give any link to tutoirial or any thread where I can learn to setup that.
Sorry if my questions feels silly to you.
Thanks again |
Why not google MQ CCDT ?
Or ask your qualified and experienced MQ administrator, which every company using MQ would be insane not to employ at least one of.... |
Thanks ZPAT. you were helpful |
|
| Back to top |
|
|
| rdg |
| Posted: Mon Aug 12, 2019 8:07 am Post subject: |
|
|
Novice
Joined: 28 May 2010
Posts: 10
|
Anyone wishing to get hold of a newer copy can download the version from GitHub, here: https://github.com/ibm-messaging/mq-rfhutil
At the time of writing this was build version 9.1.3.230, built June 2019
So far, this version works like the unofficial v8.0.0 which I had been supplied (compatible) i.e. saves message files using the same format. It has updated TLS options including an "Any TLS 1.2" option.
Note: If you are upgrading from older versions e.g. v7.0.2, for some reason the MQMD byte sequence / marker in saved message files is different in these newer versions...
MQMD starts with “MD <STX>” with “MD <SOH>” (when viewed with Notepad++). Old message files can be remedied using a search and replace in Notepad++ or alike.
Also, we'd encountered an issue with v8.0.0 where it randomly and suddenly crashes / vanishes from the screen taking any last read messages with it. So far this hasn't occurred with v9.1.3 for me but it's early days yet. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 03, 2024 6:27 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
yes, just downloaded version 9.1.6 circa 2021 which is helpful
Be great if some kind person (Mark E Taylor) could add in ciphers since that date e,.g. TLS 1.3
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| markt |
| Posted: Thu Jun 06, 2024 11:21 pm Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
It's got the generic TLS13 options already - ANY_TLS13 and ANY_TLS13_OR_HIGHER
Those are much easier to deal with; it allows negotiation with whatever the server is prepared to use, which might be a specific cipher or also one of the generics. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Jun 07, 2024 12:39 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Good idea.
Thanks
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Last edited by zpat on Mon Jun 10, 2024 10:35 pm; edited 1 time in total |
|
| Back to top |
|
|
| hughson |
| Posted: Sun Jun 09, 2024 9:52 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Indeed
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Last edited by hughson on Mon Jun 10, 2024 10:39 pm; edited 1 time in total |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 10, 2024 10:36 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
OK, although I think it's the content that matters not the event itself.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
