Node crypto pbkdf2 yields different keys on 32bit and 64bit machines - node.js

The following snippet seems to yield different answers on 32 bit and 64 bit machines.
var buf = new Buffer('ojHkXkabdV7X6xcDNKJgrg==', 'base64');
console.log(crypto.pbkdf2Sync('secret', buf.toString('binary'), 10000, 14, 'sha256').toString('base64'));
64bit machine is on Node v0.12.4.
32bit machine is on Node v0.10.12.
Is this even possible ?

I moved node from v0.12.4 to v0.10.12 on the 64 bIt machine and the keys match when the snippet is run on both machines.
I also found the implementation that I really needed resides in v0.12.4 therefore my solution to this issue is to upgrade the 32 bit machine to v0.12.4.
Sorry folks ! This is not an architecture problem.

Related

How to install previous Node version in 32 bit Win 7?

I have a 32 bit Win7 machine, and I need to install specific version of Node(V 13, https://nodejs.org/download/release/v13.0.0/)
However I can not find executable files for Win 32 bit system, All are for 64/86 system.
Is there any way ? Or am I at dead end.
Any Node version that compatible with Win 7 32 bit is fine for me.

Kubernetes on 32 bit machine

While I was running kubectl command in my ubuntu 16.04 os which is a 32 bit machine, I was getting
cannot execute binary file: Exec format error
Can some one tell me whether Kubernetes works on 32 bit machine or not ?
Currently there are no ready-made binaries for 32bit systems at: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.7.md#downloads-for-v1710
You can build kubernetes from source though: https://kubernetes.io/docs/getting-started-guides/binary_release/#building-from-source
As a commenter mentioned, there is support for 32bit systems for the client tool, kubectl: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.7.md#client-binaries

Installed windows 10 with 32-bit on accident now i can't re-install windows 10 as 64-bit

I recently installed windows 10 and on accident installed 32-bit. Now when I try to re-install windows 10 with 64-bit I receive the error: This version of the program is not compatible with this version of windows. I know i have A 64-bit processor. HELP!!!
Did you try to install 64 bit version while you are in side the 32 bit version ?
You CANNOT transfer from 32 bit to 64 bit by running the installer as an upgrade over the 32 bit version.
If you need the 64 bit version, please boot from the installation disc and reinstall the OS from scratch (There’s no upgrade path),
Also remember to select the 64 bit version in the setup.
If you need more help read this How to geek article
http://www.howtogeek.com/228042/how-to-switch-from-32-bit-windows-10-to-64-bit-windows-10/

Can I use nuget packages which is not written OS ver 32 or 64 for 32 and 64 bit OS?

Now I got several nuget packages(.nupkg) and installed VS's project on 64bit OS.
It was successfully finished.
And I'd like to install these packages to 32bit PC(StandAlone) by using CD which is burned .nupkg files.
(This PC cannot connect to Internet)
These packages seems to be not defined OS version specifically.
I have a quetion which is written in above title.
Can I use nuget packages which is not written OS ver 32 or 64 for 32 and 64 bit OS?
And would you give me some reaseons about your answer.
Regards.
NuGet packages do not distinguish between 32 or 64-bit version of OS. They can be installed to both.
There was an issue filed on codeplex to support distinguishing for different platforms as
https://nuget.codeplex.com/workitem/679

How to convert a 64 bit rpm file into 32 bit rpm file

Hi I am using Fedora 10 linux with 64bit architecture. I have created 64bit rpm file for my application. It works fine all fedora 10 linux which have 64 bit. But my application doesnot work well for 32 bit linux. So how to convert 64bit rpm file into 32 bit rpm file. Or how to recreate 32 bit rpm file.
Thanks
Sunil Kumar Sahoo
You will need to have 32bit libraries installed on your machine and while package is being build/compile, compiler will need to get -m32 option. I came across this solution:
CC='gcc -m32' CXX='g++ -m32' linux32 rpmbuild --rebuild --target=i586 package.src.rpm
But I didn't try it myself.
Hops it will help you somehow.
BR,
Dawid.
You can use the way Czlowiekwidmo has mentioned or if you have a machine with 32 bit architecture you can set up the same environment as you have setup for 64 bit. follow the same process for rpm creation as you have done for 64 bit then you will get rpm for 32 bit.
Maybe a bit more than you ask for but have you ever looked at http://build.opensuse.org/ ? It's a fantastic build service that allows to build packages for a vast number of Linux distributions (including Fedora 10 - however marked as DISCONTINUED).
Apart from using the superb web-interface, you can also build locally (just in case, your package is closed-source?).
And yes, building both 64 bit and 32 bit packages is supported, along with building 32 bit support libraries for 64 bit platforms.
You can also use "mock" command. "yum install mock", then "man mock", you will find how to use it.
The similar question was answered here:
https://serverfault.com/questions/200712/how-to-create-rpm-for-32-bit-arch-from-a-64-bit-arch-server
One example for mock:
mock -r fedora-10-i386 --rebuild foo.srpm

Resources