Gotta love unsubscribe pages... Filled in the email address as the placeholder text, but clears out the box when I click on it, and the Unsubscribe button doesn't accept it as is, so I need to type it again (link)
@PearsonArtPhoto except that each year in GPU/CPU advancements is as significant as 10-20 years in car advancements, and the VLIW5 architecture is from somewhere around 2009
so it's like buying a brand new 1974 car in 2014 :)
enjoy your carburetor flooding is all I can say ;p and lack of airbags, no CD player or bluetooth, horrible MPG, violating the law by not using a catalytic converter, paint that wears off in a year due to acid rain, etc. ;p
This page contains general information about the GPUs and video cards by Advanced Micro Devices (AMD), including those by ATI Technologies before 2006, based on official specifications in table form.
== DirectX version note ==
DirectX version indicates which graphics acceleration operations the card implements.
DirectX 6.0 - Multitexturing
DirectX 7.0 - Hardware Transformation, Clipping and Lighting (TCL/T&L)
DirectX 8.0 - Pixel Shader 1.1 & Vertex Shader 1.1
DirectX 8.1 - Pixel Shader 1.4 & Vertex Shader 1.1
DirectX 9.0 - Shader Model 2.0
DirectX 9.0b - Pixel Shader 2.0b & Vertex Shader ...
> All models up to including HD 76xx based on TeraScale 2 (VLIW5), HD 77xx - 79xx are based on GCN 1.0 (Graphics Core Next) architecture except the HD 7790 which is based on GCN 1.1.
for HD8000:
> All models up to including HD 84xx based on TeraScale 2 (VLIW5), HD 85xx and later are based on Graphics Core Next architecture.
> All models up to including R5 235X based on TeraScale 2 "Evergreen" (VLIW5) R5 240 and up are based on Graphics Core Next 1.0 The R9 290, R9 290X, R7 260 and R7 260X are based on Graphics Core Next 1.1 and also support TrueAudio.
so even in the very latest branding scheme they're still selling off old VLIW5
@PearsonArtPhoto WEI is pretty meaningless... it hasn't been updated in years... yes, you'll get great performance with desktop effects, but games are much more demanding than desktop effects
Anyone know how I can sort a text file, based on the 3rd column? The text file contains MAC addresses (separated by a dash, and starting with a tilde (~)), then the hash tag, then the DNS name I want to sort it by . This all should be done, hopefully, in the bash shell
But each DNS name should be unique, and that would help us determine if the systems in question were setup by the techs, or by people purchasing machines and putting them on the network themselves
OK, random question: when I run cat /etc/watch-ddhcp/white_list.txt | sort -t'"' -k 2 > ~/newList.txt, it works perfectly. Running that from a script, it outputs a blank file. Am I using it wrong?
@meda So? Are you only allowed to run software that's part of the core OS? If you're allowed to install software beyond what comes with the OS, you can have your pick of dozens of viable FTP servers -- some free, some not.
@meda "Secure FTP" and "SFTP" are not the same thing.
SFTP is FTP over SSH. Since Windows and SSH don't get along that well without some kind of emulation layer (the Windows builtin terminal does not make POSIX-compliant commands available), you probably don't want SFTP, unless you know that you have clients that are unable to use FTP over SSL, which is called FTPS (or FTPES).
FTPS is very similar in design to, say, HTTPS... the client and server set up an SSLv3 or TLSv1.x tunnel, then the regular old FTP protocol is used within that (encrypted) tunnel. Since there's no SSH involved, it's fairly well-suited to Windows.
That isn't to say you can't run an SFTP (FTP over SSH) server on Windows. But you'd probably end up using something like Cygwin, or paying out the nose for a commercial package.
I would suggest you start here. You need to figure out what your criteria are. You can't have NO criteria. The range of software available is so vast that you need to narrow down your choices.
Also, you didn't mention which version of Windows Server you are running, but if you have IIS 7 or later (which I believe comes with Windows Server 2008 R2), it supports FTP + SSL (FTPES) out of the box, so in that case, you just need to activate the role, you don't have to do anything special.
That's assuming you really don't need FTP over SSH (because I can tell you that if you have no particular preference of FTP over SSH or FTP over SSL, I think the latter is the better choice.)
> IIS 7.5 was included in Windows 7 (but it must be turned on in the side panel of Programs and Features) and Windows Server 2008 R2. IIS 7.5 improved WebDAV and FTP modules as well as command-line administration in PowerShell. It also introduced TLS 1.1 and TLS 1.2 support and the Best Practices Analyzer tool and process isolation for application pools.
TLS is just a newer and more secure version of SSL, so TLS 1.1/1.2 on top of FTP is FTPS.
@Kate Er, what?
Are you sure you aren't confusing OpenSSH with OpenSSL?
Also, many of the OpenSSL security vulnerabilities are being fixed now that it has gotten huge public exposure by way of Heartbleed, so that won't have many holes for long anyway.
I haven't heard of any major vulnerabilities in OpenSSH lately; it's still the standard SSH daemon on RHEL, Debian, Ubuntu, *BSD, etc.
@meda You should be able to activate FTPS support and make it required so that all FTP connections must be done over TLS. Check here for multiple ways how to do it (if you prefer GUI-driven, scroll down a few pages until you start seeing the screenshots.)
That'll use IIS as your FTPS server. If you already have IIS running for web hosting, it's probably a good idea.
@meda You only need SFTP if you know that your clients (only) support SFTP. Many standard FTP clients support both SFTP and FTPS.
FileZilla for instance supports both, so it doesn't really matter which one you install on the server side, in the case of using FileZilla as your FTP client.
@meda I agree with @allquixotic that you should be going for FTPS if the client's requirement was "need encryption". If for whatever reason they specifically want SFTP (as was the case with me) this is a good article on setting up an SFTP server on a Windows Server allthingsmarked.com/2006/08/17/…
@meda I already know that. I provided you a link to the Microsoft website where the instructions are for installing the FTP support into IIS and then configuring it. I don't know how else to help you. If you try it and you run into problems, let us know. There's really nothing more I can say except that I think it should work for you.
@meda Not enough information. Linux is just a kernel. It is impossible to know without details of what FTP library or command line software your client is using, whether it will be compatible with FTPS.
That's like saying "I operate a gas station. My client wants to bring a vehicle in to fill it up with fuel. Will you be able to provide fuel that will run in the vehicle?"
@meda The port you select to listen on should not matter. Any FTP client should be able to connect on any port; you'll just have to specify the specific port you choose, if it's not the default, to the client.
The default port for FTPS should be 990. The default port for SFTP -- if you choose to use that instead -- should be 22. The default port for unencrypted FTP would be 21 (but you shouldn't run an FTPS or SFTP server on 21, because that would be confusing.)
@meda It's not required to buy a certificate. The user's client will get a warning that the default or self-signed certificate is not trusted, but they can skip that warning and continue anyway. It will result in slightly reduced security, but it'll still be encrypted.
If you want it to be 100% as secure, but you don't want to pay any money to a public Certificate Authority (CA), you can generate your own Certificate Authority on your server; then generate a key-pair, and share the public key of both the CA and the server with your client.
Your client could then add the keypairs to their FTPS client, and it wouldn't give them any warnings at all, and would provide very strong assurance that they are connecting to YOUR FTPS server, and not a Man in the Middle.
If you were to purchase a certificate from a public CA, the advantage is that you wouldn't have to provide your public certificates to your client using another method (e.g. email), and they wouldn't receive the warning at all.
This is because the public CAs are already trusted by every SSL implementation in the world. (or, they're supposed to be)
@meda it seems you need to get familiarized with IIS first... I would suggest that you first setup a basic FTP through IIS then work your way up to make it secure.
@meda create a test folder and make it accessible through FTP
Would it be possible to add computer related terminology to the list of correctly spelled words? There seems to be a lot of words that are correct that superuser doesn't recognize.
Some of them I ran into today: login, subnet, comodo, IP, DNS, DSL, ISP, Powershell, analytics, and I know there's ...
@MichaelFrank damryfbfnetsi. declined - a moderator reviewed your flag but found no evidence to support it. it's the name of a user. i can't recall his old name. 'g' something.
@allquixotic You should need to read an explanation on why you shouldn't deleted questions then type "I understand" into a text box before you can delete a question with answers that have >-1 votes.
Just got a Starbucks loyalty card today, which left me wondering: does anybody think it's a good idea to start a project on GitHub documenting the Starbucks ordering language?