abrt-auto-reporting(1)
======================

NAME
----
abrt-auto-reporting - Get or modify the auto reporting option values

SYNOPSIS
--------
'abrt-auto-reporting' [-v] [ enabled | yes | 1 | on | disabled | no | 0 | off ]
                      [ [--anonymous] |
                        [--username USERNAME [--password PASSWORD] ] |
                        [--certificate SOURCE] ]

DESCRIPTION
-----------
Reads the configuration from abrt.conf and saves the changes to the same file.

The changes will take effect immediately without necessity to restart any ABRT
process and will be persistent.

'disabled'::
   User have to report the detect problems manually

'enabled'::
   ABRT uploads an uReport which was generated for a detected problem
   immediately after the detection phase.

Reads and saves the authentication configuration options in
/etc/libreport/plugins/ureport.conf and /etc/libreport/plugins/rhtsupport.conf

uReport description
~~~~~~~~~~~~~~~~~~~
ABRT supports uReports for four types of crashes: crashes of C/C++ programs
that result in a core dump, uncaught Python exceptions, uncaught Java
exceptions and kernel oopses.

Each uReport generally contains a stack trace, or multiple stack traces in the
case of multi-threaded C/C++ and Java programs. The stack trace only describes
the call stack of the program at the time of the crash and does not contain
contents of any variables.

Every uReport also contains identification of the operating system, versions of
the RPM packages involved in the crash, and whether the program ran under a
root user.

There are also items specific to each crash type:

C/C++ crashes::
    these are path to the executable and signal delivered to the program,

Python exceptions::
    there is the type of the exception (without the error message, which may
    contain sensitive data),

for kernel oopses::
    these are list of loaded kernel modules, list of taint flags, and full text
    of the kernel oops.

The authenticated uReports also contains *hostname* and *machineid* to enable a
server side filtering at https://access.redhat.com/.

The authenticated uReports have the benefit of rich server replies which may
include a solution for the submitted crash. The authentication is done using
either Anolis Subscription Certificates or Anolis Customer Portal
credentials.

'Warning':
The full text of a kernel oops might contain information like the
identification of the host hardware type. You should disable the autoreporting
feature if you do not want to share this information with Anolis.


OPTIONS
-------
-v, --verbose::
   Be more verbose. Can be given multiple times.

-a, --anonymous::
   Turns the authentication off by clearing both 'SSLClientAuth' and 'HTTPAuth'
   configuration options in /etc/libreport/plugins/ureport.conf

-u, --username USERNAME::
   Turns HTTP Authentication on by setting 'HTTPAuth' configuration option to
   *rhts-credentials* in /etc/libreport/plugins/ureport.conf and storing
   USERNAME and PASSWORD in /etc/libreport/plugins/rhtsupport.conf
   Also turns the SSL Client Authentication off, because these methods cannot
   be used together.

-p, --password PASSWORD::
   Password for HTTP Authentication. If not provided, a prompt asking for it
   will be issued.

-c, --certificate SOURCE::
   Turns SSL Client Authentication on by setting 'SSLClientAuth' configuration
   option to SOURCE in /etc/libreport/plugins/ureport.conf.
   Also turns the HTTP Authentication off, because these methods cannot
   be used together.

SEE ALSO
--------
abrt.conf(5), ureport.conf(5), rhtsupport.conf(5)

AUTHORS
-------
* ABRT team
