Crashdump - Revision history

DoesItReallyMatter: Dummy edit: Though I describe the endianness, OS and build string the coredump was from ~10 years ago and I expect the details have changed; thus they are no longer sensitive

2019-04-13T10:14:35Z

Dummy edit: Though I describe the endianness, OS and build string the coredump was from ~10 years ago and I expect the details have changed; thus they are no longer sensitive

← Older revision		Revision as of 10:14, 13 April 2019
Line 1:		Line 1:
			<!--Dummy edit-->
	:''See [[Report_bugs#Mac_OS_X_users\|here]] for macOS information''		:''See [[Report_bugs#Mac_OS_X_users\|here]] for macOS information''
	'''crashdump''' is the file VLC's Windows builds generate when VLC crashes. It is stored to '''%appdata%\vlc''' folder and its content can be send to VLC server during next startup if you want that. Content of the file is something like this:		'''crashdump''' is the file VLC's Windows builds generate when VLC crashes. It is stored to '''%appdata%\vlc''' folder and its content can be send to VLC server during next startup if you want that. Content of the file is something like this:

DoesItReallyMatter: Core dumps can be sensitive; use encryption! Full core dumps can reveal passwords and encryption keys. Small core dumps reveal hardware and software

2019-04-13T10:03:24Z

Core dumps can be sensitive; use encryption! *Full* core dumps can reveal passwords and encryption keys. *Small* core dumps reveal hardware and software

← Older revision		Revision as of 10:03, 13 April 2019
Line 1:		Line 1:
			:''See [[Report_bugs#Mac_OS_X_users\|here]] for macOS information''
	'''crashdump''' is the file VLC's Windows builds generate when VLC crashes. It is stored to '''%appdata%\vlc''' folder and its content can be send to VLC server during next startup if you want that. Content of the file is something like this:		'''crashdump''' is the file VLC's Windows builds generate when VLC crashes. It is stored to '''%appdata%\vlc''' folder and its content can be send to VLC server during next startup if you want that. Content of the file is something like this:
	<syntaxhighlight lang="ini">		<syntaxhighlight lang="ini">
Line 57:		Line 58:
	</syntaxhighlight>		</syntaxhighlight>

	~~So crashdump doesn~~'~~t reveal the played file or other programs you might be using~~. ~~You~~ can ~~check the content of crashdump file with~~ any ~~text editor~~.		'''It is a good idea to send crashdumps with encryption.''' Otherwise attackers can snoop and learn about any software vulnerabilities. For example, the metadata in the short crashdump above show 32-bit Windows Vista SP2 VLC 1.1.2 Qt Interface on what seems to be a Finnish locale. This information, combined with possibly more information, can make for an effective attack by compiling lists of vulnerabilities against 32-bit systems, Vista systems, VLC 1.1.2, etc. To guard against this:
			* For forum posts, email and bug reports you can use [[HTTPS]] (look for a green lock icon in the URL bar)
	~~File send operation is done via FTP~~, ~~so if your firewall blocks FTP connections, then~~ the crashdump ~~cannot~~ be ~~send to~~ VLC ~~developers~~.		* For file send operations, this means [[FTPS]] if available

	~~See~~ [[~~Report_bugs#Mac_OS_X_users\|here~~]] ~~for OS X users.~~

	[[Category:Glossary]]		[[Category:Glossary]]

DoesItReallyMatter: syntaxhighlight

2019-04-13T07:44:08Z

syntaxhighlight

← Older revision		Revision as of 07:44, 13 April 2019
Line 1:		Line 1:
	'''crashdump''' is the file VLC's Windows builds generate when VLC crashes. It is stored to '''%appdata%\vlc''' folder and its content can be send to VLC server during next startup if you want that. Content of the file is something like this:		'''crashdump''' is the file VLC's Windows builds generate when VLC crashes. It is stored to '''%appdata%\vlc''' folder and its content can be send to VLC server during next startup if you want that. Content of the file is something like this:
	<~~nowiki~~>		<syntaxhighlight lang="ini">
	[version]		[version]
	OS=6.0.6002.2.Service Pack 2		OS=6.0.6002.2.Service Pack 2
Line 55:		Line 55:
	779e19bb\|C:\Windows\system32\ntdll.dll		779e19bb\|C:\Windows\system32\ntdll.dll
	779e198e\|C:\Windows\system32\ntdll.dll		779e198e\|C:\Windows\system32\ntdll.dll
	</~~nowiki~~>		</syntaxhighlight>

	So crashdump doesn't reveal the played file or other programs you might be using. You can check the content of crashdump file with any text editor.		So crashdump doesn't reveal the played file or other programs you might be using. You can check the content of crashdump file with any text editor.

Courmisch at 13:06, 29 July 2017

2017-07-29T13:06:03Z

← Older revision		Revision as of 13:06, 29 July 2017
Line 61:		Line 61:
	File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.		File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.

	See [[Report_bugs#Mac_OS_X_users]] for OS X users.		See [[Report_bugs#Mac_OS_X_users\|here]] for OS X users.

	[[Category:Glossary]]		[[Category:Glossary]]

Courmisch at 13:05, 29 July 2017

2017-07-29T13:05:40Z

← Older revision		Revision as of 13:05, 29 July 2017
Line 61:		Line 61:
	File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.		File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.

	See [[/Report_bugs#Mac_OS_X_users]] for OS X users.		See [[Report_bugs#Mac_OS_X_users]] for OS X users.

	[[Category:Glossary]]		[[Category:Glossary]]

Corbax at 10:21, 1 October 2013

2013-10-01T10:21:24Z

← Older revision		Revision as of 10:21, 1 October 2013
Line 62:		Line 62:

	See [[/Report_bugs#Mac_OS_X_users]] for OS X users.		See [[/Report_bugs#Mac_OS_X_users]] for OS X users.

			[[Category:Glossary]]

RogerDPack at 20:34, 17 November 2010

2010-11-17T20:34:25Z

← Older revision		Revision as of 20:34, 17 November 2010
Line 60:		Line 60:

	File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.		File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.

			See [[/Report_bugs#Mac_OS_X_users]] for OS X users.

VLC help at 14:00, 10 August 2010

2010-08-10T14:00:13Z

← Older revision		Revision as of 14:00, 10 August 2010
Line 57:		Line 57:
	</nowiki>		</nowiki>

	So crashdump doesn't reveal the played file or other programs you might be using.		So crashdump doesn't reveal the played file or other programs you might be using. You can check the content of crashdump file with any text editor.

	File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.		File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.

VLC help at 13:59, 10 August 2010

2010-08-10T13:59:03Z

← Older revision		Revision as of 13:59, 10 August 2010
Line 58:		Line 58:

	So crashdump doesn't reveal the played file or other programs you might be using.		So crashdump doesn't reveal the played file or other programs you might be using.

			File send operation is done via FTP, so if your firewall blocks FTP connections, then the crashdump cannot be send to VLC developers.

VLC help at 13:57, 10 August 2010

2010-08-10T13:57:31Z

← Older revision		Revision as of 13:57, 10 August 2010
Line 55:		Line 55:
	779e19bb\|C:\Windows\system32\ntdll.dll		779e19bb\|C:\Windows\system32\ntdll.dll
	779e198e\|C:\Windows\system32\ntdll.dll		779e198e\|C:\Windows\system32\ntdll.dll
	<nowiki>		</nowiki>

			So crashdump doesn't reveal the played file or other programs you might be using.