On Mon, Mar 27, 2023 at 09:48:37AM -0700, Jared Harper wrote:
> As of right now, the website redirects incorrectly:
>
> ~% curl -I https://www.tarsnap.com/scrypt/
> HTTP/1.1 301 Moved Permanently
> Date: Mon, 27 Mar 2023 15:12:55 GMT
> Server: Apac
As of right now, the website redirects incorrectly:
~% curl -I https://www.tarsnap.com/scrypt/
HTTP/1.1 301 Moved Permanently
Date: Mon, 27 Mar 2023 15:12:55 GMT
Server: Apache/2.4.55 (FreeBSD)
Location: http://www.tarsnap.com:8080/scrypt.html
Content-Type: text/html
FilesOpenSSL-Win64 and c:Program
FilesOpenSSL-Win32
thanks
gIndex: py-scrypt//Makefile
===
RCS file: /cvs/ports/security/py-scrypt/Makefile,v
retrieving revision 1.10
diff -u -p -r1.10 Makefile
--- py-scrypt//Makefile 11 Mar 2022 19:53:58
> The following diff adds WANTLIB to help the port to update for the
> next bump.
ok tb
Hi,
It seems that security/py-scrypt has missing WANTLIB for system shared
library. Currently, it doesn't have any WANTLIB, but it is a c module
which depends on crypto and pthread.
With the recent crypto bump, it fails to run:
$ python3 -c 'from scrypt import hash'
Traceback (m
On Wed, Feb 10, 2021 at 01:27:28PM +, Charlene Wendling wrote:
> Here is a patch for security/py-scrypt:
> i) Update to 0.8.17
> ii) Switch to python3
> It build well and pass all tests on amd64-6.8 system.
>
> Only one port depends on it, security
Hi, ports@:
Here is a patch for security/py-scrypt:
i) Update to 0.8.17
ii) Switch to python3
It build well and pass all tests on amd64-6.8 system.
Only one port depends on it, security/py-passlib, build
well pass test with this patch too.
wen
Index: Makefile
Björn Ketelaars wrote:
> On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> > On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > > Björn Ketelaars wrote:
> > > > - When estimating the amount of available RAM, scrypt ignores
> > > > RLIMIT_DATA on systems w
On Sun, 12 Jan 2020 15:38:21 +0100
Björn Ketelaars wrote:
> On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> > On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > > Björn Ketelaars wrote:
> > > > - When estimating the amount of available RAM, scrypt ignores
> >
On Sun 12/01/2020 15:38, Björn Ketelaars wrote:
> On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> > On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > > Björn Ketelaars wrote:
> > > > - When estimating the amount of available RAM, scrypt ignores
> > > >
On Thu 02/01/2020 06:27, Björn Ketelaars wrote:
> On Wed 01/01/2020 23:03, Ted Unangst wrote:
> > Björn Ketelaars wrote:
> > > - When estimating the amount of available RAM, scrypt ignores
> > > RLIMIT_DATA on systems which have mmap.
> >
> > This is wro
On Wed 01/01/2020 23:03, Ted Unangst wrote:
> Björn Ketelaars wrote:
> > - When estimating the amount of available RAM, scrypt ignores
> > RLIMIT_DATA on systems which have mmap.
>
> This is wrong on OpenBSD. I sent an email to Colin, but the update should
> patch
Björn Ketelaars wrote:
> - When estimating the amount of available RAM, scrypt ignores
> RLIMIT_DATA on systems which have mmap.
This is wrong on OpenBSD. I sent an email to Colin, but the update should
patch this out in the meantime.
Hi Kurt,
On Wed, 1 Jan 2020 12:46:36 -0500
Kurt Mosiejczuk wrote:
> I used this (without the COMPILER_LANGS line) to fix scrypt in the
> current sparc64 build. I saw I should have used COMPILER_LANGS too
> after the fact.
>
> --Kurt
I've looked at the issue on my powerpc
I used this (without the COMPILER_LANGS line) to fix scrypt in the current
sparc64 build. I saw I should have used COMPILER_LANGS too after the fact.
--Kurt
Index: Makefile
===
RCS file: /cvs/ports/security/scrypt/Makefile,v
Diff below brings security/scrypt to 1.3.0. Significant changes since
1.2.1 [0]:
- In addition to the scrypt command-line utility, a library
"libscrypt-kdf" can now be built and installed by passing the
--enable-libscrypt-kdf option to configure.
- On x86 CPUs which support them,
On Sat 23/11/2019 14:54, Stuart Henderson wrote:
> ok to import?
>
>
> This is a set of Python bindings for the scrypt key derivation function.
>
> Scrypt is useful when encrypting passwords as it is possible to specify a
> *minimum* amount of time to use when encrypti
ok to import?
This is a set of Python bindings for the scrypt key derivation function.
Scrypt is useful when encrypting passwords as it is possible to specify a
*minimum* amount of time to use when encrypting and decrypting. If, for
example, a password takes 0.05 seconds to verify, a user
Hi!
Here is an updated port.
With a lot of help from jca@, we've managed to "persuade" (no, really,
Joshua was also very-very helpful :) ) upstream to replace the base64
functions with portable ones, so it now compiles and works on strict
aligned archs also.
Ok?
Daniel
--
LÉVAI Dániel
PGP key
On p, dec 20, 2013 at 14:37:15 +0100, Jérémie Courrèges-Anglas wrote:
[...]
> I doubt -soname $fullversion is a good idea. But we don't need
> it -soname at all. Also, duplicating information that could be present
> in the port Makefile only isn't a good idea.
>
> Here's a tarball that uses MAKE
LEVAI Daniel writes:
> On cs, dec 19, 2013 at 14:14:40 +0100, Jérémie Courrèges-Anglas wrote:
>> LEVAI Daniel writes:
> [...]
>> but you can keep the upstream version in the comment.
> [...]
>
> This was fixed in the last tarball.
"0" was indeed their version number, hehe. Ahem.
>> >> | @bin
On cs, dec 19, 2013 at 14:14:40 +0100, Jérémie Courrèges-Anglas wrote:
> LEVAI Daniel writes:
[...]
> but you can keep the upstream version in the comment.
[...]
This was fixed in the last tarball.
> >> | @bin lib/libscrypt.so.0
> >> | lib/libscrypt.so
> >>
> >> Library generation is wrong, the
this url query hack, please use the newer style of github
>> handling you'll see in other ports e.g. www/tt-rss.
>
> Oh blimey! I would have sweared that I saw this in devel/libgit2 (that
> pkg was even your example in [1] :) ).
I think that included the GH_VER stuff.
>>
On v, dec 15, 2013 at 11:23:22 +0100, LEVAI Daniel wrote:
> On szo, dec 14, 2013 at 22:41:21 +, Stuart Henderson wrote:
> > On 2013/12/14 18:35, LEVAI Daniel wrote:
> [...]
[...]
> Okay, I tried to do a better job this time. The source builds a
[...]
Ping?
Daniel
--
LÉVAI Dániel
PGP key ID
> handling you'll see in other ports e.g. www/tt-rss.
Oh blimey! I would have sweared that I saw this in devel/libgit2 (that
pkg was even your example in [1] :) ).
>
> | SHARED_LIBS += scrypt 1.0 # 1.0
>
> Library versioning for OpenBSD ports should start at 0
ewer style of github
handling you'll see in other ports e.g. www/tt-rss.
| SHARED_LIBS += scrypt 1.0 # 1.0
Library versioning for OpenBSD ports should start at 0.0.
| @bin lib/libscrypt.so.0
| lib/libscrypt.so
Library generation is wrong, there should be
libscrypt.so. and also either a
st
Hi!
I came across this useful library.
I could only test it on amd64, and have no idea how it behaves
elsewhere.
Aside from a simple patch, the build is pretty straightforward, and the
regression test also runs smooth.
libscrypt_scrypt() is very simple to use and the header file contains
useful A
On Sat, Dec 18, 2010 at 11:34:52PM +0100, Marius ROMAN wrote:
>Update to scrypt 1.1.6.
>Tested with mandoc(1) so I removed the line wth groff.
>Tested on i386.
>Encrypted / decrypted one file and works OK.
>
>Comments ? OK ?
>
>Index:
Update to scrypt 1.1.6.
Tested with mandoc(1) so I removed the line wth groff.
Tested on i386.
Encrypted / decrypted one file and works OK.
Comments ? OK ?
Index: security/scrypt/Makefile
===
RCS file: /cvs/ports/security/scrypt
Stuart Henderson wrote:
> no time to look further now; build fails:
>
I did look at it. Maybe this can give you some clue. When you comment
out
# SEPARATE_BUILD = concurrent
it builds fine. I have to check the documentation what this
separate build mean.
Cheers,
Predrag
On 2009/06/15 21:06, Predrag Punosevac wrote:
> Original Message
> Date: Mon, 15 Jun 2009 16:39:04 -0600
> From: Colin Percival
> To: Predrag Punosevac , wen heping
>
> Subject: new version of scrypt
>
> Hi scrypt ports maintainers,
>
> I just
Colin Percival wrote:
> Hi Predrag & OpenBSD ports people,
>
> I've released scrypt version 1.1.3, which now has a man page in addition to
> the
> portability fixes in the version I sent Predrag for testing a few days ago; it
> is at
> http://www.tarsnap.com
Colin Percival wrote:
> Hi Predrag & OpenBSD ports people,
>
> I've released scrypt version 1.1.3, which now has a man page in addition to
> the
> portability fixes in the version I sent Predrag for testing a few days ago; it
> is at
> http://www.tarsnap.com
Hi Predrag & OpenBSD ports people,
I've released scrypt version 1.1.3, which now has a man page in addition to the
portability fixes in the version I sent Predrag for testing a few days ago; it
is at
http://www.tarsnap.com/scrypt/scrypt-1.1.3.tgz
and there's a GPG-signed SHA256
Just one correction. The name of the package is scrypt. I played
with it in the mean time. I do not see any man pages.
You can encrypt a file as:
scrypt enc filename filename.enc
To decrypt
file scrypt dec filename.enc filename.decrypted
Sorry for the wrong name.
Predrag
Stuart Henderson wrote:
> On 2009/05/19 21:05, Predrag Punosevac wrote:
> > Is anybody working on porting scrypt to OpenBSD?
> >
> > www.daemonology.net/blog/2009-05-16-scrypt-version-1.1-released.html
> >
> > I tried to compile out of joke on 4.4/amd64
On 2009/05/19 21:05, Predrag Punosevac wrote:
> Is anybody working on porting scrypt to OpenBSD?
>
> www.daemonology.net/blog/2009-05-16-scrypt-version-1.1-released.html
>
> I tried to compile out of joke on 4.4/amd64 and compiler reports
> slue of problems.
>
> Best
Is anybody working on porting scrypt to OpenBSD?
www.daemonology.net/blog/2009-05-16-scrypt-version-1.1-released.html
I tried to compile out of joke on 4.4/amd64 and compiler reports
slue of problems.
Best,
Predrag
38 matches
Mail list logo
