Hi all!
Enabling Automatic reporting is a matter of setting
AutoreportingEnabled = on in the /etc/abrt/abrt.conf file.
This can also be accomplished through a D-Bus call.
However, we wanted to start with manual analysis and reporting
of the detected problems and develop ABRT configuration capabilities
later on.
You have pointed out security problems and I appreciate that. We have an
idea how
to sort out the problem with leaking potentially private stuff. For some
time now
ABRT has been storing Vendor of the relevant packages. So we need to check
if everything in the report was issued by a white-list of public vendors.
This hasn't been
implemented yet and it will take some time to ABRT team to do so, thus I
would
not try to include Automatic reporting in the first version of ABRT for
Cockpit.
Regards,
Jakub
---------- Původní zpráva ----------
Od: Andreas Nilsson <[email protected]>
Komu: [email protected]
Datum: 13. 2. 2017 13:20:06
Předmět: Re: Supporting ABRT in Cockpit
"Hi, and sorry for the delayed reply.
It's been a bit of traveling between conferences, and then I only
remembered I hadn't replied to this mail until yesterday.
The stories looks really good! Thanks for the good work there.
One thing I'm wondering about is automatic crash reporting. It's the
only thing I ever use myself on my laptop, and I know it's good useful
information for my OS provider (Fedora). I would never do the manual job
of reporting the crashers by hand (unless they are very critical).
At the same time I see how it could be a privacy concern to a specific
group of people (say in the situation where you are actually developing
a piece of software that is secret and maybe it's a competing product to
your competitor) where it would be good you would turn any automatic
reporting off.
Is automatic reporting planned for this initial version, or is that for
a later version?
- Andreas
On 2017-02-01 10:58, Matej Marusak wrote:
> Hi Cockpit people,
>
> A while ago the ABRT team presented [1] Cockpit module showing problems
detected by ABRT and allowing users to report them. It was more less a proof
of concept. But we are eager to finish this effort.
>
> After speaking with some members of the Cockpit team on DevConf we were
advised to start by writing user stories. We did so and today I presented
them on the wikipage of cockpit's github [2].
>
> We would love to have a feedback from you. What do you think of this? Is
it suitable for Cockpit?
> We are open-minded to yours ideas.
>
>
> Best regards,
> Matej
> ABRT
>
> 1: https://lists.fedorahosted.org/archives/list/cockpit-devel@lists.
fedorahosted.org/message/D6KLKDFMTRLSJSVBFY7ICTSPMHCOQO65/
> 2: https://github.com/cockpit-project/cockpit/wiki/Feature:-ABRT
> _______________________________________________
> cockpit-devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
"
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
