Ask Your Question
0

Wireshark on MacOS Mojave crashes when setting SSL key in protocols

asked 2019-02-13 04:13:13 +0000

I have a capture that I need to decrypt. I also have the private key from the server.

I started wireshark from command line ( wireshark /tmp/capture.cap ).

Then in Preferences->Protocols->SSL I set the path to the Pre-Shared-Key.

Then I click OK.

Now the app will crash and terminate. This is what it prints to stdout

20:03:47.629 Capture Warn

sync_pipe_wait_for_child: waitpid returned EINTR. retrying. Segmentation fault: 11

Please help. I am unable to decrypt the SSL session. Here is the crash log being sent to apple:

 Process:               Wireshark [64120]
Path:                  /Applications/Wireshark.app/Contents/MacOS/Wireshark
Identifier:            org.wireshark.Wireshark
Version:               2.6.6 (2.6.6)
Code Type:             X86-64 (Native)
Parent Process:        bash [51400]
Responsible:           Wireshark [64120]
User ID:               501

Date/Time: 2019-02-12 20:12:09.134 -0800 OS Version: Mac OS X 10.14.3 (18D109) Report Version: 12 Bridge OS Version: 3.0 (14Y674) Anonymous UUID: 7E979940-36F9-12F4-14A2-4529CA6C98D6

Sleep/Wake UUID: AF9A1738-CD5B-45A6-91FA-2E0AB6984F69

Time Awake Since Boot: 29000 seconds Time Since Wake: 3800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [64120]

Application Specific Information: Performing @selector(itemFired:) from sender NSMenuItem 0x7fcc26a0b860 Wireshark 2.6.6 (v2.6.6-0-gdf942cd8)

Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with GLib 2.37.6, with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.21.0, with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with SBC, with SpanDSP, with bcg729.

Running on Mac OS X 10.14.3, build 18D109 (Darwin 18.2.0), with Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (with SSE4.2), with 16384 MB of physical memory, with locale en_US.UTF-8, with libpcap version 1.8.1 -- Apple version 79.200.4, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with zlib 1.2.11, binary plugins supported (0 loaded).

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.9.00).

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 QtCore 0x0000000111b028d4 QSortFilterProxyModel::parent(QModelIndex const&) const + 84 1 QtCore 0x0000000111af7175 QIdentityProxyModel::parent(QModelIndex const&) const + 53 2 QtCore 0x0000000111adb0e3 QPersistentModelIndex::parent() const + 35 3 QtCore 0x0000000111aee072 mergeIndexes(QVector<qpersistentmodelindex> const&) + 306 4 QtCore 0x0000000111aeda5d QItemSelectionModelPrivate::_q_layoutChanged(QList<qpersistentmodelindex> const&, QAbstractItemModel::LayoutChangeHint) + 1853 5 QtCore 0x0000000111af1bb9 QItemSelectionModel::qt_static_metacall(QObject, QMetaObject::Call, int, void) + 921 6 QtCore 0x0000000111b62b6f QMetaObject::activate(QObject, int, int, void) + 1871 7 QtCore 0x0000000111be2be3 QAbstractItemModel::layoutChanged(QList<qpersistentmodelindex> const&, QAbstractItemModel::LayoutChangeHint) + 67 8 QtCore 0x0000000111af852c QIdentityProxyModelPrivate::_q_sourceLayoutChanged(QList<qpersistentmodelindex> const&, QAbstractItemModel::LayoutChangeHint) + 876 9 QtCore 0x0000000111af8bf2 QIdentityProxyModel::qt_static_metacall(QObject, QMetaObject::Call, int, void) + 850 10 QtCore 0x0000000111b62b6f QMetaObject::activate(QObject, int, int, void) + 1871 11 QtCore 0x0000000111be2be3 QAbstractItemModel::layoutChanged ...

(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-02-13 19:30:49 +0000

Guy Harris gravatar image

This is probably bug 14453.

edit flag offensive delete link more

Comments

Thank you! When will this be fixed? It has been more than 1 year since this bug was reported.

ferozed gravatar imageferozed ( 2019-02-18 04:35:44 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2019-02-13 04:13:13 +0000

Seen: 153 times

Last updated: Feb 13