Hi Matias,
>- Since the bug remains reproducible with the latest git HEAD, should I >make a new issue on the project's Github page, or is it enough that the >issue is now labeled "upstream" in Debian BTS? We prefer github, were we can provide patches and other upstream developers can look into >- The debug build says to include the debug dump capture file with the >>report. Do I need to prune this for sensitive data? The debug .pcap is >from a live system, where I'm logged into eg. Dropbox and Google Drive. >I'm looking at the .pcap in Wireshark, but there's 20k+ packets and I'm >worried someone could compromise some of these services with the data. You can try to reproduce in a virtual machine, or disable the dropbox/google drive services, in order to avoid this kind of data. Sensitive data in either case should be sent privately by mail. (if really necessary of course) you can also change your passwords and change them back once you have done -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
