=== m1dnight1 is now known as m1dnight_ === Monthrect is now known as Piper-Off === cpaelzer is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer === cpaelzer is now known as cpaelzer_afk === Lcawte|Away is now known as Lcawte === Piper-Off is now known as Monthrect === Lcawte is now known as Lcawte|Away === Lcawte|Away is now known as Lcawte === stevenroose|BNC is now known as stevenroose [17:27] does 14.03 server distribution not support wirelss network? [17:27] Ubuntu Server connects to wireless networks fine. [17:27] it won't recognise my card [17:27] You may need to install the wpasupplicant package though, and you will need configure /etc/network/intefaces as usual. [17:28] I believe it should recognise anything that Ubuntu generally does. If there's no support then it may be a Linux-wide thing. [17:28] 14.04 desktop uses it when i boot the cd [17:28] Maybe you need a firmware package or something. [17:28] all other distributions use it [17:29] If Ubuntu on the desktop can work with it then it can be made to work on Ubuntu Server. They share the same core platform, including kernel. [17:29] i thought it should...but it doesn't [17:29] bill_: -desktop installs network-manager whereas -server doesn't. network-manager handles a lot of the background plumbing for WiFi so it 'just works'. You can use network-manager service (without any GUI components) on -server, too [17:29] i will run the disk check on the install cd [17:29] maybe it's broken [17:30] i will try that [17:30] thank you TJ [17:30] TJ-: if it's just a single wireless network that needs connecting to, then no need for network-manager. Just wpasupplicant and /etc/network/interfaces can achieve all that network manager can in terms of that. [17:30] at the moment i have 14.04 desktop almost installed [17:31] i'll strip out the desktop 'fluff and install some more serveices [17:31] network manager is much higher up the stack than plain wireless driver problems. [17:32] i only want it to store the backups from other computers on the network [17:32] thanks for your help [17:32] i'll revisit this later === cpaelzer_afk is now known as cpaelzer [17:53] Hello, I am trying to set up my ubuntu server as a mailserver but I can't get it to send the mails, it only receives them. [17:54] toor: what error(s) do you receive when attempting to send mail? What are the logs telling you? Also, which version of Ubuntu Server are you using? [17:55] There are no errors and I cannot find any error logs. Ubuntu 14.04 TLS. [17:56] LTS* [17:57] toor: are you using postfix or sendmail or something else? [17:57] postfix, dovecot and I used the mail command. [17:59] toor: you should be able to view your postfix log in /var/log/mail.log [17:59] "No such file or directory" [18:01] toor: then you've likely changed some kind of configuration on your system telling it to log elsewhere [18:01] There is no such file anywhere on the system. [18:02] toor: again, that's because you've changed something from the postfix default...please pastebin the result of postconf -n and link it here [18:03] Cound be there's no syslog service, too [18:03] http://pastebin.com/21wJeY2L [18:06] toor: have you restarted postfix & rsyslog? sudo service postfix restart && sudo service rsyslog restart === cpaelzer is now known as cpaelzer_afk [18:12] postfix/postfix-script: fatal: the Postfix mail system is already running [18:12] [fail] [18:14] sounds like a PID file is present but the process has died, or else you started the process manually [18:15] I wrote "service postfix start" when the computer booted. [18:17] Is there a guide or something that works in all cases? [18:19] Could it be that it's Ubuntu's fault? I don't remember having problems installing on Debian [18:21] it's not likely ubuntu's QA would allow for completely broken packaging of postfix that did not log by default [18:22] Well I could try to reinstall and try from scratch.. [18:22] Could you private message me a tutorial that would work if I did that? [18:23] it would be better to try and understand the current state and the desired working state, instead of reinstalling blindly [18:24] It's too complicated for me. [18:24] toor: for example: if the service command says the service is already running, can you verify that by looking at the process list? There should be a process named "master". === cpaelzer_afk is now known as cpaelzer [18:27] toor: some amount of basic unix knowedge and analytical skills is needed to run a linux server. === cpaelzer is now known as cpaelzer_afk === hxm is now known as Guest96070 === hxm- is now known as hxm [21:11] if i plan a cronjob for lets say 1 2 3 1,3 0 /path/to/script.sh [21:12] it runs at 2:01 on the 3rd of january and march [21:12] what would the 'dow' parameter do here, only run it when that date is a sunday? [21:12] Yes. [21:13] hm so i would want that to be * I guess :) [21:13] Yes. :) [21:13] would be a funny 'why didnt my letsencrypt certs renew' debug session [21:20] heh mine are on manual [21:21] lets encrypt is not very friendly much other than a certificate [21:21] cannot use certificate pinning/dane/... with it, cause it changes so often, and you need to renew, but delay using it [21:21] patdk-lap: then you're pinning the wrong certs I guess [21:21] how so? [21:22] well you can also pin the letsencrypt intermediate for example [21:22] pinning an intermediate or ca certificate is a horrible thing to do [21:22] it means anyone that uses that same ca, can spoof you [21:22] and it assumes they dont rotate them out, most ca's rotate the intermediates yearly [21:23] letsencrypt hasn't said how they plan to do it yet [21:23] true [21:23] so you might just pin outself out of a useful website [21:23] (I don't have pinning atm) [21:23] and there is no way to fix that, other than hope your old certificate isn't expired [21:24] and the pin expiration time is highly short, and having it short is a bad idea [21:24] why can't you pin them? [21:24] well, I normally use 6month pins [21:24] letsencrypt is only good for 3 [21:25] I cannot pin a new one, till everyone knows about it [21:25] so say, I give it a 1month overlap [21:25] so the new cert is not useful for atleast 1 month [21:25] I add it to my websites pin [21:25] then after a month, I switch to it [21:25] patdk-lap: then maybe not use letsencrypt for this [21:25] and have the pin expire in a month [21:26] use it for a month, and start process to new one again [21:26] renewing doesn't imply using a new private key though [21:26] so you could still use the same pin? [21:26] using the same key is possible [21:26] but kindof defeats the point [21:26] half the point of getting a new cert, is to rotate the keys [21:26] so the bruteforce would have to start over [21:27] if you start reusing the keys, your likely going get yourself into trouble [21:28] not pinning the leaf isn't that bad though, plenty of people do it that way [21:28] even companies like github [21:28] they pin their root CA [21:29] anyway I still need to dive into that topic someday, first getting all my boxes set up with autmatic renewal + LE [21:29] I think someone could setup certs worse than letsencypt [21:30] yes, I just wish they had a 6month option [21:30] for usecases like this [21:30] 3months is fine for if you don't need any leadtime for the cert [21:32] atleast I got it programmed to update dane automatically [21:32] but haven't picked a solution to delay activation yet [21:33] probably will patch their program to keep two certs in the folder, and only use the old one [21:40] patdk-lap: Another option might be to pregerante key+csr, publish parallel dane/tlsa record, and then renew based on on that explicit csr. [21:42] but pinning is based only on the cert [21:43] I think [21:44] patdk-lap: No, pinning is based on the key material, and you can/should generate a backup pin based on an existing csr. [21:44] actually it's both [21:44] patdk-lap: How do you mean that it's both? [21:45] you can do it either way [21:45] pin by cert [21:45] or pin by public key [21:45] Ok, my bad. [21:45] Only seen pins based on the public key. [21:45] Why would you want to do it any other way? [21:46] easier to do :) [21:47] Well, writing that helper script is a one time thing in both cases. [21:48] if everyone could write that :) [21:48] most of the people using certificates have no idea how they work [21:48] let alone there are two parts to them [21:49] Not sure if one should try out HPKP unless one really knows what ones is doing? :-) [21:50] that is the problem [21:50] boss tells you to do it :) [21:50] or, you are new into that department [21:50] managing certs isn't exactly the highest and most important thing in a company view generally [21:51] it's easy to kindof tell, based on all the dnssec issues [21:51] certificate is annoying, and generally easily fixable, or worked around [21:51] dnssec is normally very noticable [21:51] Hmm, I think most DNSSEC issues are more about people not doing DNS right, which then becomes more much visable then you add DNSSEC. [21:54] But yeah, I agree with your more general point, about there being stuff like certs, dns(sec), etc which isn't given the needed importance. === Lcawte is now known as Lcawte|Away === Monthrect is now known as Piper-Off