| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12
Comments:
<0> tightvnc client can auto-create the tunnel for you, and tear it down when it's done.
<1> would i run the normal vnc server with a tightvnc client?
<1> another topic: is there a program or method to automate/require users to change p***words every X days?
<2> google can answer that
<1> i know you do so in p***wd or shadow (forget which) but what i want is for them to have a pop up after X login with old p***word
<3> muchacho: if you create an account with an expiration date for the p***word, it will expire and prompt the user to change it before hand.. if they failed to, the root/admin would have to set a new p***word them
<3> muchacho: here you go: man useradd |grep expire -A3 -B3
<3> muchacho: if you're the admin, you might be making more work for yourself.. just a little FYI
<1> OptimusPrime i'll go read that, but i dont want a solution that ... yeah exactly what you said above
<3> muchacho: well, what did you mean then? prompt them to change their p***word? and if they don't email them a new one?
<1> i want a solution that lets them (forces them) to change it even if they long in X+1 days later
<3> muchacho: man useradd |grep expire -A3 -B3
<1> got it, thanks
<1> anyone ever use xautolock to close out an X session due to inactivity?
<3> muchacho: not too sure such utils are necessary nowadays... KDE/Xfce/etc. have their 'own' locking mechanisms, not to mention xscreensaver as well
<3> muchacho: and the same would go for xlockmore/xload/etc. those are some old, pre XFree86-4.3.x tools
<1> i dont believe those options will logout a user in an X session due to inactivity for x minutes, will they?
<1> ok i didnt know about xlockmore or xload
<3> muchacho: no, they lock the screen and require a p***word...much like Windows screensavers can be setup
<1> yeah, thats not what i'm seeking. too many people are just leaving their session logged in overnight, over weekend etc
<1> i dont know if they're actually there or what so i cant do things like reboot etc
<1> and its a security issue (physical security)
<1> xautolock says it can do this, log out an x session after x mins
<1> but i cant find any docs on configuring it.
<3> muchacho: oh... don't know what to tell ya... haven't used it in ages
<3> muchacho: have you tried man xautolock or man autolock
<1> so you have used it? you're the first person willing to confess :)
<1> yeah, and i tried those configs, but login just sits there post expiration time
<1> i know its user error but cant quite discern what/why
<1> or perhaps its just too old a prog?
<3> muchacho: yea years ago under XFree86-4.3.x ... xautolock/xlockmore/xload/a bunch of them... you had to for the most part...most gui's didn't support that sort of thing
<1> from what i read via google, xautolock does the trick, repos even maintain it for yum
<1> so it cant be that out of date
<1> eh i'll go tinker with it later
<3> muchacho: have you tried reading the man?
<1> ok another one: in a script running yum -y blah blah, what should i use to keep running yum if it fails (stderr output results, i guess)
<1> OptimusPrime yes, its a short and quick man, and it makes sense but still no success
<3> muchacho: shoot, I just ran xlock...for memories...that pupy is a bugger
<1> i've never tried the others like xlock or such, xautolock is the only one googling said will log out an x session
<1> its not made for that mind you, but others said they achieved it
<3> muchacho: I gotcha
<1> well not made specifically for that
<1> anyway, any ideas on the script/yum issue?
<1> yum fails sometimes because repos i use are down or just had a bad connection etc
<1> even with mirror lists it fails sometimes so i wanted the script to keep retrying yum until it didnt fail
<3> muchacho: I don't use YUM.. I'm sporting Alpha Linxux, Redhat... YUM doesn't do anything for me... no packages or they're way out of date
<0> Why in the world would you want yum to do that?
<1> why would i want yum to retry?
<1> the repo isnt really down, for instance, i can run yum again right away and it works.
<0> Unless they're trusted packages from an internal repository, automated unattended updates are one of the stupidest things you can do.
<1> but once in awhile it fails, and works again right away if you retry
<0> Especially since you're apparently not using official package archives of whatever distribution you're using.
<1> they're all pretty standard repos (fedora, dag.wieers, freshrpms), you think that is still unwise?
<0> Of course.
<0> You don't randomly update boxen in a production environment, unless you're a fool.
<1> for security or stability reasons? or both?
<1> well i can go figure how to host my own repo, but what do you use to decide if an update is acceptable, just curious?
<0> You *test*, of course.
<1> do you run a test server ... ok answers that one
<0> Unless you like the idea of pushing $RANDOM_UPDATE to all the boxen and suddenly finding that $CRITICAL_APPLICATION no longer works.
<0> And, since you did the update unattended, you have no idea what got changed.
<1> i fully understand; i just havent had problems yet. of course thats no reason to keep going as is.
<0> You also apply updates when they're *necessary*, not just because there *is* one.
<1> well i would ***ume every update has either new features or bug resolutions you would want, what else are they updating?
<2> I'm keeping yum nightly update started on a production box
<1> i want to do my own yum repo anyway (quicker than every client going out to the net).
<3> muchacho: if you want speed, you'll compile everything yourself and custom your CFLAGS at build time
<1> but i do agree that using a beta box to test the updates is wiser.
<1> OptimusPrime i'm familiar with cflags; i'll have to go read on it
<1> i'm = i'm not
<3> muchacho: a lot of people complain about it, others swear by it. It can boost perf rather nicely...some buggy apps, not many, will act flakey but most will run like a top....
<0> muchacho: But are the "new features" anything you care about? Are the "bug resolutions" for anything that's affecting you?
<1> mwilson but to go and determine that for the 100s of pkgs updated weekly, is that feasible?
<4> i dont know
<1> if you test the updates on a beta box and see no problems, doesnt it make sense to update by default?
<0> Hardly.
<1> ok you may get no benefit but you get no harm.
<1> please explain.
<0> Version churn for the sake of version churn is always stupid.
<0> If (A) works and does what it's supposed to do in the way it's supposed to do it, why would you replace it with (B)?
<1> its not for the sake of version churn, its so you get the bug fixes and features, but its just the only feasible way i can think of doing it (ie without checking each pkg individually for benefit)
<1> perhaps A turns out to have a security hole only discovered recently?
<0> Of course you're doing it for the sake of version churn... I have no idea why you even try to pretend it's otherwise.
<0> As long as you want to update from repositories like freshrpms, what else would *you* call it?
<1> are you saying freshrpms wouldnt have bug fixes or new features?
<4> windows xp is a better choice
<1> OptimusPrime yeah i'd need to read up heavily on cflags then cause if there is a potential for probs, i cant just deploy ubiquitously
<0> muchacho: Huh? "can't deploy ubiquitously"? Where in the *world* did you get the idea that wasn't what you're already *doing*? You have very odd ideas about how things work.
<1> mwilson if you test the updates and then deploy, it is different from using something like cflags which i dont know at all ubiquitously
<3> muchacho: yea.. CFLAGS aren't too bad... about the only real program that you'll encounter thats buggy about it would be MySQL [not well written] and perhaps MnoGoSearch search engine...other than that, they're [problem softwares] are kind of rare
<3> muchacho: generally, as a rule, more warnings=worst written... oh, another iffy program is Firefox/Mozilla series.. you often can only built it with older [less restrictive] gnu compilers and with old installs of binutils...other than that
<1> OptimusPrime well i do use mysql so i'm a bit ancy (sp?) about it, but definitely sounds like its worth a read
<1> i use firefox too.
<0> muchacho: Despite what a Gentoo user like OptimusPrime would like you to believe, you have no reason to build your own binaries.
<3> muchacho: postgres compiles like a top! even with standard ansi c compilers like Compaq C....
<3> mwilson: I'm not a Gentoo user... I'm a Redhat 7.2 [alpha] user and cflags do give a nice kick... build openssl a couple of times and check it out for yourself
<3> mwilson: and run openssl speed
<1> OptimusPrime i would use postgres but some oss stuff i use requires mysql
<1> anyway i'm not going to build my own binaries; hell i have trouble installing binaries others built! :)
<1> perhaps later when i've learned more.
<3> mwilson: building my own binaries, and using my own compiler/cflags, is one of the reasons I still use this box... Compaq C is FREE speed... of about 50% or better
<1> regardless of all this, is there a way to make a command in a script repeat if it results in stderr (which is what i ***ume yum failure does) until it does not result so?
<3> muchacho: yep, using bash scripting but I"m not too much in to bash scripting
<1> yes i meant in bash scripting, but i just need to know what command to read up on
<1> i wonder if its as simple as some if output = stderr thing
<3> muchacho: you could use an 'if/else' statement...wheres Kitty when you need her.. shes a bash scripting wiz
<0> If yum is at all competently written, I imagine it supports standard result codes.
<1> OptimusPrime if i use the p***word options with useradd you were mentioning before, will it work in regards to an x session as well? meaning will user have option to change it via gui? or only from command line?
<3> muchacho: yea but if they have xsession running, they may not see the warning to change p***word..thats only displayed on the console and possibly in xterm.... it won't log them out, once they log out, they won't be able to log back in
<3> muchacho: if you set the warning period to several days warning, they may see it at some point, but its not guarrenteed unless they use the console at some point
<1> OptimusPrime thats the problem i have with that method, these users never use console, not even on login
<3> muchacho: ouch
<3> muchacho: they use something like GDM or KDM?
<1> so i'd be changing p***words forever then
<1> gdm
<1> i knew you could do it with useradd but it doesnt provide gui advance notice
<3> muchacho: thats a problem
<3> muchacho: xautolock may be your only real option
<4> is there any default p***wd for ubuntu?
<5> hello im a pc unix dummy what u advise me for 1 linux version ?
<4> root p***wd i mean
<0> darkolf: Of course not.
<4> maybe im downloading from a wrong mirror
<0> darkolf: Ubuntu doesn't use root, as is widely documented.
<4> just cant install it
<5> hi i want to p*** to linux but im a pc dummy for now what i have to put ?
<0> Try actually reading the instructions.
<5> can u give me help for linux i want to put linux but im pc dummy can u advise me best version?
<4> ubuntu has no root?
<1> just a "pc" dummy?
<0> vegan: You don't need Linux.
<5> no i do i have windows
<1> mwilson tell him waht he does need
<0> darkolf: So you haven't read anything at all about Ubuntu, huh?
<4> mwilson yes
<4> i dont
<4> hate reading
<5> so what u advise me ubunthu was to hard
<5> hey this is a help chan so help pc begginers to
<5> ok
<4> what i know is any user in the "admin" group has sudo power
<4> thats all
<0> muchacho: As far as I'm concerned, he doesn't need anything other than Windows. I would never recommend Linux to anyone.
<1> OptimusPrime actually xautlock doesnt mention anything about pw expiration unfortunately
<0> darkolf: They do?
<1> mwilson i meant what he "really" needs, go read, buy a book, a brain, etc.
<5> why can't i put linux if this is a linux chan i nead to know unix first?
<4> mwilson yes they are
<0> darkolf: Then why are you asking me?
<1> so it accurate to say we dont really know of a way to force users to change pw every x days but without getting admin involved? users who dont use console ever.
Return to
#linuxhelp
or
Go to some related
logs:
QuickTime7 for linux
bf2-deathmatch
Manduh food
xss scan
#linux
#linux
#apache
whitehat
./krad3 -t 1
#chatzone
|
|