Russtopia
/
xs
mirror of https://gogs.blitter.com/RLabs/xs
2
1
Fork 0
Code Issues Projects Releases Wiki Activity

Update page 'FAQs'

Russtopia 2021-08-20 20:07:35 -07:00
parent 9fb3f62138
commit 01cd88fbc3
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
FAQs.md

@ -30,12 +30,12 @@ Sure, but again this was a learning project, and those are also written in C, wi
Go away. Just kidding. Well, half-kidding. I plan to learn Rust someday, but not today. Feel free to port `xs` to Rust if you're a wiz, and I'd be interested to compare the implementations, really! I'll still prefer the solution which is easier to read and with lower SLOCC, which I honestly doubt Rust will achieve... I may be proven wrong, and I'll happily buy a round of beer at the release party where this is demonstrated.
### Why won't the server `hkexshd` build in Windows?
### Why won't the server `xsd` build in Windows?
Windows has a completely different console and file handle model from UNIX/POSIX OSes. I jumped through some hoops to get the client `xs` building and running under MSYS2, but the server side needs a lot more platform-dependent voodoo. I don't have the expertise nor desire to go off into the weeds on this; contributors are welcome.
If you can, contribute such cross-platform console and exec/file-handle code to the Go core standard libraries. They are still grappling (as of 2018/2019) with how best to support an OS-neutral terminal/console model.
If you can, contribute such cross-platform console and exec/file-handle code to the Go core standard libraries. They are still grappling, AFAIK, with how best to support an OS-neutral terminal/console model.
### Why is there a separate `xspasswd` util and config file?
Out of caution. Until confidence in this project is higher, the client and server by default depend on a separate user/password database from the default system equivalent. In the near future, I'll add a build option to the client and server to use the system password API to authenticate users so (for example) on Linux /etc/passwd, /etc/shadow etc. will be used. Eventually, that will be made the default.
Out of caution in early development. One still use it, but `xsd` can now use the main system passwd/shadow infrastructure via the `-L` switch.