leap_web.git/users, branch 0.2.6 [leap_web] Fix button to enable account: https://leap.se/code/issues/4246 2013-10-28T20:10:12+00:00 jessib jessib@riseup.net 2013-10-28T20:10:12+00:00 7aaedeaf6fdd2d84ebab7bde2f6a6bdcf8d930b8 






no need to create a user for testing failed login attempt
2013-10-28T10:08:31+00:00

Azul
azul@leap.se

2013-10-28T10:08:31+00:00

1ef3e9df271934b983ff5afe60c2dcf34c090a98












reset button loading... state on error (#4231)
2013-10-28T09:51:04+00:00

Azul
azul@leap.se

2013-10-28T09:48:53+00:00

315a7c9aa3d6cc6cde51a67b6dcc91aea085f518

including test
refactored error display some





including test
refactored error display some







Merge branch 'feature/4109-https-sources' into develop
2013-10-28T07:53:08+00:00

Azul
azul@leap.se

2013-10-28T07:53:08+00:00

630b6c603594df8a9fa99555928ca68df8e8d8fa












use https sources in Gemfiles and also in the documentation (#4109)
2013-10-18T11:12:50+00:00

Azul
azul@leap.se

2013-10-18T11:12:50+00:00

936015afe051c82d5677601f7f58944ed42b4623












test logging in through the API using python with umlauts
2013-10-18T10:20:23+00:00

Azul
azul@leap.se

2013-10-18T10:20:23+00:00

18c6f005d0eb0099a1d41235818564fbab94fb1b












Merge pull request #98 from jessib/feature/billing-past-due-subscriptions
2013-10-18T07:18:03+00:00

azul
azul@riseup.net

2013-10-18T07:18:03+00:00

221532448ba4c435427ad2b5b3eca729b352c354

Feature/billing past due subscriptions




Feature/billing past due subscriptions






Merge pull request #102 from azul/feature/3602-email-blacklist
2013-10-17T17:51:47+00:00

jessib
jessib@riseup.net

2013-10-17T17:51:47+00:00

bf3b59e6807c8e4789b97232c7416093b07cccdf

blacklist system logins for aliases and logins




blacklist system logins for aliases and logins






blacklist system logins for aliases and logins
2013-10-17T10:05:26+00:00

Azul
azul@leap.se

2013-10-17T10:05:26+00:00

9f4b1bcf315f09fd6d302ad187281ec4ed443f04

We blacklist based on three things:
* blacklist in APP_CONFIG[:handle_blacklist]
* emails in RFC 2142
* usernames in /etc/passwd

The latter two can be allowed by explicitly whitelisting them in APP_CONFIG[:handle_whitelist].

We stick to blocking names that have been configured as both blacklisted and whitelisted - better be save than sorry.





We blacklist based on three things:
* blacklist in APP_CONFIG[:handle_blacklist]
* emails in RFC 2142
* usernames in /etc/passwd

The latter two can be allowed by explicitly whitelisting them in APP_CONFIG[:handle_whitelist].

We stick to blocking names that have been configured as both blacklisted and whitelisted - better be save than sorry.







use latest version of srp_js to fix #4002
2013-10-17T08:13:44+00:00

Azul
azul@leap.se

2013-10-17T08:13:44+00:00

155c2d25395a02916543131348a703cd13573d4c

We were not encoding the srp password properly before. So umlauts in the password would cause the login procedure to fail.





We were not encoding the srp password properly before. So umlauts in the password would cause the login procedure to fail.