[07:24] <lordievader> Good morning
[14:22] <teward> cpaelzer: regarding 1893753.  no i havent made any plans to uograde because E:BUSY - theres also an additional dependency it needs packaged first.  I dont see this reported in Debian so maybe we need to check there too to see how they want to handle?
[14:23] <teward> because more deltas is... meh
[15:59] <xibalba> who could i inform that ns1 doesn't have a AAAA record?
[16:01] <sdeziel> ns1 from which domain?
[16:02] <xibalba> ns1,2,3.canonical.com. tried to lookup via whois, but it's privacy guard.
[16:03] <sdeziel> ah, right, none of those seems to have AAAA
[16:03] <sdeziel> maybe the IS team?
[16:10] <teward> um, isn't this By Design?
[16:10] <teward> sdeziel: ^
[16:10] <teward> to my knowledge NONE of the Canonical infra has v6 on it
[16:10] <teward> so no AAAA records is By Design
[16:11] <sdeziel> canonical.com has AAAA
[16:11] <teward> well
[16:12] <teward> xibalba: i can confirm the records exist
[16:12] <teward> so
[16:13] <xibalba> the NS1 server doesnt, so my ipv6 only resolver can't get the AAAA records for ubuntu.com, etc..
[16:13] <teward> xibalba: you never stated the *domain* you were working with
[16:13] <teward> state that in #canonical-sysadmin
[16:13] <teward> andonly there now
[16:37] <MIF> Is there a way for me to have the output print to a file and to my screen?
[16:37] <MIF> for example this command md5deep -r * > md5.txt
[16:39] <xibalba> MIF, try the script command
[16:39] <MIF> the what?
[16:39] <xibalba> which script
[16:39] <xibalba> - /usr/bin/script
[16:40] <MIF> /bin/md5deep
[16:41] <MIF> is that what you where looking for?
[16:44] <xibalba> no, lookup the command called 'script'
[16:44] <xibalba> type 'man script' on your terminal
[16:44] <MIF> ok?
[16:44] <xibalba> that will print your standard terminal output to your screen and to a file
[16:44] <genii> https://askubuntu.com/questions/625224/how-to-redirect-stderr-to-a-file
[16:45] <genii> Is probably more the solution required
[16:46] <tribaal> thanks
[16:46] <tribaal> (sorry, wrong chan. But thanks for all the good work everyone :) )
[16:47] <sdeziel> MIF sounds like you want "tee"
[16:47] <genii> The "script" command is more of a fake shell which can record all the commands and output of the commands
[16:47] <MIF> so this genii?  md5deep -r * >md5.txt 2>&1
[16:47] <genii> MIF: Yes
[16:48] <MIF> when I run that it dose not print it out, just to the file
[16:51] <MIF> I got it
[16:51] <MIF> I just had to flip the order around
[16:51] <MIF> to make it  md5deep -r * >&1 2>md5.txt
[16:51] <genii> I figured if you studied the answer givent here, it would occur to you
[16:51] <genii> given there, rather
[16:52] <MIF> thank you for your help
[16:56] <genii> Glad to assist
[16:58] <MIF> after me running that it only printed the errors so I just had to so a normal md5deep -r * >md5.txt then just tail the file
[19:55] <xibalba> whats the proper way to persist iptables config between reboots?
[19:56] <sdeziel> xibalba: apt install iptables-persistent
[19:58] <xibalba> thank you
[19:58] <sdeziel> yw
[23:38] <geosmile>  is there a way to hide from an attack on AWS on an Ec2 instance where I am root, but the account is controlled by someone else (who can clone the instance, or shutdown the instance etc)?
[23:39] <Ussat> wat ?
[23:50] <geosmile> Ussat, what is not clear on my question?
[23:50] <oerheks> if you are root, you are in control.
[23:51] <sarnold> I didn't understand it at all
[23:51] <oerheks> the 'but the account is controlled by someone else´  is weird
[23:51] <Ussat> and "hide from" ?
[23:51] <oerheks> are you legally owner?
[23:57] <JanC> I assume the AWS account is controlled by someone else
[23:57] <JanC> and that person isn't easily reachable maybe
[23:59] <geosmile> oerheks, There is a client of mine that owns an AWS account - I am root on one of the machines they created for me. I am root on the machine.
[23:59] <geosmile> I would like to encrypt/hide everything I do from the AWS account. The AWS account owner has the ability to clone the machine, shutdown the machine. Almost like having physical access to the machine.