Why Lubuntu 18.04 calls Amazon servers? (motd.ubuntu.com)
In wireshark logs I found that my Lubuntu 18.04 calls Amazon servers. See this log:
17 192.168.1.1 192.168.1.13 DNS 118 Standard query response 0x0e33 A motd.ubuntu.com A 54.194.229.79 A 52.18.210.215 OPT
18 192.168.1.1 192.168.1.13 DNS 142 Standard query response 0xebef AAAA motd.ubuntu.com AAAA 2a05:d018:91c:3200:4a81:cf9a:267b:97df AAAA 2a05:d018:91c:3200:5869:6d03:bf3a:f619 OPT
19 192.168.1.13 54.194.229.79 TCP 74 50656 > 443 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4010357077 TSecr=0 WS=128
20 54.194.229.79 192.168.1.13 TCP 74 443 > 50656 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1380 SACK_PERM=1 TSval=2116889653 TSecr=4010357077 WS=128
21 192.168.1.13 54.194.229.79 TCP 66 50656 > 443 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4010357137 TSecr=2116889653
22 192.168.1.13 54.194.229.79 TLSv1.2 284 Client Hello
It downloads some message of the day (MOTD). What is it and how to disable this "feature"?
lubuntu privacy motd
add a comment |
In wireshark logs I found that my Lubuntu 18.04 calls Amazon servers. See this log:
17 192.168.1.1 192.168.1.13 DNS 118 Standard query response 0x0e33 A motd.ubuntu.com A 54.194.229.79 A 52.18.210.215 OPT
18 192.168.1.1 192.168.1.13 DNS 142 Standard query response 0xebef AAAA motd.ubuntu.com AAAA 2a05:d018:91c:3200:4a81:cf9a:267b:97df AAAA 2a05:d018:91c:3200:5869:6d03:bf3a:f619 OPT
19 192.168.1.13 54.194.229.79 TCP 74 50656 > 443 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4010357077 TSecr=0 WS=128
20 54.194.229.79 192.168.1.13 TCP 74 443 > 50656 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1380 SACK_PERM=1 TSval=2116889653 TSecr=4010357077 WS=128
21 192.168.1.13 54.194.229.79 TCP 66 50656 > 443 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4010357137 TSecr=2116889653
22 192.168.1.13 54.194.229.79 TLSv1.2 284 Client Hello
It downloads some message of the day (MOTD). What is it and how to disable this "feature"?
lubuntu privacy motd
add a comment |
In wireshark logs I found that my Lubuntu 18.04 calls Amazon servers. See this log:
17 192.168.1.1 192.168.1.13 DNS 118 Standard query response 0x0e33 A motd.ubuntu.com A 54.194.229.79 A 52.18.210.215 OPT
18 192.168.1.1 192.168.1.13 DNS 142 Standard query response 0xebef AAAA motd.ubuntu.com AAAA 2a05:d018:91c:3200:4a81:cf9a:267b:97df AAAA 2a05:d018:91c:3200:5869:6d03:bf3a:f619 OPT
19 192.168.1.13 54.194.229.79 TCP 74 50656 > 443 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4010357077 TSecr=0 WS=128
20 54.194.229.79 192.168.1.13 TCP 74 443 > 50656 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1380 SACK_PERM=1 TSval=2116889653 TSecr=4010357077 WS=128
21 192.168.1.13 54.194.229.79 TCP 66 50656 > 443 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4010357137 TSecr=2116889653
22 192.168.1.13 54.194.229.79 TLSv1.2 284 Client Hello
It downloads some message of the day (MOTD). What is it and how to disable this "feature"?
lubuntu privacy motd
In wireshark logs I found that my Lubuntu 18.04 calls Amazon servers. See this log:
17 192.168.1.1 192.168.1.13 DNS 118 Standard query response 0x0e33 A motd.ubuntu.com A 54.194.229.79 A 52.18.210.215 OPT
18 192.168.1.1 192.168.1.13 DNS 142 Standard query response 0xebef AAAA motd.ubuntu.com AAAA 2a05:d018:91c:3200:4a81:cf9a:267b:97df AAAA 2a05:d018:91c:3200:5869:6d03:bf3a:f619 OPT
19 192.168.1.13 54.194.229.79 TCP 74 50656 > 443 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4010357077 TSecr=0 WS=128
20 54.194.229.79 192.168.1.13 TCP 74 443 > 50656 [SYN, ACK] Seq=0 Ack=1 Win=26847 Len=0 MSS=1380 SACK_PERM=1 TSval=2116889653 TSecr=4010357077 WS=128
21 192.168.1.13 54.194.229.79 TCP 66 50656 > 443 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4010357137 TSecr=2116889653
22 192.168.1.13 54.194.229.79 TLSv1.2 284 Client Hello
It downloads some message of the day (MOTD). What is it and how to disable this "feature"?
lubuntu privacy motd
lubuntu privacy motd
asked Dec 31 '18 at 13:12
Jasom Dotnet
25817
25817
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you have a look in /etc/update-motd.d/ you will see the configuration that is responsible for updating motd with information.
It's the 50-motd-news-file that is responsible for fetching news from motd.ubuntu.com (which is controlled by Ubuntu, but hosted in AWS, which is why whois shows Amazon).
Simply remove the 50-motd-news-file, and it will stop checking for news for motd.
You can also remove the update-motd package if you desire. sudo apt remove update-motd will disable all automatic motd updates, including update and reboot notifications.
In addition, you should change ENABLED=1 to ENABLED=0 in /etc/default/motd-news.
How I found this
I can add how I figured out this. I did a grep -r 'motd.ubuntu.com' /etc/ 2>/dev/null. This showed the two files mentioned above.
A apt-cache search update-motd confirmed that this was a package, and man update-motd explained how it works:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execution is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats).
Thus, removing any individual scripts will not be harmful. You can even add your own if you want.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105825%2fwhy-lubuntu-18-04-calls-amazon-servers-motd-ubuntu-com%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you have a look in /etc/update-motd.d/ you will see the configuration that is responsible for updating motd with information.
It's the 50-motd-news-file that is responsible for fetching news from motd.ubuntu.com (which is controlled by Ubuntu, but hosted in AWS, which is why whois shows Amazon).
Simply remove the 50-motd-news-file, and it will stop checking for news for motd.
You can also remove the update-motd package if you desire. sudo apt remove update-motd will disable all automatic motd updates, including update and reboot notifications.
In addition, you should change ENABLED=1 to ENABLED=0 in /etc/default/motd-news.
How I found this
I can add how I figured out this. I did a grep -r 'motd.ubuntu.com' /etc/ 2>/dev/null. This showed the two files mentioned above.
A apt-cache search update-motd confirmed that this was a package, and man update-motd explained how it works:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execution is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats).
Thus, removing any individual scripts will not be harmful. You can even add your own if you want.
add a comment |
If you have a look in /etc/update-motd.d/ you will see the configuration that is responsible for updating motd with information.
It's the 50-motd-news-file that is responsible for fetching news from motd.ubuntu.com (which is controlled by Ubuntu, but hosted in AWS, which is why whois shows Amazon).
Simply remove the 50-motd-news-file, and it will stop checking for news for motd.
You can also remove the update-motd package if you desire. sudo apt remove update-motd will disable all automatic motd updates, including update and reboot notifications.
In addition, you should change ENABLED=1 to ENABLED=0 in /etc/default/motd-news.
How I found this
I can add how I figured out this. I did a grep -r 'motd.ubuntu.com' /etc/ 2>/dev/null. This showed the two files mentioned above.
A apt-cache search update-motd confirmed that this was a package, and man update-motd explained how it works:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execution is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats).
Thus, removing any individual scripts will not be harmful. You can even add your own if you want.
add a comment |
If you have a look in /etc/update-motd.d/ you will see the configuration that is responsible for updating motd with information.
It's the 50-motd-news-file that is responsible for fetching news from motd.ubuntu.com (which is controlled by Ubuntu, but hosted in AWS, which is why whois shows Amazon).
Simply remove the 50-motd-news-file, and it will stop checking for news for motd.
You can also remove the update-motd package if you desire. sudo apt remove update-motd will disable all automatic motd updates, including update and reboot notifications.
In addition, you should change ENABLED=1 to ENABLED=0 in /etc/default/motd-news.
How I found this
I can add how I figured out this. I did a grep -r 'motd.ubuntu.com' /etc/ 2>/dev/null. This showed the two files mentioned above.
A apt-cache search update-motd confirmed that this was a package, and man update-motd explained how it works:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execution is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats).
Thus, removing any individual scripts will not be harmful. You can even add your own if you want.
If you have a look in /etc/update-motd.d/ you will see the configuration that is responsible for updating motd with information.
It's the 50-motd-news-file that is responsible for fetching news from motd.ubuntu.com (which is controlled by Ubuntu, but hosted in AWS, which is why whois shows Amazon).
Simply remove the 50-motd-news-file, and it will stop checking for news for motd.
You can also remove the update-motd package if you desire. sudo apt remove update-motd will disable all automatic motd updates, including update and reboot notifications.
In addition, you should change ENABLED=1 to ENABLED=0 in /etc/default/motd-news.
How I found this
I can add how I figured out this. I did a grep -r 'motd.ubuntu.com' /etc/ 2>/dev/null. This showed the two files mentioned above.
A apt-cache search update-motd confirmed that this was a package, and man update-motd explained how it works:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execution is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats).
Thus, removing any individual scripts will not be harmful. You can even add your own if you want.
edited Dec 31 '18 at 13:42
answered Dec 31 '18 at 13:20
vidarlo
9,30442445
9,30442445
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105825%2fwhy-lubuntu-18-04-calls-amazon-servers-motd-ubuntu-com%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown