Back to Blog
Red hat bugzilla5/15/2023 Even if a CVE exists, at least in the case of Ubuntu and Debian especially, users are often left with kernels full of known holes for months at a time. If the problem has a CVE assigned to it, maybe your distribution will pick it up. As a result, many "stable" or "LTS" distributions don't know which commits should be backported to their old kernels, or even that something needs backporting at all. These releases typically don't make explicit mention of which commits have security implications. New versions of Linux are released almost every week, often containing important security fixes among the other changes. > A common misconception about the Linux kernel is that it's secure, or that users can go a long time without worrying about security updates. Quoting from a sort of Arch-specific security hardening page: Reporting bugs is not difficult, and it is an important way to participate.Can confirm this is a very real problem with a long history. For example, only submit bugs about Red Hat products on the Red Hat Bugzilla, and submit bugs about LibreOffice by following LibreOffice's instructions. Use sites like Bugzilla to search for existing bug reports on the problem you have found.īe sure you submit your bugs on the correct bug reporting website. There are many wikis, listservs, and Q&A websites that are appropriate for asking questions. That means you must have performed some work on your own to conclude that there really is a bug. Be kindīug reporting websites are not for asking questions-they are for searching and reporting bugs. When you finish adding as much information as you can, press Submit Bug. If it happened only once, it's very unlikely anyone will be able to reproduce the problem you observed. Be sure to describe the exact steps needed to reproduce the problem and how reproducible it is: does it fail every time, every second, third, fourth, random time, or whatever. Add as much information as you can, including error messages and screen captures that illustrate the problem. If none match, fill in the information requested in the Description field. If one matches, click Add Me to the CC List to receive emails when changes are made to the bug. When you type a short problem description in the Summary field, Bugzilla displays a list of other bugs that might match yours. The following image shows how I filled out the required fields (and a couple of others that are not required). This will narrow down some of the choices on the next page. You'll need to select a classification for the bug to continue the process. Log into your account and click on New in the menu bar or the File a Bug button. Please do not do this unless you have a real bug to report. To demonstrate how to submit a bug report, I'll use a fictional example of creating a bug against the Xfce4-terminal emulator in Fedora. I strongly suggest not creating an account unless you intend to submit bug reports or comment on existing bugs. After you verify your email address, you can fill in the rest of the information to create your account.Īdvisory: Bugzilla is a working website that people count on for support. On Bugzilla's main page, click Open a New Account and fill in the requested information. The Red Hat Bugzilla website requires an account to submit new bugs or comment on old ones. 10 command-line tools for data analysis in Linux.Go to the Bugzilla site and click on the Advanced Search tab. You can search the Red Hat Bugzilla site without an account. If it appears that no one has encountered this problem before (or if they have, they haven't reported it as a bug), I go to the Red Hat Bugzilla site and begin searching for a bug report that might come close to matching the symptoms I encountered. I also try to check the various distro listservs. I always start with a search of relevant websites, such as the Fedora wiki, the CentOS wiki, and the documentation for the distro I'm using. Start with a searchĮven though it's tempting, never assume that seemingly anomalous behavior is the result of a bug. Bugzilla is a popular tool, and I use the Red Hat Bugzilla website to report Fedora-related bugs because I primarily use Fedora on the systems I'm responsible for. It's an easy process, but it may seem daunting if you have never done it before. Product maintainers use a lot of tools to let their users search for existing bugs and report new ones. But a way I can return some value to the Linux community is by reporting bugs. I am not a C language programmer, so I don't create fixes and submit them with bug reports, as some people do. As a long-time Linux user and sysadmin, I have benefited greatly from GNU/Linux, and I like to give back. Sometimes this leads me to discover bugs in the software I use, including Fedora and the Linux kernel. I spend a lot of time doing research for my books and articles.
0 Comments
Read More
Leave a Reply. |