mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-25 23:35:58 +03:00
[GH-ISSUE #279] Linux support for the Server #136
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#136
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gngeorgiev on GitHub (Jul 15, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/279
How about we make it possible run the server on a linux machine(Ubuntu, Arch, etc.). This will allow the RAT to have a bigger audience. I can do this if you see fit.
@MaxXor commented on GitHub (Jul 15, 2015):
Have you already tried running it with Mono, does it work, are there errors?
@gngeorgiev commented on GitHub (Jul 15, 2015):
Yeah, there are:
NATUPNPLibdoes not work and the theming. Other things should be minor.@MaxXor commented on GitHub (Jul 15, 2015):
Ah, alright. Yes the Listview calls some windows-only functions...
Maybe we could use an alternative to NATUPNPLib to have support for UPnP on Linux too.
@gngeorgiev commented on GitHub (Jul 15, 2015):
Yeah, I think we can use https://github.com/lontivero/Open.NAT. As it will work on bot windows and linux since NATUPNPLib is a COM library which can in no way be used in Linux.
@MaxXor commented on GitHub (Jul 15, 2015):
Alright, I'll make the library change later today so we can get rid of the COM library.
@gngeorgiev commented on GitHub (Jul 15, 2015):
Refer the PR here so I can test it out 🌟
@MaxXor commented on GitHub (Jul 15, 2015):
Sure!
@MaxXor commented on GitHub (Jul 15, 2015):
Library change complete! :) (using now https://github.com/nterry/Mono.Nat)
@gngeorgiev commented on GitHub (Jul 15, 2015):
Great, gonna test it out sometime tonight probably.
@MaxXor commented on GitHub (Jul 15, 2015):
Thanks! I've tested it on Windows, worked very well.
@yankejustin commented on GitHub (Jul 15, 2015):
@MaxXor I would imagine that the Keylogger will be very broken since it relies on Windows' Hooks.
@MaxXor commented on GitHub (Jul 15, 2015):
@yankejustin We are talking here about the Server only. :)
@yankejustin commented on GitHub (Jul 15, 2015):
Oh, right. I apologize. :)
@MaxXor commented on GitHub (Jul 19, 2015):
Now it's starting on Linux with Mono, gonna check the Builder too later.
@bitterypaul commented on GitHub (Jul 30, 2015):
Will the remote desktop work on linux
@ghost commented on GitHub (Jul 30, 2015):
Remote Desktop currently as it is won't work on linux. We would just need to disallow the hooks that the keyboard input uses for it to work.
@MaxXor commented on GitHub (Jul 30, 2015):
Yes, Remote Desktop should be disabled on Mono to prevent any crashes.
@ghost commented on GitHub (Jul 30, 2015):
I'm currently working on keyboard input for Remote Desktop through Mono
@MaxXor commented on GitHub (Jul 30, 2015):
You don't need to do that, it's still incompatible with the entire UnsafeStreamCodec. ;)
@ghost commented on GitHub (Jul 30, 2015):
It is working for me on Ubuntu 14.04 :D, Mono JIT compiler version 4.0.3 (Stable 4.0.3.19)
@MaxXor commented on GitHub (Jul 30, 2015):
Oh, you are right, only the encoding uses functions (i.e.
memcpy) from themsvcrt.dll. Decoding in the server is fine. 👍@ghost commented on GitHub (Jul 30, 2015):
Everything seems to work fine, from what I've tested on the Server with Mono.. I think using the .NET events for the picturebox (e.g. OnKeyDown) might be the best way to support keyboard input (for linux). Do you think this would be fine? If so, I can start working on it!
@MaxXor commented on GitHub (Jul 30, 2015):
Yes, you can easily change this I guess. So the only unsupported thing would be only the mouse wheel, but that's not really important.
@ghost commented on GitHub (Jul 30, 2015):
Right, I believe if we were to implement the mouse wheel we would have to use a parent control to access the MouseWheel event.