# [2018.11.19] More on SFTP and SDF
The reason why a non-ARPA user can `sftp` into SDF and can't `sftp`
from SDF is that SFTP server daemon is a subsystem of OpenSSH
Server. It can be easily checked from SDF.
<pre>
$ grep sftp /etc/ssh/sshd_config
Subsystem sftp /usr/libexec/sftp-server
</pre>
If admin comments this line out and restarts `sshd` then nobody
(including ARPA members) will be able to `sftp` to SDF. SFTP also
uses the same port as SSH making it even harder to decouple, and
seemingly that's why we observe the status quo.
I also tried to obtain the newest version of Python on SDF (even
ARPA members have only 3.6 now by default). I `curl`ed the source
tarball from the official Python website and tried to `make` it. I
was only partly successful, since `make` failed to find `ctypes`
library and didn't compile any `pip`. So I have only bare-bone
Python 3.7 with no additional packages whatsoever. Well, maybe next
time.
I can't really say why I'm hacking around SDF, I just get some fun
this way:)
Why don't join ARPA? Well, I paid SDF only because for me $3 are a
small amount of money, and I believe that SDF is a cool project. $36
for ARPA membership are still not much but more tangible, and I
can't say that I feel any difference between being a non-ARPA and
not. But I think that after using SDF for a while I surely will join
ARPA just to support the project more.
Went to 'Fantastic Beasts: The Crimes of Grindelwald' yesterday
evening. Didn't like it at all. The original 'Fantastic Beasts and
Where to Find Them' was much better.
