121–130 of 187 posts
Choosing a ftp server in 2021 is an decission between two options, bad and worse. Vsftpd is easier to setup than proftpd but it last release was 6 years ago...
Earlier quoted context omitted.
Because nodejs kubernetes modern cloud.
> Because nodejs kubernetes modern cloud. Not necessarily so. The history of FTP servers is ridden by bugs with practically no exceptions. At some point some folks decided they finally implement a bug-free implementation and even dared to call it "Very Secure FTPd." Needless to say, it turned out it has bugs, too. As most of these bugs were related to buffer overflows and similar issues, implementing a new FTP server…
I see a fairly alarming open issue: https://github.com/autovance/ftp-srv/issues/167
Amazing. I never thought I would say this, but I actually implemented an FTP server in 2020. This was needed to support firmware updates to specific hardware (Electric Vehicle charging stations). Apparently embedded software developers choose FTP whenever a spec doesn't specify how binary file transfers should work. It was kind of amusing getting FTP to work in a modern cloud environment. I run a single Kubernetes po…
If you did this for work, junior engineer move in my opinion. This practice is called not invented here syndrome.
Amazing. I never thought I would say this, but I actually implemented an FTP server in 2020. This was needed to support firmware updates to specific hardware (Electric Vehicle charging stations). Apparently embedded software developers choose FTP whenever a spec doesn't specify how binary file transfers should work. It was kind of amusing getting FTP to work in a modern cloud environment. I run a single Kubernetes po…
> I never thought I would say this, but I actually implemented an FTP server in 2020. If you did this for work, junior engineer move in my opinion. This practice is called not invented here syndrome.
You don't always have off-the-shelf packages for every conceivable environment you work in.
Not that I think we should go back, but I do miss the wildwest days of web development when it was still acceptable to FTP untested code straight to production. For my first dev job we would develop on production using an FTP client to push up changes on save. One day I was writing an SQL UPDATE statement and I forgot to include a WHERE clause. I basically nuked the entire product DB and it took days to recover becau…
I still use it to sync folders to my iPad (from Documents Readdle). Since walled gardens don't leave much options open, it's basically either that or a cloud provider -- and no free cloud plan has enough space to store these folders. So FTP wins easily this one. It's free with unlimited storage, always has been, always will be.
Amazing. I never thought I would say this, but I actually implemented an FTP server in 2020. This was needed to support firmware updates to specific hardware (Electric Vehicle charging stations). Apparently embedded software developers choose FTP whenever a spec doesn't specify how binary file transfers should work. It was kind of amusing getting FTP to work in a modern cloud environment. I run a single Kubernetes po…
Username: anonymous
Anonymous login accepted, enter e-mail address as password.
Password: aoeu@aoeu.com
I bet aoeu.com and asdf.com got a good amount of unwanted mail back then.
Earlier quoted context omitted.
FTP is certainly more flexible and virtual users are far more secure than adding folks to /etc/passwd. PureFTPd [1] was my favorite for that very reason. There have been a few FTP daemons that supported the SFTP protocol and had virtual users, but they had too many bugs for me. I believe ProFTPd was one of them. Regarding SFTP and null passwords, I do not use a separate sshd. I just use the "Match" stanza in OpenSSH.…
I was forced to implement chroot() for SFTP users under Oracle/RedHat Linux 5. We are, alas, still running it. The OpenSSH 4.3 release on this platform does not support the "match" keyword, but I was able to coerce it to run a separate SFTP-only on port 24, where I constrained the SFTP-specific accounts. I find that I prefer this approach. My wily users then discovered that the working passwd entry also let them logi…
I put a sftp server back up. Feel free to play around with it. This is a single sshd instance and a copy of the config is in the /pub directory of the anonymous user. I did not change anything in pam. The sftp users are selinux confined as user_u.
server: 45.79.100.12
port: 22
username: anonymous, anon, pub, public
pw: (null) just hit enter
Earlier quoted context omitted.
I thought a byte ment “by eight” What’s a nibble of a byte is 8bits
By the way, the handy word for an 8-bit byte is “octet” (I have not observed octet used in the software industry, only in school. Don’t use it at work or you might come across as an ass...) I was curious and searched HN and found this 2012 comment explaining octet is essentially an anachronism, as bytes have been standardized at 8 bits: https://news.ycombinator.com/item?id=4649528 . Feeling old!
So, do we still have to give our email to enter in Anonymous mode? And can we use PASV?