It's a work in progress. I just kept trying to run the original scripts which were broken on OpenBSD, and reading the error messages then going and modifying the problem code, took about 5 tries for endtube.
There are several command differences even with some of the more common commands. No shuff, changed this to sort -R | head n 1, changed my random number scheme to using just $RANDOM. So some stuff is forcing me to do things more efficiently or differently at least. But some of my other scripts will require substantial reworkings. changing sha256 to shash etc...
I'm new at BSD, but I like it. I have to turn my computers on every day to work with them. I'll get the hang of it eventually. I want to re-write everythign to run with the default BSD ecosystem + some pkg_add ports packages. I'm going to test some more of them on Friday and try to fix them. I'll also have to write a new firewall in pf that approximates endwall.sh for iptables. I should have something internally by January and probably release it in March/April. I'm getting busy though so it might take longer, we'll see.
I have an installation of FreeBSD on a Sun Ultra60 ultrasparc II, but I need to put it on a more modern computer for testing. I'm planning on putting FreeBSD on a mac G5 I have for testing and programming. I'll get around to it all eventually.
Let me know if they work on FreeBSD, or if there are any problems. Thanks for the feedback.
Tyler Torres
Oh god, how did I miss this shit for a month? This is the best thing I have seen all week, thanks OP.
Christopher Miller
By the way, note the -n — the length of the password is actually random, and in 1 out of 256 cases, the password will be Cg==. All these details actually make me suspect it's extremely elaborate trolling, but I'm having a laugh regardless.
There is nothing wrong with urandom. Or at least there wouldn't be if Linux wasn't retarded and would adopt OpenBSD's urandom behavior, oh well. In the cases where such a program would ever be used, a machine will already have enough entropy.
Jordan Anderson
Usually I just run passgen a couple of times and dart my eyes around the screen and start writing down blocks of 4-5 characters from different parts of the screen output into a password log book. I stop writing when the password gets too long.
You can now control the output length by changing the number of bytes it reads $ passgen --bytes 18
outputs a 24 character random password. I've also added the flags --help, --version, --bytes, --outfile
Let me know if you see any other problems, or have any comments, suggestions or product ideas. Thanks.
Matthew Powell
You also know you're dealing with a retard when you torify/torsocks programs that already support using a SOCKS proxy, like curl.
Luis Murphy
What you mentioned about curl has merit, however i'm using torsocks -i which opens a new circuit (seperate and isolated from any circuit in use for something else like web browsing) for the tcp connection.
Also you can then chain a socks5 proxy to the endcurl call using the usual curl flag --socks5 . So this is an advantage. Otherwise I'd agree with your observation. I'll add a --native flag to make it do it with it's own socks compatibility. Thanks for the idea.
Oliver Gomez
Someone go compile screenshots of the other ENTERPRISE JAVA BEAN BOURN[sic] SHELL retardation this lolcow wrote, we can dump this hilarity in the tech cringe thread
No wonder they're trying to stay anonymous at all costs
Parker Scott
I just added the --native flag, and a --version flag it works good. I'll add this option to endtube as well next weekend.
Hey thanks for catching that typographic error on Bourne Shell. I fixed it. Thanks!
William Edwards
The tech cringe thread? Where is that?
I just added the --native, and --version flags to endtube.sh as well as --url and allowing for the last input to be a url and to use additional youtube-dl options.
