similar to: SHA1

Hi, I am using postgresql for my password and user databases. The problem is, that the information needed in the user database is held in more than one table. But it seems to me that dovecot expects to get all the information for mailbox, uid, gid and home in _one_ query. Is there a way to get around this? Maybe even getting some of this information by another way than pgsql (this is more a

Hi, I have a question about the raw logging feature. As I understand the documentation it is meant for traffic measuring. But it seems to be more targeted at developers. Is there a way for measuring the traffic for the end user? If not with raw loggin in another way? Regards Marco -- The minute a man is convinced that he is interesting, he isn't. -- Marco Herrn _ ___ o

Hi. I'm having a problem with hashing passwords for use in the menu. If I specify plain passwords in my config it works file: Example: MENU MASTER PASSWD 1234567890 MENU PASSWD test123 However if I hash a password using the sha1pass script the resulting hashes don't work. MENU MASTER PASSWD $4$9qj4qv8g$HQ6Jl6TVrpign78XeofX2OLmfJo$ MENU PASSWD test123

Vielen Dank für Ihre e-mail. Da ich vom 30.09.-06.10 in Urlaub bin, kann ich sie leider erst danach bearbeiten bzw. beantworten. In dringenden Fällen, können Sie sich gerne an meinen Kollegen Herrn Lamotte wenden. Er hat die email-Adresse hans.lamotte@umbreit-kg.de und ist telefonisch unter 07142/596-152 zu erreichen. Mit freundlichen Grüßen Michael Müller G. Umbreit GmbH & Co.KG

Abwesenheitsnotiz: Vielen Dank f?r Ihre Nachricht. Ich bin ab dem 16.08. wieder im B?ro erreichbar. In dringenden F?llen wenden Sie sich bitte an Herrn Ostermann, Email <ostermann at dimast.de>. Vielen Dank!

Abwesenheitsnotiz: Vielen Dank f?r Ihre Nachricht. Ich bin ab dem 22.10. wieder im B?ro erreichbar. In dringenden F?llen wenden Sie sich bitte an Herrn Ostermann, Email <ostermann at dimast.de>. Vielen Dank!

The idea of salted hash algorithms is to generate a different hash even if the same text is entered. That can be easily seen with dovecotpw: using NON-salted SHA256, same hash is generated for a given password [root at correio ~]# dovecotpw -s SHA256 -p 123 {SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM= [root at correio ~]# dovecotpw -s SHA256 -p 123

Hi, I am trying to install the salted login generator from rubygems. I have version 0.13.1 of rails installed. When I try to install the salted login generator (gem install salted_login_generator) it asks: Install required dependency rails? If I select yes it says: RubyGem version error: rails(0.11.1 not >= 0.13.1) and fails. It does the same thing when I try to install the regular

First of all, you can probably go online before you convert all passwords. You can modify your query in dovecot-sql.conf.ext to something like the following: SELECT IF(crypt_pass IS NULL OR crypt_pass='', CONCAT('{PLAIN}',plain_pass), crypt_pass) as password FROM mailuser .. This is assuming that: * for incoming users, you have a plain_pass column containing just the plaintext

The cryptic subject is the outcome of my looking into how to do a particular thing. I wonder if anyone else has solved this problem in a way that hasn't occurred to me. I'm using dovecot 1.1.11 on Ubuntu Server 9.10. I could consider upgrading to my own install of a newer dovecot if it made a difference to this problem. I have two populations of dovecot users. Some users have Unix

Hello, I am having some trouble running the unit tests for the salted has login generator. I am a bit new to both ruby and rails so I am having a little trouble deciphering the error message I get when running ''rake test_units''. Up till the point where I try to run the unit tests I have followed the quick start guide for the salted hash login generator

Aki Tuomi wrote: > The use of salt, today, is to prevent the attacker from directly seeing > who has same passwords. Of course it also will make a rainbow table > attack less useful, Not just less useful, but almost infeasible. Given the use of random salts, you would have to generate (number of possible salts) rainbow tables. This drastically changes the CPU/storage tradeoffs. >

Hello, I have a few questions on password schemes. Is SHA512 the most secure? Is there a difference between SHA512 and SHA512-CRYPT? What about SSHA512 and SSH512-CRYPT? Is there a problem with this sql statement: UPDATE virtual_users SET password=CONCAT(?{SHA256-CRYPT}?, ENCRYPT (?Password Goes Here?, CONCAT(?$5$?, SUBSTRING(SHA(RAND()), -16)))) WHERE user=?user at example.com?; I'm

Hi, I am using salted hash login generator to create my login page. In the user_environment.rb file, I saw that there is a comment saying should NOT include the email field in the changeable user fields array. Does anyone know why? > # Add all changeable user fields to this array. > # They will then be able to be edited from the edit action. You > # should NOT include the

Hi folks. I've recently set up a Postfix 2.9.6/Dovecot 2.0.19 IMAPS/SMTPS setup on Ubuntu 12.04.2 (Mysql backend). I'm new to all this, so I apologize if this is fairly basic. I've attempted to the best of my ability to search for an answer, but no luck so far. What I'm trying to do is generate a password hash that I can inject directly into my Mysql database (disaster recovery

All, I''ve come across a confusing problem when attempting to run unit tests for an application on OSX (works on Windows). I''m receiving the following error: `load_specification'': undefined method `parse'' for Time:Class (NoMethodError) This is also confusing because I can''t figure out how the error appeared. When I revert back to previous revisions,

I''m building a site that requires user log-in and i have seen the Agile book using sha1 for password hashing while R-Forum uses md5. Is there any compelling argument to use one over the other? -- Posted via http://www.ruby-forum.com/.

what i have done is as follows password = Digest::SHA1.hexdigest("#{salt}:#{password}") pass1 = Digest::SHA1.hexdigest("#{salt}:asdfgh") pass2 = Digest::SHA1.hexdigest("#{salt}:asdfgh") pass3 = Digest::SHA1.hexdigest("#{salt}:qwerty") puts pass1==pass2 puts pass1==pass3 This works fine but i need to get the decrypted password how can i get it any help is

You do need to complete the query. Don't just replace your query with the one I wrote. You have to have a WHERE clause, and you might need to return other fields. Keep the password query you had before, just replace the 'password' column with "IF( ... ) as password" The query as you have it now simply returns all the passwords for all the users, because you don't have a

Hi I would like to simulate dovecot's dovecotpw with a perl script I tried / used use Crypt::SaltedHash; my $csh = Crypt::SaltedHash->new(algorithm => 'SHA-1'); $csh->add($passwd_string); my $salted = $csh->generate; also use Digest::SHA1; use MIME::Base64; $ctx = Digest::SHA1->new; $ctx->add($passwd_string); $ctx->add('salt'); my $salted =