** Description changed:
+ [Impact]
+
+ "postfix tls deploy-server-cert" did not handle a missing optional
+ argument which makes users get a "can't shift that many..." error.
+
+ In this SRU we are proposing a microrelease update in Focal from version
+ 3.4.10 to 3.4.13 since the changes are
** Changed in: postfix (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: postfix (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/postfix/+git/postfix/+merge/386118
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls
FYI the SRU exception for Postfix is documented here:
https://wiki.ubuntu.com/StableReleaseUpdates#Postfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls
Awesome, thank you for that. Since it was already approved there is no
reason to go through the whole process again, but to keep it documented
I'll create a wiki page for this Postfix exception and link it here:
https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
After
On Thursday, June 18, 2020 9:46:34 AM EDT you wrote:
> To do that a process needs to be defined for future Postfix SRUs
> containing micro-release updates. I see we already have some good DEP-8
> tests, so we'd need to write a wiki page describing this process and ask
> the SRU team to acknowledge
Scott, I asked around about this subject and those past SRUs with micro-
release updates were accepted probably based on this:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
And since Debian is also including those micro-releases in stable point
releases I also think we
On Wednesday, June 17, 2020 5:51:07 PM EDT Lucas Kanashiro wrote:
> I see this fix in version 3.4.13. Hopefully this postfix SRU [1] will be
> accepted and we will have version 3.4.11 in Focal, so we have two patch
> level releases to consider if we want to update to 3.4.13. Checking the
>
Thanks for the pointer Scott, appreciated. And also for fixing it in
Debian and consequently in Groovy which is a sync.
I see this fix in version 3.4.13. Hopefully this postfix SRU [1] will be
accepted and we will have version 3.4.11 in Focal, so we have two patch
level releases to consider if
This bug was fixed in the package postfix - 3.5.3-1
---
postfix (3.5.3-1) unstable; urgency=medium
[Wietse Venema]
* 3.5.3 LP: #1881196
[Debian Janitor]
* Trim trailing whitespace.
* Fix day-of-week for changelog entries 0.0.20001030.SNAPSHOT-4,
https://github.com/vdukhovni/postfix/commit/
119d6abed969b1b30c62722ae31c854b5682beae#diff-1843f98f5710e97bd063d5807334442a
There will be a new 3.4 release in a few days, I'd just update your SRU to
encompass that when it comes out. It's all bug fixes, reported by users or
not.
--
You
After proposing the mentioned change to Debian [1] we decided to wait
for the next snapshot release since upstream implementation might differ
from what was presented in the mailing list. Moreover, this is not an
urgent issue.
[1]
** Also affects: postfix (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu Bionic)
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls deploy-server-cert fails with "can't shift that many"
To manage notifications about this bug go
Link to postfix-users archive:
http://postfix.1071664.n5.nabble.com/postfix-tls-deploy-server-cert-
fails-with-quot-can-t-shift-that-many-quot-td106183.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Below is a reply from postfix-users. Works perfectly for me.
--
Below is a patch. I find that the handling of this differs a lot
among shell implementations, from terminating to ignoring.
Wietse
diff -ur /var/tmp/postfix-3.6-20200523/conf/postfix-tls-script
conf/postfix-tls-script
---
Ah. I'll report it to postfix-users as recommended.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls deploy-server-cert fails with "can't shift that many"
To manage
Postfix doesn't have a bug tracker. Their policy is to fix bugs when
they are identified. Emailing postfix-users is the correct path
forward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
The fix could be as easy as
--- a/conf/postfix-tls-script
+++ b/conf/postfix-tls-script
@@ -1039,7 +1039,7 @@ deploy-server-cert)
*) keyfile="${config_directory}/${2}" ;;
esac
- deploy_server_cert "${certfile}" "${keyfile}" || exit 1
+ deploy_server_cert
The man page doe snot hint to any wrong use in this case as far as I can see:
deploy-server-cert certfile keyfile
This subcommand deploys the certificates in certfile and private key in
keyfile (which are typically generated by the commands above, which will also
log and display the
full
I agree that it seems to miss an argument in the call from deploy-server-cert.
I have compared the versions up to the much more recent 3.5.2-1 but the
situation is the same.
Reproducing this doesn't need a lot of pre-setup:
$ apt install postfix ssl-cert
$ postfix tls deploy-server-cert
21 matches
Mail list logo
