IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 28 July 2014   (all times are UTC)

00:36roasted_ is now known as roasted
00:48rpt has left IRC (rpt!4dfe46a4@gateway/web/freenode/ip.77.254.70.164, Ping timeout: 246 seconds)
01:02Ark74 has left IRC (Ark74!~Ark74@189.220.254.152.cable.dyn.cableonline.com.mx, Remote host closed the connection)
03:22Parker955_Away is now known as Parker955
04:36Phantomas1 has joined IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas)
04:56vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
05:26
<vagrantc>
bennabiy: so, you've still got the indent runs co-mingled with other changes :P
05:27
bennabiy: this just makes it hard to review.
05:27bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
05:54mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:18adrianorg has left IRC (adrianorg!~adrianorg@179.180.167.164, Ping timeout: 260 seconds)
06:19adrianorg has joined IRC (adrianorg!~adrianorg@179.180.167.164)
06:33alexxtasi has joined IRC (alexxtasi!~alex@unaffiliated/alexxtasi)
06:35uXus has left IRC (uXus!~uXus@217.77.222.72, Ping timeout: 245 seconds)
06:48uXus has joined IRC (uXus!~uXus@217.77.222.72)
06:51workingcats has left IRC (workingcats!~workingca@212.122.48.77, Remote host closed the connection)
06:52vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
06:55workingcats has joined IRC (workingcats!~workingca@212.122.48.77)
06:58mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 260 seconds)
07:15mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
07:44Ark74 has joined IRC (Ark74!~Ark74@187.252.185.23)
08:00uXus has left IRC (uXus!~uXus@217.77.222.72, Ping timeout: 245 seconds)
08:01ben_nabiy has joined IRC (ben_nabiy!~bennabiy@unaffiliated/bennabiy)
08:04bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Ping timeout: 245 seconds)
08:13uXus has joined IRC (uXus!~uXus@217.77.222.72)
08:27Ark74 has left IRC (Ark74!~Ark74@187.252.185.23, Quit: Saliendo)
08:54Phantomas1 has left IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas, Ping timeout: 256 seconds)
08:55Phantomas1 has joined IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas)
09:08book` has left IRC (book`!~book`@192.241.198.49, Quit: ERC Version 5.3 (IRC client for Emacs))
09:12book` has joined IRC (book`!~book`@192.241.198.49)
09:26PhoenixSTF has joined IRC (PhoenixSTF!~rudiservo@78.29.147.214)
09:33Phantomas1 has left IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas, Ping timeout: 250 seconds)
10:59rafepren has joined IRC (rafepren!~rafepren@unaffiliated/rafepren)
11:34
<ben_nabiy>
vagrantc: You said run it, commit, then run it again and commit again, so I did
11:34
just do a diff between the two revisions
11:36ben_nabiy is now known as bennabiy
11:37
<bennabiy>
vagrantc: The indent run was only on ssh.c
11:37
both before and after my additional changes
11:43
so basically, if you see changes in other files it is what you see
11:45
<ogra_>
can you keep that in a separate commit ?
11:46
<bennabiy>
ogra_ So tell me clearly what you want to see me do.
11:46
I thought I did.
11:46
<ogra_>
one commit that has your feature change ...
11:47
once commit that has your indendation changes separately (if you insist to have them)
11:47
just keep whitespace change out of the feature code
11:47
<bennabiy>
I do not insist, I was just going according to what you all put in the README-DEVELOPMENT-POLICY
11:48
So either we should re-write it, or not balk when someone does it
11:48
<ogra_>
right, if something broke the formatting policy it should be fixed ... but in its own commit
11:48
<bennabiy>
Perhaps we should re-word it then.
11:49
<ogra_>
that probably too :)
11:49
<bennabiy>
I do not mind rolling back the work, once again (I am getting good at resubmitting the same code over and over...)
11:50
I just hate to waste time, thinking I am doing it right
11:50
<ogra_>
"if you change whitespace or formatting of existing code, please do this in a separate merge proposal"
11:50
seems sommething like that should go into the policy
11:51
<bennabiy>
Ok, so how about this. I will edit the README, and run indent, in one merge proposal, and then base the rest of my changes on that and do a second merge request
11:51
Should I just go ahead and run indent on all .c files?
11:51
without any changes made by me?
11:51
<ogra_>
sounds fine (though up to vagrant or alkis to accept ... i'm only standing on the fecne here)
11:51
*fence
11:51
<bennabiy>
heh
11:52
I figured I did not want you to break my fingers... or whatever else it says in there
11:57
ok, so here goes. Fresh merge request coming up in about 15
12:31
ok, so https://code.launchpad.net/~bennabiy/ltsp/ldm-cleanup/+merge/228474 is the code cleanup merge request (only ran indent on all .c files) no actual changes by me done. (vagrantc, alkisg)
12:32
let me know when I can then submit my actual changes.
12:32
I will be back in a few hours
12:58Faith has joined IRC (Faith!~paty@unaffiliated/faith)
13:18bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
13:27stgraber_ is now known as stgraber
13:48mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
13:59championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:15championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:15mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Ping timeout: 240 seconds)
14:16championofcyrod1 has joined IRC (championofcyrod1!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
14:30
<bennabiy>
back
14:32alexxtasi has left IRC (alexxtasi!~alex@unaffiliated/alexxtasi)
14:49kb8wmc has joined IRC (kb8wmc!~chatzilla@64.25.194.29)
14:58dberkholz has joined IRC (dberkholz!~dberkholz@gentoo/developer/dberkholz)
15:00mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
15:11telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
15:12championofcyrod1 has left IRC (championofcyrod1!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
15:12telex has joined IRC (telex!~telex@freeshell.de)
15:15championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
15:27abs has joined IRC (abs!4fbcde82@gateway/web/freenode/ip.79.188.222.130)
15:28abs is now known as Guest70301
15:28Guest70301 is now known as sbd
15:28sbd is now known as trr
15:47Gremble has joined IRC (Gremble!~Ben@host-92-27-135-217.static.as13285.net)
15:48Gremble is now known as Guest3980
16:07bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
16:58
<bennabiy>
!seen yanu
16:58
<ltsp>
yanu was last seen in #ltsp 1 year, 33 weeks, 0 days, 0 hours, 56 minutes, and 44 seconds ago: <yanu> fuzai: this is what I saved once :http://pastebin.com/Snt1tK4s
17:04jaskaran has joined IRC (jaskaran!~jaskaran@27.255.254.39)
17:17Guest3980 has left IRC (Guest3980!~Ben@host-92-27-135-217.static.as13285.net, Quit: I Leave)
17:45jaskaran has left IRC (jaskaran!~jaskaran@27.255.254.39, Ping timeout: 260 seconds)
17:49* bennabiy wishes vagrantc would just show up while I am here this time... ;)
17:50* bennabiy has gotten good at mixing persons...
17:50
<bennabiy>
Comes from having children.
17:59PhoenixSTF has left IRC (PhoenixSTF!~rudiservo@78.29.147.214, Ping timeout: 240 seconds)
18:18vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
18:20* bennabiy rejoices
18:20
<bennabiy>
Welcome vagrantc!
18:20
Two questions for you
18:21
One, was that latest merge request (the code cleanup one) acceptable? And two, once a merge has taken place, can I delete my old branches?
18:22
The code cleanup was just that, simply running indent on all the .c files, and modifying the README-DEVELOPER-POLICY file
18:28jaskaran has joined IRC (jaskaran!~jaskaran@27.255.254.39)
18:39
<vagrantc>
bennabiy: i merged the code cleanup branch
18:39
bennabiy: not your other branch has merge conflicts
18:39
er, now your...
18:39
<bennabiy>
yes, I have a new one ready, just waiting on the first merge to complete
18:39
<vagrantc>
but they're fairly easy to resolve
18:40
it's already pushed, i wouldn't worry about it
18:40
i.e. there's nothing really to wait for
18:41
<bennabiy>
yes
18:41
should I just delete the old branch now?
18:41
<vagrantc>
don't see any problem with that
18:41
<bennabiy>
great
18:41
one minute
18:41
<vagrantc>
or, old branches?
18:42
i.e. ldm-hash and ldm-cleanup
18:42
that said, i just reviewed the code, with my poor C skills... i didn't even do a compile test
18:43
but... what could possibly go wrong?
18:45
<Hyperbyte>
vagrantc, yes, what?
18:45* Hyperbyte whistles
18:46* vagrantc wonders what Hyperbyte is asking about
18:46
<vagrantc>
ah
18:48
bennabiy: so, you've got a predictible temp file ... that's not good practice... how about generating a random tempfile using proper tempfile generation functions, and then passing the tempfile as a variable to the rc.d hook
18:49
bennabiy: alternately... putting the hash in the environment and then clearing the environment variable, but that may leave stray processes with the environment in an unclean state
18:49* bennabiy shrugs.
18:49
<bennabiy>
I set the temp, and then have the RC clean it up one way or the other
18:49
it gets deleted
18:49
<vagrantc>
yes, but it shouldn't be a predictible file name
18:50
<bennabiy>
ok, let me push my setup as is, and then you can look at it, and then I will switch it to write to a temp name instead, with that name exported as environment.
18:51
<vagrantc>
mkstemp or something
18:51
<bennabiy>
yes, should not be too hard. I was actually planning on doing something like that anyways, but wanted to get something working in place to begin with
18:52
perfection is the enemy of good
18:52
<vagrantc>
fair enough
19:10
<bennabiy>
ok, merge request in
19:11
vagrantc: https://code.launchpad.net/~bennabiy/ltsp/ldm-hashing/+merge/228560
19:14
I am going to build new packages on my PPA, and then pull the source from them to do test with the temp name
19:14ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
19:14
<bennabiy>
Does it need to be a temp folder, or will a temp filename do fine?
19:14ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
19:17auts has joined IRC (auts!4fbcde82@gateway/web/freenode/ip.79.188.222.130)
19:29
<vagrantc>
bennabiy: temp filename should be fine ...
19:33
bennabiy: why move around the + g_free(sshinfo->password); ??
19:34
<bennabiy>
line?
19:34
ah, because it was being freed before the function ever was called
19:34
it was being freed once it had done the password to ssh
19:35
<vagrantc>
would it make sense to call the function sooner?
19:35
so as not to leave the password in memory as long
19:36
bennabiy: in the rc.d hook, why create the hashed password file when it's not going to be used?
19:36
<bennabiy>
either way, it would need to be freed once my function is called, and not where it is currently being freed
19:37
<vagrantc>
bennabiy: i'm asking if it makes sense to call your hashing function sooner, and leave the g_free where it is
19:38
bennabiy: also, would it make sense to not generate the hash file at all if the conditions (LDM_FATCLIENT, LTSP_LOCALAPPS) weren't true?
19:38
<bennabiy>
When are those set?
19:39
<vagrantc>
bennabiy: those environment variables are exported before LDM is started
19:39
<bennabiy>
ok, so I could test for them.
19:40
I was not sure, and did not want to rip apart everything to try to find out. I just wanted to get something to work
19:40
let me see if I can look at when it is called.
19:40
<vagrantc>
bennabiy: i'd also like to see the hashing be optional ... i.e. a way to return to the current behavior ... although i should be able to add that easily enough
19:41
<bennabiy>
I did not want to generate the file if the password was wrong
19:41* bennabiy sighs...
19:41
<vagrantc>
does it free the password before it determines if the password was wrong?
19:41
<bennabiy>
yes
19:42
it frees it once it sees that it has submitted the password
19:42
then if there is no response, it resets
19:42
and tries again
19:43
<vagrantc>
right
19:45
bennabiy: so, in the rc.d hook, you could unconditionally rm -f the file, rather than having multiple redundant if -e ; rm -f
19:45
<bennabiy>
so rather than catch the password, and store it and free it and store it and free it... I would rather just keep it and free it a microsecond later
19:45
yes
19:45
I thought of that too,
19:46
brb
19:46
<vagrantc>
bennabiy: how expensive is it to generate the hash? you could just generate the hash weather it's a valid password or not...
19:47
maybe only saving to the file if it's successful
19:49
<bennabiy>
hmm, it is semi expensive
19:49
because of the crypt call
19:50
ok, so this is untested change, but I will make the modification to use a temp name.
19:51Andymeows has joined IRC (Andymeows!~Andymeows@unaffiliated/andymeows)
19:52auts has left IRC (auts!4fbcde82@gateway/web/freenode/ip.79.188.222.130, Ping timeout: 246 seconds)
19:52
<Andymeows>
Hello, would it be possible/easy for a Debian ltsp-server to serve out an Ubuntu image to the clients?
19:54
<bennabiy>
Andymeows: Absolutely...
19:56
<Andymeows>
maybe something like 'ltsp-build-client --mirror file://mnt/Ubuntu-14.04.img' then?
19:56
or iso
19:57
I'm not finding a clear-cut guide from any search engines
19:57
<bennabiy>
VENDOR=Ubuntu ltsp-build-client --dist trusty
19:57
should get it, but maybe vagrantc would have more info
19:57
he is the debian guru
19:57
<Andymeows>
I'll give that a try
19:58
<bennabiy>
and if you need to specify an architecture, just add --arch i386 or amd64
19:58
etc
20:03
<Andymeows>
seems to be working so far. Thank you!
20:04rafepren has left IRC (rafepren!~rafepren@unaffiliated/rafepren, Quit: Leaving)
20:05
<bennabiy>
Great :)
20:05kb8wmc has left IRC (kb8wmc!~chatzilla@64.25.194.29, Quit: ChatZilla 0.9.90.1 [Firefox 20.0/20130329043827])
20:11
<bennabiy>
vagrantc: failed to build because quilt not installed?
20:12
from launchpad
20:12jaskaran has left IRC (jaskaran!~jaskaran@27.255.254.39, Quit: Ex-Chat)
20:13jaskaran has joined IRC (jaskaran!~jaskaran@27.255.254.39)
20:17
<vagrantc>
bennabiy: maybe you need to fix your launchpad build.
20:18
<bennabiy>
hmm
20:18jaskaran has left IRC (jaskaran!~jaskaran@27.255.254.39, Quit: Ex-Chat)
20:19
<vagrantc>
bennabiy: debian/source/format: is "3.0 (quilt)" in my packaging, so it shouldn't require a build-dep on quilt.
20:19
<bennabiy>
https://launchpadlibrarian.net/180930102/buildlog.txt.gz
20:19
<vagrantc>
bennabiy: as it uses dpkg-source's built-in quilt implementation
20:19
<bennabiy>
I am puzzled what I am doing wrong.
20:20
bzr: ERROR: bzrlib.plugins.builder.deb_util.MissingDependency: quilt is not installed, please install it.
20:20
<vagrantc>
i don't use launchpad to build packages, so no idea.
20:21
<bennabiy>
hmm
20:22
<vagrantc>
looks like your build rules are trying to apply quilt manually, but they shouldn't need to do so.
20:22
<bennabiy>
alkisg is failing too
20:23
wonder if it is the packaging
20:23
<vagrantc>
no, it's the build system
20:23
the packaging is fine.
20:23
<bennabiy>
It was building fine until today
20:24
<vagrantc>
ldm-debian-packaging last commit was from 2014-02-23
20:24
so something broke in the build system
20:24
<bennabiy>
yes, so something changed in launchpad
20:24
<vagrantc>
like trying to get too smart about quilt
20:25
<bennabiy>
err soyouz or whatever
20:26
<vagrantc>
ask in #launchpad or some other relevent channel
20:31
bennabiy: having ssh_hashpass handle the g_free means if the password is wrong it won't get freed?
20:33* vagrantc is planning on switching to debian branches with full uptream checkouts, for future reference
20:35
<bennabiy>
vagrantc: I would have to look at the greeter code, but it does not look like it frees it in the ssh_chat
20:35
apart from success so I think close_greeter() frees it, but I would have to look
20:36
so should we keep a copy of the packaging for ubuntu launchpad ?
20:38
<vagrantc>
dunno what you mean
20:39staffencasa_ is now known as staffencasa
20:39
<bennabiy>
I think I misunderstood what you said about debian branches
20:40
<vagrantc>
right now, the bzr branch only contains the debian dir. in the future, it will also contain the corresponding upstream source
20:40
at least, that's my intention
20:41
<bennabiy>
So what will that do for those of us in Ubuntu land?
20:41
Right now my head is spinning in about 6 different directions
20:41
sorry for all the questions
20:42
<vagrantc>
you'll need to teach launchpad to only use the debian dir.
20:42
i think it has support for that sort of thing.
20:42
<bennabiy>
Heh, or branch it :)
20:43
yes, that is what it is doing now
20:43
<vagrantc>
right, and that will fail when i switch.
20:44
have alkisg figure it out :)
20:46
<bennabiy>
!learn alkisg_todo as figure it out...
20:46
<ltsp>
The operation succeeded.
20:49
<bennabiy>
!alkisg_todo
20:49
<ltsp>
alkisg_todo: (#1) LDM password hash, or (#2) Hooks for running scripts on these phases: INITRD/INIT/RC/DM/AUTH/LOGIN/SESSION/PERIODIC/LOGOUT/SHUTDOWN, or (#3) implement ltsp-config aoe, or (#4) figure it out...
20:49
<bennabiy>
!forget
20:49
<ltsp>
(forget [<channel>] <key> [<number>|*]) -- Removes a key-fact relationship for key <key> from the factoids database. If there is more than one such relationship for this key, a number is necessary to determine which one should be removed. A * can be used to remove all relationships for <key>. If as a result, the key (factoid) remains without any relationships to a factoid (key), it shall be removed from the database. (1 more message)
20:50
<bennabiy>
!forget alkisg_todo 4
20:50
<ltsp>
The operation succeeded.
20:50
<bennabiy>
!alkisg_todo
20:50
<ltsp>
alkisg_todo: (#1) LDM password hash, or (#2) Hooks for running scripts on these phases: INITRD/INIT/RC/DM/AUTH/LOGIN/SESSION/PERIODIC/LOGOUT/SHUTDOWN, or (#3) implement ltsp-config aoe
20:51
<bennabiy>
!learn alkisg_todo as teach launchpad to only use the debian dir when vagrantc makes his branch correspond with upstream source
20:51
<ltsp>
The operation succeeded.
21:09Andymeows has left IRC (Andymeows!~Andymeows@unaffiliated/andymeows, Ping timeout: 250 seconds)
21:13
<bennabiy>
vagrantc: I will need to finish patching tomorrow.
21:13
Are you going to be around?
21:24
<vagrantc>
here and there
21:24
bennabiy: this is a much desired feature, though.
21:24
bennabiy: so thanks so much for working on it!
21:25
<bennabiy>
no problem. Glad to be able to contribute a little
21:25
see you tonight or tomorrow
21:36Andymeows has joined IRC (Andymeows!~Andymeows@unaffiliated/andymeows)
22:04Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
22:48adrianorg has left IRC (adrianorg!~adrianorg@179.180.167.164, Ping timeout: 245 seconds)
22:50adrianorg has joined IRC (adrianorg!~adrianorg@179.187.24.30.dynamic.adsl.gvt.net.br)
22:56
<bennabiy>
!learn bennabiy_todo as Temp file for hash
22:56
<ltsp>
The operation succeeded.
22:56
<bennabiy>
!bennabiy_todo
22:56
<ltsp>
bennabiy_todo: (#1) Finish patching LinuxMint code to detect NON mint chroot build requests on mint, and to build a mint chroot on non mint server., or (#2) Temp file for hash
22:57* vagrantc forgets what's on the todo list
22:57
<vagrantc>
!vagrant-todo
22:57
<ltsp>
Error: "vagrant-todo" is not a valid command.
22:57
<vagrantc>
!vagrantc-todo
22:57
<ltsp>
Error: "vagrantc-todo" is not a valid command.
22:57* vagrantc cheer
22:57
<bennabiy>
heh
22:59
!vagrantc_todo
22:59
<ltsp>
vagrantc_todo: solve all the mysteries of the world... or at least try.
22:59* vagrantc didn't even think to check _
23:01
<bennabiy>
heh, I just added it
23:01
back in a few
23:30
vagrantc: Can you leave me with a clear list of what you need me to change before you will allow the merge?
23:30
I will work on it tomorrow
23:31
<vagrantc>
the main thing is the tempfile handling
23:31
should use something like mkstemp at the very least
23:31
seems like there should be some clean way to do it without writing any files...
23:32
ut i guess with variable export, that can linger in the environment of other processes...
23:32
<bennabiy>
there is, if I have it fire after the RC files all run, I could write straight to /etc/shadow
23:32
but that is tricky
23:33
I feel more comfortable having it in a root owned 600 file than in environment
23:33
because ultimately, if someone has access to the terminal, they have access to root
23:34
<vagrantc>
so, my idea is to use mkstemp to generate a /tmp/ldm-XXXXXX or some such, and then set the path to the tempfile in a variable...
23:34
<bennabiy>
I mean, if someone was really wanting to get the passwords, they could attach to ldm and watch for the password to be grabbed on input or pushed to ssh
23:34
yes
23:35
then delete the file and unset the variable
23:35
<vagrantc>
right
23:35
i would really like this to be opt-out or opt-in, also ...
23:36
<bennabiy>
!learn bennabiy_todo as use mkstemp to generate a /tmp/ldm-XXXXXX or some such, and then set the path to the tempfile in a variable...
23:36
<ltsp>
The operation succeeded.
23:36
<bennabiy>
!learn bennabiy_todo as to be opt-out or opt-in,
23:36
<ltsp>
The operation succeeded.
23:36
<vagrantc>
LDM_HASHPASS boolean?
23:36
<bennabiy>
which would you like the default to be?
23:36
opted in or out?
23:37
<vagrantc>
since it's such a commonly requested feature, i think opt-in would be ok.
23:37
er, opt-out
23:37
opt-out would be fine, even though it's a change in behavior, i think it's reasonably well done.
23:37
<bennabiy>
so if LDM_HASHPASS=false would be what to check for
23:37
<vagrantc>
we have boolean_is_true functions
23:38
<bennabiy>
yes
23:38
<vagrantc>
to catch other boolean values
23:38
<bennabiy>
!learn bennabiy_todo as <vagrantc> LDM_HASHPASS boolean?
23:38
<ltsp>
The operation succeeded.
23:39
<bennabiy>
great
23:39
should be able to pull that off tomorrow, if all goes well
23:42Mike has joined IRC (Mike!ad24c407@gateway/web/freenode/ip.173.36.196.7)
23:42Mike is now known as Guest51018
23:43
<Guest51018>
Hello, I'd like some help with VPN.
23:43
Can each ltsp client connect to their separate VPNs?
23:45
<vagrantc>
what exactly are you trying to accomplish with the vpn ?
23:50
<Guest51018>
Some of the users would like to connect to their labs/servers using vpn connections.
23:51
I can successfully connect to vpn from the server, but unable to do so from client machines.
23:52
<vagrantc>
fat clients?
23:52
<Guest51018>
thin
23:52
<vagrantc>
thin clients essentially are the server
23:53
so you wouldn't need a separate vpn for each user
23:53
unless you're talking about thin clients with localapps...
23:53
<Guest51018>
sorry, I'm not sure what localapps are..
23:54
<vagrantc>
apps running on the client hardware, but most apps running on the server (thin clients)
23:54
<Guest51018>
I was hoping to use Openconnect (cisco's anyconnect equivalent)
23:55
<vagrantc>
if you just want a vpn connection from the server to a vpn network, there isn't anything ltsp-specific about it, really.
23:56
so you'd configure it like you would for any machine ... unless openconnect/anyconnect does things on a per-user basis ... then i'm not sure what you'd do.
23:56
<Guest51018>
i see..
23:57
do fat-clients build their own tunnels? or is it on the server as well?
23:58
<vagrantc>
fat clients are running all applications locally, so it's largely like you would with any disked machine