Ohm

Members
  • Content count

    3,178
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by Ohm

  1. I've deployed a new theme and pushed it out as the default. Anyone who manually changed their theme can change it to Midnight Glow by using the drop-down box at the bottom on the page. If you notice any problems with the theme, send me a PM.
  2. Any in-browser database is compromised if only for reasons like this. It doesn't matter if it's encrypted on disk or not, or if it has a master password, only that the browser willingly gives out and exposes your passwords to attackers. You have to remember that most things like this are broken in the protocol, not the encryption. This is the weakness with password safes too. The password safe is secure from any attacks you can throw at it (assuming the crypto is solid). Such a system is only going to be defeated by using a keylogger to grab the master password, grab the password from the clipboard (as many allow you to copy passwords to the clipboard), a network sniffer, or a third party compromise. However, password safes require a manual step. A simple XSS attack isn't going to do it, for example. You can still be fooled, but it's harder to fool a person than a program (at least a person savvy enough to use a password safe).
  3. That's a good advantage. But another of the advantages of a password manager is to have large, incomprehensible passwords that are utterly immune to dictionary and brute force attacks. These are... difficult to type.
  4. That's strange. KeePass works fine for me on Windows. Try upgrading your .net runtime or something. How well does KeePassX work on Linux? I think I mentioned before, I can't get it to copy passwords to the clipboard at all. It just won't work for me.
  5. A .xm file is better known as a MOD file. Look up MOD music for a real trip
  6. They're using the win32 API. If you look at some low-level documents on win32, it explains how to do all that stuff. I specifically remember this guy's tutorials, which are really great. How do they fit such long songs in a tiny file? Chiptunes! They make a primitive little tracker, and a little synth to go with it. It's just a few kilobytes of code and the song itself is quite small. A lot of these programs are really impressive.
  7. KeePass is working great on Linux? Or KeePassX? I can KeePass on Linux, but it was unusable. It couldn't access the clipboard, so you had to open up each password manually, unmask the password, copy it and paste it into Chromium. Quite cumbersome. I blame mono though, because it's easy to blame I had no problems with KeePassX though. The problem is KeePassX can't open KeePass' .kdbx files. I think I'm going to just keep 2 databases. A .kdbx for use with KeePass on Windows (I like the extra features), and every time I make changes, I'll export a .kdb for use with KeePass on Linux. Not ideal, but it works.
  8. I'm running it on the same OS. The problem is certainly not KeePass, it's something on your machine. As for the reasons... did you actually read the first post, or did you tl;dr? Because I thought I explained why you would want to use one quite well.
  9. As for portability, you can put your password database and KeePass or KeePassX on the drive. KeePass is .net, so it should run on all Windows machines that have been updated regularly. KeePassX is written in C++ with Qt, so you'll need to carry around Linux, Windows and OSX builds, but that shouldn't be a problem. The question then becomes how much you trust the machines you're using the password manager on. If you think there's a keylogger, simply change your master password when you get home. Other than that, unless there's a very targeted attack against your specific password manager, it'll be quite difficult to steal passwords from the encrypted database. Even in memory, the passwords are only decrypted when necessary, and erased when they're finished. If you copy a password to the clipboard, it'll clear the clipboard in a few seconds. Overall, I think you might be OK taking the password database with you. I might make a second database for the really important stuff (banking, paypal, etc) that you don't take with you though. Edit: Oh yeah, KeePass works with Mono. Barely.
  10. I agree, but...you do still consider look/database type for collections/etc right? I think that's the point of this post/thread. All he said was audio player. That doesn't necessarily entail a full-blown database of your entire collection. I just click and drag files to a playlist. It's surprisingly easy. I used Amarok for a while when I was on KDE, and it was great while it worked. Some of my files don't have such great ID3 tags though, so I ended up wasting a lot of time cleaning those up. It also broke down from time to time. I tend to avoid these now, and use whatever simple player I have at the moment.
  11. I use whatever happens to be handy at the moment. They all do the same thing in the end, so I don't bother trying to find the "best" one.
  12. Nothing to see here. Go blag about it in your own blag!
  13. DHCP doesn't do any routing. All it does is assign IP addresses, default routes and DNS addresses.
  14. As always, I'm having trouble understanding your post. Do you want to add a second router to your network? What is your current network topology? What do you want to add? Exactly what functionality do you need? You've been around long enough, you should know to include this information if you want any meaningful answers. But yeah, iptables is what you want. You can use it as is, but there are also some frontends you might want to check out. I don't have much experience with it though, any network equipment I hack together with an old machine uses OpenBSD and pf (OpenBSD's packet filter, much easier to use than iptables).
  15. Well.. you could just be using Git. Not the same thing, but the end result is the same.
  16. I thought about installing it a few times, but I never really found a reason. I was using Linux at the time and there was no real reason to switch to a less developed and supported OS for use on the desktop. Some of the features sound really cool but unless you have a real reason for them, they're not a real big draw. So what features are liking? Are you having any specific troubles with it?
  17. Perl is even confusing for experienced programmers. There are so many features, I can't even begin to count them all. It doesn't follow a single paradigm, there are so many "magic" syntax constructs and "blessed" objects that do mysterious things behind the scenes, I can't imagine what it would be like to deal with that on a daily basis. Most of the features lack basic abstractions that would make them seem like an actual part of the language. Almost everything with Perl ends up being a hack that was never fixed or improved. The syntax is extremely cryptic. This is a major hindrance not only for newbies, but for any programmers. The high use of symbols, single letter or symbol variables, "magic" control structures that give no indication to the reader what they do, etc all contribute to "write only" programs. As in they're so cryptic, it takes serious effort to actually figure out what they do, even if what they do is not very complicated. Yes, you can avoid that, but it involves ignoring the idioms of the language and adhering to strict conventions. What's the point of using a language if you have to ignore half of it and fight it at every step. The learning curve is steep. Once you get beyond how to declare a variable and a few basic constructs, it just keeps getting steeper. Want to use object oriented programming? There's yet more cryptic syntax and "blessed" modules with subroutines. When I was programming with Perl, I had to constantly look things like this up. If I used them once then needed them again months later, I'd completely forgotten how to do it. The bottom line is this: Perl is messy. Really messy. Perl is what happens when you get 100 people together to make a programming language. Except they all have a different view of what the language will be, how it will work and what you can do with it. On top of that, you have a project leader that lets all of these ideas be implemented and integrates them all. Perl is a language with no direction and no focus. What comes out of the oven is a gigantic mess. But of course it makes a lot of language nerds very happy, because all of their favorite (often obscure and not very useful) language features are implemented there. This has actually gotten worse with Perl 6 as well. It has even more features you'll never use (or can't remember how to use), and a whole new set of idosyncrasies to learn and work around. That's not to say it can't be used to write good software, but then again I've seen some good software written in GW-BASIC. I'm not about to go recommend that to a newbie though. I suppose he could start with Perl if he really wanted to, but there are much better choices out there.
  18. I've made this point several (many?) times before on these forums. Please, don't recommend Perl to a newbie. Perl is difficult for just about anyone. It has a learning curve that makes the white cliffs of dover look like a gentle hill. It's confusing, it's convoluted, it's messy, and generally a terrible programming language. You can debate that last point all you want, but I think we can all agree that this is one that newbies should stay clear of.
  19. Starting is hard. Like anything, there's a learning curve and as this is not a trivial task, the curve is rather steep and quite high. Pick a programming language and learn it. Knowing a programming language is mandatory. Even if you don't know exactly how something is written, having programming experience and having a reasonable knowledge of how something could be written is essential. The more of this knowledge you have, the more things you will know intuitively. It is not possible to understand a thing about computers without knowing how they're programmed, so even if this doesn't achieve any of your short-term goals, your first step should be to learn a programming language. I recommend a modern, dynamic language. They're very easy to work with, easy to learn, very forgiving, etc. Some good candidates are Ruby and Python. Both are free, both run on any OS, and both have free (legal) books online teaching them. It doesn't really matter which language you choose though, just stick with it. Saying C is too hard and just giving up wastes time. Yes, you are going to be confused. Yes, it will take work. Yes, you will get through it. So just pick a language, learn it, and (this is the important part) stick with it. Learn it completely and thoroughly. This could take you a very long time, as there are a lot of concepts you need to wrap your brain around, but it will happen. Use this language to write programs. Either computer science problems, other "practice" programs, or practical programs. Become a competent programmer. Once you're a competent programmer, a lot of other things just fall into place. You also don't really need a "mentor." You can ask any and all questions you want here, we'll all be your mentor.
  20. How are you measuring RAM usage?
  21. That's also assuming the router's address is .1 as well. I guess the point is having your router on a non-default network, possibly with a host address other than .1 will prevent blind attacks like this.
  22. So make 256 of these image tags.
  23. Whether it's a malicious trojan or not, all antivirus programs will probably call it a trojan anyway. There's no real way to tell what this is without source code (or some RE work I don't think any of us want to do). Download at your own risk.
  24. Hardware problems, have we? While it's true that there is quite a bit of hardware that's not compatible, to me it only makes sense to check your hardware for compatibility before trying an operating system. It's also true that on Unix systems it might take a little more configuration to get a piece of hardware working, but for me it's always been a one-time deal resulting in working hardware, and almost every time I learned something about the system. Yes, hardware problems. Always hardware problems. Or more accurately, software problems on Linux. Linux boasts the most drivers in the world, yet most are of obsolete hardware and the drivers for modern hardware are always a step behind. If your stuff works out of the box, it's by chance you have a configuration that works. Next kernel release with new drivers and that might all change. Linux is a never-ending battle of fighting with drivers that rarely work. It's a headache I prefer not to put up with. What if I just want to listen to some music? Well, first I have to check if pulse audio didn't explode again. Next I have to check my levels. If anything turned up the master level past 50, it distorts horribly. Then I have to start playing it and hope nothing turned the line-in audio up unexpectedly (as tvtime seems to like doing). Because if that happened, all you get is static. This seems to be the story with most realtek audio chipsets, which seem to be the de facto standard for integrated audio these days. Another headache I prefer not to put up with. So if you want to put up with things like that, have fun. I have better things I could be doing than fighting with my own hardware. I have no such problems on Windows. You just install it and it works. Things have been working for me and many others in a pretty straight line. You can't generalize your case just as I can't generalize mine. Drivers always break on Linux. It's a given you'll have to waste your time fscking with them at some point in time. There's also a chance that your hardware will just be broken on Linux, as I've come across several times. An update to a driver just breaks it, and you either have to downgrade it or live without the hardware. And yes, I can generalize my case. Go to any Linux forum and it's full of people needing help getting their hardware working. And for every person that posts, there's more behind them that are simply reading the posts with the same problem, have given up on the problem, or have solved it themselves. I'd say it's a pretty accurate generalization. Windows games don't work on Unix? Scandalous! Flash is a steaming pile of crap. If you want to waste your game playing time messing with Wine and hoping it works, again, good luck. If I want to play a game, winecfg is not a very good one. I'd rather play Civ 4 or something. I'd like to amend your statement about flash. Flash is a steaming pile of crap on Linux. Flash works fine on Windows. I'm sorry Flash doesn't work on your OS, but it doesn't mean you have to take it out on the rest of us. I enjoy flash video and flash games on Windows. True, flash is not ideal (certainly not for video), but it works fine. On Windows. So yeah, I really didn't expect for you to dissect all that. All I'm saying is that Linux is a pain in the ass. I'm much happier and spend less time fscking with Linux drivers by running it in a VM. I still get access to all the tools on Linux without any of the headache.
  25. Yes, really. What part of spending hours trying to get the sound driver for your integrated sound working, or trying to figure out why your video driver makes everything lock up, or trying to get MadWifi to work sounds fun? If it's not one thing, it's another. Rarely, everything on the machine will actually be working as intended, but then you're terrified to upgrade because it might break something. And this isn't even considering things like trying to play a game or watch a flash movie, which will only disappoint you. There are many times where I've said to myself "Gee, if I were running Windows this would just work." No, I ditched Linux as my native OS a long time ago. It just ended up being a frustrating, disappointing time sink. I have it in a VM where I have the same access to all the tools with none of the headache. It runs a little slower, but the trade-off is totally worth it in saved time and hair-pulling. I only run it natively on the Eee PC, where running it in a VM is unrealistic.