** Patch added: "openssl-atexit-1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+attachment/5607147/+files/openssl-atexit-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
** Description changed:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
** Description changed:
+ [Impact]
+
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
I uploaded a patched package to
https://launchpad.net/~nicolasbock/+archive/ubuntu/lp1983100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build
Public bug reported:
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
(openssl/openssl@c2b3db2).
The
Hi Dan,
Before the upstream openssl fix [1] the behavior was to send a proper
CertificateStatus if the client requested the status_request extension
from the server in a CertificateRequest. In other words, the additional
information contains valid data.
[1]
** Description changed:
[Impact]
openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
CertificateRequest message to the client with a non-empty
status_request extension.
This issue was fixed in openssl-1.1.1d and is included in Focal
onward.
Upstream issue is
** Description changed:
[Impact]
openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
CertificateRequest message to the client with a non-empty
status_request extension.
This issue was fixed in openssl-1.1.1d and is included in Focal
onward.
Upstream issue is
Test package at
https://launchpad.net/~nicolasbock/+archive/ubuntu/sf00317240
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1940141
Title:
OpenSSL servers can send a
** Patch added: "bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5518220/+files/bionic.debdiff
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Nicolas Bock (nicolasbock)
** Changed in: openssl (Ubuntu Bionic)
will break
with this patch. As a non-empty reply is incorrect behavior
** Affects: openssl (Ubuntu)
Importance: Undecided
Assignee: Nicolas Bock (nicolasbock)
Status: New
** Affects: openssl (Ubuntu Bionic)
Importance: Undecided
Assignee: Nicolas Bock (nicolasbock
** Description changed:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
Public bug reported:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple
On Tue, Sep 29 2020, Brian Murray wrote:
> On Tue, Sep 29, 2020 at 12:38:38PM -0000, Nicolas Bock wrote:
> Could you please run 'systemctl status whoopsie' and
> include the output of the command here?
$ sudo systemctl status whoopsie
● whoopsie.service - crash report submissi
Still failing for me. I see now:
Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when
automatic reporting is enabled...
Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Succeeded.
Sep 29 06:32:27 rubberducky systemd[1]: Finished
On Fri, Sep 25 2020, Brian Murray wrote:
> The issue with PathChanged is that /var/crash is used for writing three
> types of files. The .crash file, the .upload file (which signifies the
> crash is ready to be uploaded), and the .uploaded file (which contains
> the UUID of the crash in the error
@balint I was wondering why we don't use `PathChanged` in the systemd
path file. This checks for any changes in the path and will pick up new
crash files... But after reading the systemd docs again I guess the
reason is that we want the service to activate if the crash directory
already contains a
On systemd-246.4-1ubuntu1 the setting PathChangedGlob leads to an error.
But I tried the following which seems to work correctly:
[Path]
# PathExistsGlob=/var/crash/*.crash
PathChanged=/var/crash
Thanks @rockrequin for the hint!
--
You received this bug notification because you are a member of
After deleting the files *.upload{,ed} I can run
$ sudo /usr/share/apport/whoopsie-upload-all
/var/crash/_usr_bin_emacs-gtk.1000.crash already has info collected
Marking /var/crash/_usr_bin_emacs-gtk.1000.crash for whoopsie upload
All reports processed
And get the two files back. The content of
When I run the whoopsie upload script I get:
$ sudo /usr/share/apport/whoopsie-upload-all
/var/crash/_usr_bin_emacs-gtk.1000.crash already marked for upload, skipping
All reports processed
Why is it skipping the crash?
--
You received this bug notification because you are a member of Ubuntu
$ journalctl -b -u apport-autoreport
Sep 14 13:01:52 rubberducky systemd[1]: Starting Process error reports when
automatic reporting is enabled...
Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Collecting info for
/var/crash/_usr_bin_gnome-shell.1000.crash...
Sep 14 13:02:07
The error message (the last 3 lines) keep repeating ad infinitum until I
manually remove the crash files in /var/crash as Rocky notes in
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13.
--
You received this bug notification because you are a member of Ubuntu
Touch
22 matches
Mail list logo
