Re: [SLUG] Linux client for Citrix Access Gateway?
(sorry Sridhar, replied to you directly instead of the list) On Sat, May 31, 2008 at 11:55 PM, Sridhar Dhanapalan <[EMAIL PROTECTED]> wrote: > We're trying to deploy a Linux server into an all-Windows company. Our > client > is actually quite happy with this solution, but we were informed a couple > of > days ago that they have a Citrix Access Gateway VPN server that we must go > through in order to interact with their network. > > I can't seem to find any clear information on how to connect to the VPN > with > our Linux server. The client Citrix refers to appears to be for remote > desktop use through a Web browser, and is hence useless for a server. > I don't know much about Citrix so I could be suggesting something silly, but I searched a bit of Google and found references to some Linux "ICA Client" that apparently connects to the Citrix Access Gateway. Have you used it? Is this the software they currently use on Windows desktops to connect to the access gateway? Failing that, maybe the Citrix Access Gateway VPN Server can be configured to allow other protocols? (like IPSec, and use something like FreeS/WAN to connect) Just throwing some ideas. - Gonzalo -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open Source Medical Practice Management Software
Reviving an old thread, I just found this site: http://gplmedicine.org/ -- "The thing he [Bill Gates] realised about the windows was this: because they had been converted into openable windows after they had first been designed to be impregnable, they were, in fact, much less secure than if they had been designed as openable windows in the first place." - Douglas Adams signature.asc Description: This is a digitally signed message part. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Linux client for Citrix Access Gateway?
Sridhar Dhanapalan <[EMAIL PROTECTED]> writes: > We're trying to deploy a Linux server into an all-Windows company. Our > client is actually quite happy with this solution, but we were > informed a couple of days ago that they have a Citrix Access Gateway > VPN server that we must go through in order to interact with their > network. > > I can't seem to find any clear information on how to connect to the > VPN with our Linux server. The client Citrix refers to appears to be > for remote desktop use through a Web browser, and is hence useless for > a server. Sadly, I think you are out of luck. My understanding is that the Citrix Access Gateway "VPN" server is actually a browser hosted RDP-over-SSL solution. Since there isn't, as far as I know, any functional RDP server for Linux available you are not going to have an easy path to getting this working, as I understand things. This may help, though: http://support.citrix.com/article/CTX109043 > In a cruel twist of irony, I discovered that the Citrix device is > essentially a Supermicro rackmount unit loaded with RHEL, with the > proprietary Citrix software running on top. > > So despite our client being happy with a Linux-based solution, they > seem to be locked into Windows by their VPN. Depending on how much this is worth you /may/ find that one of two options suits: Option one, install PuTTY or another SSH client on a Windows system within their network. Use RDP to access that system and then SSH to connect to your Linux server. Option two, pay for a commercial RDP server for Linux. Regards, Daniel You could also resurrect http://xrdp.sf.net/ -- but that doesn't look fun to me. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Linux client for Citrix Access Gateway?
We're trying to deploy a Linux server into an all-Windows company. Our client is actually quite happy with this solution, but we were informed a couple of days ago that they have a Citrix Access Gateway VPN server that we must go through in order to interact with their network. I can't seem to find any clear information on how to connect to the VPN with our Linux server. The client Citrix refers to appears to be for remote desktop use through a Web browser, and is hence useless for a server. In a cruel twist of irony, I discovered that the Citrix device is essentially a Supermicro rackmount unit loaded with RHEL, with the proprietary Citrix software running on top. So despite our client being happy with a Linux-based solution, they seem to be locked into Windows by their VPN. -- Need to fork out $$$ for the next software upgrade? Break the cycle! http://www.linux.org.au/linux signature.asc Description: This is a digitally signed message part. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] upgrading complicated installs
david <[EMAIL PROTECTED]> writes: > On Sat, 2008-05-31 at 13:06 +0800, jam wrote: >> On Saturday 31 May 2008 10:00:04 [EMAIL PROTECTED] wrote: >> > >> It is also helpful to try and avoid building your own custom packages as >> > >> much as possible. In many cases alternatives exist, or waiting for an >> > >> upgrade has a longer cost. >> > > >> > > >> > > >> > >> Yes: checkinstall is a good tool for doing this, although the various >> > >> 'dh-make-*' packages provide good support for Perl and PHP modules. [...] > For example, if I'm going to build a package for Cinepaint ... what's > the most appropriate approach? I've never built a package. I would advise that the best path is: 1. Read the distribution packaging guidelines and standards, and understand them. Without that it is easy to cause nasty problems for yourself later. 2. Find an existing package of the tool; cinepaint /was/ in Debian and Ubuntu previously, so the old version will be a good template. 3. Failing that, find a similar package and study it until you understand why it is put together the way it is. 4. Update the packages you have, or build a new one using distribution supplied helpers as much as possible. (eg: dh-make) 5. Build your distribution package, install, test. 6. Modify the package to fix issues you found in testing, update the version of your package to reflect that, and reinstall. 7. If legally permissible, publish your package (at least source, ideally binary) for others to benefit from. The best way to achieve 7 is so submit your changes in the distribution preferred fashion (debdiff, for Ubuntu) to the distribution maintainer, if there is one -- and if not, perhaps you should volunteer? Make sure you understand the legal risks you might be taking, especially licensing related risks, at step 7 though. > These were my "howto" notes I kept when I built Cinepaint on Feisty: > > [EMAIL PROTECTED]:~/howto $ cat cinepaint > download cinepaint, extract into /usr/local/cinepaint-0.22-0 As a rule of thumb you should put the source into one of two places: ~/src/cinepaint-0.22-0(preferable) /usr/src/cinepaint-0.22-0 Using your home dir is strongly preferable because it avoids giving your uid elevated privileges to the rest of the system, and because it is reusable experience if you ever need build software on a machine where you /can't/ get those privileges. > sudo apt-get install libopenexr-dev sudo aptitude install ... Aptitude is generally considered a superior replacement for apt-get these days, since it implements considerably better conflict resolution algorithms. Not that apt-get is going to cause (much) grief or anything. [...] > # make install A better replacement for this is: sudo aptitude install checkinstall checkinstall -D make install That will build a .deb package, which you can then remove using the standard tools at a later point. It will, as one poster pointed out, not be a very /good/ package, but it is at least trivial to remove. Otherwise, look forward to cleaning it up by hand when you want to get rid of the mess (or reinstalling your machine at some stage, of course.) Regards, Daniel -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] upgrading complicated installs
jam <[EMAIL PROTECTED]> writes: > On Saturday 31 May 2008 10:00:04 [EMAIL PROTECTED] wrote: >> >> OK.. looks like a complete install, track down all the bits and pieces >> >> and hopefully not miss anything. >> >> >> >> Luckily I'm reasonably consistent where I put things, so it's just going >> >> to be a long slow process. >> >> >> >> In a perfect world, apt-get would do everything but in practice it >> >> doesn't :( >> > >> > So you can try to narrow the gap between "perfect" and "current" by >> > trying to create packages for the software you write. >> >> It is also helpful to try and avoid building your own custom packages as >> much as possible. In many cases alternatives exist, or waiting for an >> upgrade has a longer cost. (Ahem. I meant "lower" rather than "longer" there. :l) > Might as well use winders. Seriously - is not THIS what the whole > linux thing is all about. Well, from where I set: no. Linux is about getting useful and productive things done. This is true in business, and in my personal life, and is true (I think) for many of the people out there.[1] > You don't NEED to, but if you want to ... Have fun! This is what it's > all about. I have no objection to people who want to build their own packages, but I think it is generally a mistake, and they are generally poorly advised to do so. As asked elsewhere, why? Because building your own packages is a huge commitment. It sounds temptingly easy, but it really isn't -- and most of that cost comes *after* you build the package and install it. Having done this you are faced with needing to do integration and testing for the system when you upgrade, because you have a special unique snowflake of a system that isn't like anything else out there. Your distribution puts in hundreds of person-hours a year, and ofter (much) more, testing updates to make sure they just work. On your system that is no longer valid -- your custom package can throw a spanner in the works, and /you/ better know how to get it back out. You suddenly have to be your own security team: keep up to date on security issues for your package, and anything it depends on, and update your own package when something happens. Without that commitment you well, eventually, get to join the legions of poorly maintained, compromised Linux boxes out there. This hurts everyone, but especially you -- potentially legally, certainly in terms of a lot of work when your ISP (or the police) call up about all that SPAM you have been sending out or those warez you are distributing... You might face a steep learning curve when you want to deploy a new system: the world moved on, and your application isn't available on the platform because it was obsolete some time ago. So, either build it again yourself or face learning the new "standard" now. Either way, not fun to suddenly have thrust on you -- especially if it is for security reasons. Finally, building and maintaining a package costs you. You have to spend a /lot/ of time on it, which you could be using to do something productive. Heck, even a couple of hours is notable... I don't know about you, but I never have enough free time to do everything I want to get done. ;) Regards, Daniel Footnotes: [1] Specifically, as Linux becomes more "mainstream" this becomes more true, because it moves outside the "geek" origins of the platform. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Audio Mixing Deck with Linux
Hi Slugers I want to set up a audio mixer deck in Fedora 9 if possible This is my situation i have 4+ microphones connected to 4 USB Audio adaptors i need to in real time mix and apply filters and output the results to a 5th USB Audio adaptor I am currently using 64Studio and will build up a fedora 9 install with the tools i need shortly. I problem i am having is multiply inputs and outputs at the same time. Any Help is greatly appreciated. regards Daryl Thompson Ph : 0408 472 041 E-Mail : [EMAIL PROTECTED] This email and any attachments are intended only for the addressee and may contain confidential or privileged information. If you have received this email in error please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments. -- Please consider the environment before printing this e-mail -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
