Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 12 22:36

    wtgodbe on revert-28171-hoyosjs-patch-31

    (compare)

  • May 12 19:20

    wtgodbe on 3.1

    Update finalize-publish.yml (compare)

  • May 12 17:58

    wtgodbe on 3.1

    Revert "Disable publish to dotn… (compare)

  • May 12 17:58
    wtgodbe closed #28172
  • May 12 17:18
    wtgodbe review_requested #28172
  • May 12 17:18
    wtgodbe edited #28172
  • May 12 17:17
    wtgodbe synchronize #28172
  • May 12 17:17

    wtgodbe on revert-28171-hoyosjs-patch-31

    Update finalize-publish.yml (compare)

  • May 12 17:16
    wtgodbe review_requested #28172
  • May 12 17:16
    wtgodbe opened #28172
  • May 12 17:16

    wtgodbe on revert-28171-hoyosjs-patch-31

    Revert "Disable publish to dotn… (compare)

  • May 12 17:15

    wtgodbe on hoyosjs-patch-31

    Disable publish to dotnet/versi… (compare)

  • May 12 15:58

    wtgodbe on hoyosjs-patch-31

    (compare)

  • May 12 15:58

    Anipik on 3.1

    Disable publish to dotnet/versi… (compare)

  • May 12 15:58
    Anipik closed #28171
  • May 12 15:56
    wtgodbe commented #28171
  • May 12 15:15
    MattGal closed #28103
  • May 12 15:15
    MattGal commented #28103
  • May 12 14:34

    aik-jahoda on v3.1.15

    (compare)

  • May 12 08:29
    hoyosjs opened #28171
Joe4evr
@Joe4evr
also, should the feature make it in next release, then it wouldn't even require unsafe, but it will be limited to use in ref structs (since the compiler needs to guarantee the wrapper object doesn't outlive the ref it points to)
Carlo Kok
@carlokok
hm? Surely you can express it?
Span uses an internal type for a hack workaround, but the runtime team wants to remove that implementation detail
Carlo Kok
@carlokok
hrmm that's nasty. I expected the typesig for byref to just work here.
And of course ByREference<T> is hidden so I can't reuse it.
Joe4evr
@Joe4evr
nor should you
Carlo Kok
@carlokok
yeah well...
Joe4evr
@Joe4evr
like I said, the moment the runtime supports ref fields, ByRef<T> is gonna be removed entirely
Carlo Kok
@carlokok
I need to support .net framework 4.* anyway. so that's not a real option to wait for
I'm trying to model rust's "ref" semantics on the clr
I don't care much if it's safe or not
Joe4evr
@Joe4evr
then I'm afraid you're out of luck
Carlo Kok
@carlokok
Obviously, pointers are a valid option.
But they would require pinning.
Joe4evr
@Joe4evr
hmmmm....
Carlo Kok
@carlokok
This is going to be an interesting project
Joe4evr
@Joe4evr
if you weren't married to 4.X, you could use the new GC APIs to allocate your objects on the Pinned Heap (so there's no need to manually pin)
Carlo Kok
@carlokok
One (other) option would be to use the regular allocation apis (marshal.alloc*) as rust doesn't do interfaces and classes, only structs.
But it would become a c++ level language pretty quickly.
Joe4evr
@Joe4evr
¯\_(ツ)_/¯
Carlo Kok
@carlokok
hahah :) sorry
It's getting a bit off topic
thanks for the help
Joe4evr
@Joe4evr
maybe build your core API in C++/CLI then? :laughing:
Carlo Kok
@carlokok
i have a compiler with vb, c#, pascal, java, go as frontends running on .net
I want to see if it's possible to map rust now
Joe4evr
@Joe4evr
yea.... I sincerely doubt it
Carlo Kok
@carlokok
oh I'll win this battle; the real question is how fast it's going to be
masonwheeler
@masonwheeler
Oh hey @carlokok, haven't seen you in a while!
Carlo Kok
@carlokok
yo @masonwheeler. Been busy yeah
masonwheeler
@masonwheeler
Well, welcome to Dotnet gitter :smile:
John Cullen
@john-cullen
is there a simple way to return an Expression<Func<T>> instead of a Func<T> from an expressiontree or will I need to do something like Expression.Call(Expression, "Lambda", Expression.Lambda(...etc)))
mogo-edenpark
@mogo-edenpark
do you guys know how to get the password from the table as a normal string?
I use .net framework core 3.1
Stephen A. Imhoff
@Clockwork-Muse
@mogo-edenpark - define "normal string". In almost all modern auth systems the string is actually encoded for a specific password handling library (besides salting and hashing), so the "raw" string shouldn't be useful anyways.
mogo-edenpark
@mogo-edenpark
I need to show the actual password to the user. The password is hashed and salted and then saved to the database.
I need to descrypt the hashed and salted password to get as a normal string
Joseph Musser
@jnm2
Being able to show a user a previously-entered password is a sign that the passwords are being mishandled.
Hashes are one-way by design.
masonwheeler
@masonwheeler
Exactly. You can't "decrypt" a hash, because hashing is something different from encryption.
mogo-edenpark
@mogo-edenpark
@jnm2 I understand that, but is there built-in method with userManager to decrypt the password?
Joseph Musser
@jnm2
No, because there is no password stored (unless passwords are being mishandled). Only hashes.
You can let the user reset their password, but if you can retrieve their password, you're endangering them.
Stephen A. Imhoff
@Clockwork-Muse
What problem are you actually trying to solve here? Not as in "show password to user", but what do you think you need the password for? Why do you want the password? Because usually there's a better way to handle that.
mogo-edenpark
@mogo-edenpark
Admin might need to tell the password when the user forgets. The best way for them to do is just changing the password?
Joseph Musser
@jnm2

The best way for them to do is just changing the password?

For sure.

mogo-edenpark
@mogo-edenpark
But is that possible to get the password encrypted with the algorithm entity framework uses
Joseph Musser
@jnm2
You do not want to subvert your users' security.

https://pages.nist.gov/800-63-3/sp800-63b.html:

Verifiers SHALL store memorized secrets in a form that is resistant to offline attacks. Memorized secrets SHALL be salted and hashed using a suitable one-way key derivation function. Key derivation functions take a password, a salt, and a cost factor as inputs then generate a password hash. Their purpose is to make each password guessing trial by an attacker who has obtained a password hash file expensive and therefore the cost of a guessing attack high or prohibitive.